Closed Bug 1174870 Opened 8 years ago Closed 8 years ago

SETA is not scheduling win xp tests on fx-team as expected


(Infrastructure & Operations Graveyard :: CIDuty, task)

Not set


(Not tracked)



(Reporter: kmoir, Assigned: catlee)




(1 file)

Despite timeout limit being reached.  For instance, this is the only instance of fx-team mochitest-1 opt windows xp that has run today

     RyanVM|sheriffduty	kmoir|buildduty: does SETA know about per-product builds?
	RyanVM|sheriffduty	i.e. if build #10 is an android-only push, did I just get hosed out of WinXP tests for another 10 pushes?	
	kmoir|buildduty	RyanVM|sheriffduty: If only android tests are scheduled, the scheduling skipping will only be applied to that platform
	RyanVM|sheriffduty	so in theory I'll get them on the next push?
	kmoir|buildduty	that is my understanding

	RyanVM|sheriffduty	why hasn't WinXP run a full set of tests since 4am PT today?
	RyanVM|sheriffduty	better shown by
Assignee: nobody → kmoir
Summary: SETA is not scheduling win xp tests on fx-team → SETA is not scheduling win xp tests on fx-team as expected
Attached patch fix idle timeoutSplinter Review
Attachment #8715009 - Flags: review?(rail)
I think the problem was that we were comparing the age of the most recent request instead of the age of the oldest request. This meant that for the idle timeout to work, the time between any two builds had to be longer than the timeout period. Anything shorter would effectively reset the timeout.
Attachment #8715009 - Flags: review?(rail) → review+
Comment on attachment 8715009 [details] [diff] [review]
fix idle timeout

I landed it

so could reconfig with bug 1243877 at the same time
Attachment #8715009 - Flags: checked-in+
in production, thanks for fixing this!
Assignee: kmoir → catlee
Closed: 8 years ago
Resolution: --- → FIXED
Blocks: 1244219
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.