The default bug view has changed. See this FAQ.

Increase Android 2.3 mochitest chunks, for aws

RESOLVED FIXED

Status

Release Engineering
General Automation
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: gbrown, Assigned: gbrown)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Assignee)

Description

3 years ago
Android 2.3 mochitests run a little longer on aws, as compared to ix slaves. From recent results on ash, it looks like we might need to run more chunks, if we are going to be using aws slaves.

https://tbpl.mozilla.org/php/getParsedLog.php?id=42064193&tree=Ash&full=1

Updated

3 years ago
Blocks: 1024091
(Assignee)

Comment 1

3 years ago
Created attachment 8443647 [details] [diff] [review]
Increase to 12 Android 2.3 mochitest chunks (buildbot)

Most of those armv6 mochitests completed in a little under 1 hour, but the one that did not complete was not nearly finished, so I'm guessing we need about 12 chunks.
Attachment #8443647 - Flags: review?(kmoir)
(Assignee)

Comment 2

3 years ago
Created attachment 8443650 [details] [diff] [review]
Increase to 12 Android 2.3 mochitest chunks (mozharness)
Attachment #8443650 - Flags: review?(kmoir)

Updated

3 years ago
Attachment #8443650 - Flags: review?(kmoir) → review+

Updated

3 years ago
Attachment #8443647 - Flags: review?(kmoir) → review+

Updated

3 years ago
Attachment #8443647 - Flags: checked-in+

Updated

3 years ago
Attachment #8443650 - Flags: checked-in+
Something here is in production In production
(Assignee)

Comment 4

3 years ago
Verified armv6 mochitest chunks on Ash: First run of all chunks completed without exceeding max time.

For M5, it was a close call -- completed in 56 minutes. Rather than increasing chunks further, I will look at skipping the longest running test, which ran for 5+ minutes.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.