Cron-related integration tests are flaky

Bug #1454532 reported by Free Ekanayaka
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Charm
Invalid
Medium
Unassigned

Bug Description

Fernando reported that he had several failed runs, and I'm myself occasionally getting things like:

Failure in test test_update_security_db_cron (basic.test_service.CronTest)
Traceback (most recent call last):
  File "/usr/lib/python3.4/unittest/case.py", line 57, in testPartExecutor
    yield
  File "/usr/lib/python3.4/unittest/case.py", line 574, in run
    testMethod()
  File "/home/free/src/server/integration-test-layers/tests/basic/test_service.py", line 185, in test_update_security_db_cron
    self.assertEqual(output, "")
  File "/usr/lib/python3.4/unittest/case.py", line 794, in assertEqual
    assertion_func(first, second, msg=msg)
  File "/usr/lib/python3.4/unittest/case.py", line 1167, in assertMultiLineEqual
    self.fail(self._formatMessage(msg, standardMsg))
  File "/usr/lib/python3.4/unittest/case.py", line 639, in fail
    raise self.failureException(msg)
AssertionError: 'Error downloading USN pickle from https:/[10855 chars]onds' != ''
Diff is 11035 characters long. Set self.maxDiff to None to see it.

I think cron-related integration tests need some love.

tags: removed: kanban
Revision history for this message
🤖 Landscape Builder (landscape-builder) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

Landscape Team

Changed in landscape-charm:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.