Closed Bug 790510 Opened 10 years ago Closed 10 years ago

Add a fourth chunk to Android reftests


(Release Engineering :: General, defect)

Not set


(Not tracked)



(Reporter: philor, Assigned: philor)




(1 file)

If you look at the logs for the links pasted into bug 663657, where reftests time out after 1200 seconds with no output, you'll see that they are reftest-3.

If you look at the logs for the links pasted into bug 689856, where a job is running along, and then suddenly after 61 minutes it stops in midstream, you'll see that they are reftest-3.

If you look at the total time for Android test jobs, you'll see that it's around 30 minutes per suite, except that reftest-2 is 45 minutes, and reftest-3 is around 60-80 minutes. I'd assert that that's longer than you can hold the attention of a tegra, and we need to add reftest-4 to balance them out to small enough chunks.

Obviously, that's a releng thing, but if I file it there it'll get bounced to you to say whether or not to do it, so just move it there when you agree.
Please define "you".

It sounds fine to me.
Sorry, that was more clear while filing it, where the cc field and the comment field are close together - the you that releng will want to have pre-approve it is jmaher.
This looks like a good thing to do!
Component: Reftest → Release Engineering: Automation (General)
Product: Testing →
QA Contact: catlee
Version: Trunk → other
Attached patch configsSplinter Review
Slightly silly since the real problem is that skip-if(Android) isn't evenly distributed, so R1 does hardly any of its tests and R3 does almost all of them, but porting the reftest manifest parser to buildbot seems... unlikely to go well :)
Assignee: nobody → philringnalda
Attachment #660499 - Flags: review?(aki)
Comment on attachment 660499 [details] [diff] [review]

This looks good for android.
Did you want to do the same thing for android-armv6, or is that one fine?
If so, the relevant code is .
Attachment #660499 - Flags: review?(aki) → review+
You're right, I do - despite the small number of runs so far, it shows ample evidence of needing the same thing.
In production.
Depends on: 791427
Not sure this was a good idea after all - setup time is insane (I'm looking at a 65 minute R1 where the actual step was 20 minutes), and the fix for bug 791427 may have actually been all we needed.
But, despite the still-awful times, it did drop end-to-end time.
Closed: 10 years ago
Resolution: --- → FIXED
Product: → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.