Closed mbenkmann closed 9 years ago
From mux2...@gmail.com on October 28, 2013 02:08:12
Summer->Winter time transition has resulted in jobs planned for 1:xx,2:xx and 3:xx to not be executed. Grooming jobdb produces the following errors:
ERROR! Job has not launched. This is a bug. Please report. Job:....
Summary: Summer/winter time transition results in jobs not being executed (was: Test summer/winter time transition)
Labels: -Type-Task Type-Bug
From mux2...@gmail.com on October 28, 2013 02:08:53
There seems to be a difference in behaviour between Lucid and Precise. Make sure it works on both.
From mux2...@gmail.com on October 28, 2013 02:52:28
The problem may lie in the Go runtime. util.WaitUntil() looks good. I need to test WaitUntil() with the time transition.
From mux2...@gmail.com on November 06, 2014 09:22:46
Done in git ee20caa44fb387f2c42966b57eeb6221f6dec5a8
Status: Done
From matthias...@gmail.com on April 01, 2013 10:29:49
Just before the summer=>winter time conversion, create some jobs to be executed after the transition. Then let the transition happen while go-susi is running.
Test that the jobs' times are correctly reported on the server where they are created.
Test that the jobs' times are correctly reported on (go-susi) peers.
Test that the jobs are executed at the correct time.
Test that jobs created after the transition (without restarting go-susi in between) are correctly reported and executed.
Create a similar task ticket for the winter=>summer time transition.
Original issue: http://code.google.com/p/go-susi/issues/detail?id=108