#2261: Nightly tests fail in timezones which differ by odd multiples of 30
minutes
from UTC.
--------------------------+--------------------
Reporter: sa1 | Owner:
Type: defect | Status: new
Priority: major | Milestone: 0.8.7
Version: 0.8.6p1 | Resolution:
Keywords: tests, simple |
--------------------------+--------------------
Comment (by wakeupsid):
A patch similar to this[1] may solve the problem. But I don't understand
root cause of the problem. After this change one test fails in these
timezones.
Traceback:
{{{
[FAIL]
Traceback (most recent call last):
File "/home/naveen/gsoc/buildbot-
work/src/master/buildbot/test/unit/test_schedulers_timed_Nightly.py", line
354, in test_iterations_onlyIfChanged_mixed_changes
self.assertEqual(self.events, [ 'B[3,5,6]@1500' ])
File "/home/naveen/gsoc/buildbot-work/sandbox/local/lib/python2.7/site-
packages/twisted/trial/unittest.py", line 270, in assertEqual
% (msg, pformat(first), pformat(second)))
twisted.trial.unittest.FailTest: not equal:
a = ['B[3,5,6]@2100']
b = ['B[3,5,6]@1500']
buildbot.test.unit.test_schedulers_timed_Nightly.Nightly.test_iterations_onlyIfChanged_mixed_changes
}}}
I don't understand why this test runs at 35 minutes.
[1] http://paste.pocoo.org/show/582896/
--
Ticket URL: <http://trac.buildbot.net/ticket/2261#comment:4>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
