Closed Bug 1053502 Opened 7 years ago Closed 7 years ago

Increase Android 2.3 mochitest chunks

Categories

(Release Engineering :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gbrown, Assigned: gbrown)

References

Details

Attachments

(2 files)

+++ This bug was initially created as a clone of Bug #1028293 +++

In bug 1051131, mochitest-4 is frequently failing due to exceeding the job timeout. I am slightly hesitant to increase the number of chunks because some other chunks are running in a much shorter time. But I don't immediately see an alternative...

I'm thinking of increasing from 12 to 16 chunks.
Assignee: nobody → gbrown
The sad thing is, the chunking is inherently unpredictable, so it's hard to say for sure what effect it'll have on min/max chunk runtime.

FWIW, we should also really look into enabling chunk-by-dir on Android/B2G mochitest-plain at some point. Right now, it's enabled by default on desktop only.
:kmoir -- Do you think the timeouts might be related to bug 1047467?
Flags: needinfo?(kmoir)
Regarding comment #2, no this is not related to bug 1047467 because the mochitests all run on tst-linux64-spot-* instances which are all m1.medium.  These are not the tests I changed to run on c3.xlarge et al.  So this is a different issue. I'll assume that the mochitests don't need a more power instance type than m1.medium and look at the patches.
Flags: needinfo?(kmoir)
Attachment #8472700 - Flags: review?(kmoir) → review+
Attachment #8472701 - Flags: review?(kmoir) → review+
Attachment #8472700 - Flags: checked-in+
Attachment #8472701 - Flags: checked-in+
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Duplicate of this bug: 1051131
See Also: → 1138462
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.