spurious failure in test_min_time_to_next_builder

Bug #525329 reported by Curtis Hovey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Muharem Hrnjadovic

Bug Description

The db0devel build failed, but I cannot reproduce the issue. I think the code is fine, the test is not. I have disabled this test.

Failure in test test_min_time_to_next_builder (lp.soyuz.tests.test_buildqueue.TestMinTimeToNextBuilderMulti)
Traceback (most recent call last):
_StringException: Text attachment: traceback
------------
Traceback (most recent call last):
  File "/srv/buildbot/slaves/launchpad/db-devel/build/orig_sourcecode/eggs/testtools-0.9.2-py2.5.egg/testtools/runtest.py", line 128, in _run_user
    return fn(*args)
  File "/srv/buildbot/slaves/launchpad/db-devel/build/orig_sourcecode/eggs/testtools-0.9.2-py2.5.egg/testtools/testcase.py", line 368, in _run_test_method
    testMethod()
  File "/srv/buildbot/slaves/launchpad/db-devel/build/lib/lp/soyuz/tests/test_buildqueue.py", line 758, in test_min_time_to_next_builder
    check_mintime_to_builder(self, apg_job, 30)
  File "/srv/buildbot/slaves/launchpad/db-devel/build/lib/lp/soyuz/tests/test_buildqueue.py", line 105, in check_mintime_to_builder
    % (delay, min_time))
  File "/usr/lib/python2.5/unittest.py", line 309, in failUnless
    if not expr: raise self.failureException, msg
AssertionError: Wrong min time to next available builder (28 != 30)
------------

Related branches

Changed in soyuz:
assignee: nobody → Muharem Hrnjadovic (al-maisan)
tags: added: spurious-test-failure
Revision history for this message
Diogo Matsubara (matsubara) wrote : Bug fixed by a commit
Changed in soyuz:
status: Triaged → Fix Committed
Revision history for this message
Michael Nelson (michael.nelson) wrote :

Hi Muharem,

It turns out that the min_time_to_next_builder can be +/- the value? See

https://lpbuildbot.canonical.com/builders/lp/builds/610/steps/shell_7/logs/summary

Sorry if I led you up the wrong path during the pre-imp. call!

Changed in soyuz:
status: Fix Committed → Triaged
Changed in soyuz:
milestone: 10.02 → 10.03
Changed in soyuz:
status: Triaged → In Progress
Revision history for this message
Ursula Junque (ursinha) wrote :
Changed in soyuz:
status: In Progress → Fix Committed
tags: added: qa-needstesting
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

It's still failing for most people in non-UTC timezones...

Changed in soyuz:
status: Fix Committed → Triaged
Changed in soyuz:
status: Triaged → Fix Committed
Revision history for this message
Ursula Junque (ursinha) wrote :

If it's failing so it should be qa-bad, I've tagged it properly. Thanks!

tags: added: qa-bad
removed: qa-needstesting
Revision history for this message
Ursula Junque (ursinha) wrote :
tags: added: qa-needstesting
removed: qa-bad
tags: removed: qa-needstesting
Changed in soyuz:
status: Fix Committed → Fix Released
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.