Closed
Bug 790510
Opened 13 years ago
Closed 13 years ago
Add a fourth chunk to Android reftests
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: philor, Assigned: philor)
References
Details
Attachments
(1 file)
|
1.26 KB,
patch
|
mozilla
:
review+
|
Details | Diff | Splinter Review |
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.
| Assignee | ||
Comment 2•13 years ago
|
||
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.
Comment 3•13 years ago
|
||
This looks like a good thing to do!
| Assignee | ||
Updated•13 years ago
|
Component: Reftest → Release Engineering: Automation (General)
Product: Testing → mozilla.org
QA Contact: catlee
Version: Trunk → other
| Assignee | ||
Comment 4•13 years ago
|
||
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 :)
Comment 5•13 years ago
|
||
Comment on attachment 660499 [details] [diff] [review]
configs
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 http://hg.mozilla.org/build/buildbot-configs/file/7d811e29a112/mozilla-tests/config.py#l632 .
Attachment #660499 -
Flags: review?(aki) → review+
| Assignee | ||
Comment 6•13 years ago
|
||
You're right, I do - despite the small number of runs so far, it shows ample evidence of needing the same thing.
| Assignee | ||
Comment 7•13 years ago
|
||
Comment 8•13 years ago
|
||
In production.
| Assignee | ||
Comment 9•13 years ago
|
||
Not sure this was a good idea after all - setup time is insane (I'm looking at a 65 minute R1 where the actual remotereftest.py step was 20 minutes), and the fix for bug 791427 may have actually been all we needed.
| Assignee | ||
Comment 10•13 years ago
|
||
But, despite the still-awful times, it did drop end-to-end time.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•