test_min_time_to_next_builder fails spuriously

Bug #541914 reported by Aaron Bentley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

This test fails on one machine, but not another. It's clearly a timing issue. I will disable it in an upcoming landing.

Failure in test test_min_time_to_next_builder (lp.buildmaster.tests.test_buildqu
eue.TestMinTimeToNextBuilderMulti)
Traceback (most recent call last):
_StringException: Text attachment: traceback
------------
Traceback (most recent call last):
  File "/home/abentley/launchpad/stable/eggs/testtools-0.9.2-py2.5.egg/testtools
/runtest.py", line 128, in _run_user
    return fn(*args)
  File "/home/abentley/launchpad/stable/eggs/testtools-0.9.2-py2.5.egg/testtools
/testcase.py", line 368, in _run_test_method
    testMethod()
  File "/home/abentley/launchpad/deleted-proposal/lib/lp/buildmaster/tests/test_buildqueue.py", line 803, in test_min_time_to_next_builder
    check_mintime_to_builder(self, apg_job, 29)
  File "/home/abentley/launchpad/deleted-proposal/lib/lp/buildmaster/tests/test_buildqueue.py", line 110, 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 (30 > 29)
------------

Revision history for this message
Julian Edwards (julian-edwards) wrote :

This is failing locally for Aaron but not on ec2 or buildbot it seems. There's clearly a race somewhere.

Changed in soyuz:
status: New → Triaged
tags: added: tech-debt
Changed in soyuz:
importance: Undecided → High
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.