mochitest-6 is frequently timing out these days. It just so happens to be the chunk that content/media runs ins (which was enabled during this release cycle). We need to add more chunks to spread these out more. Setting this to critical because green M6 runs are becoming the exception more than the norm lately.
Do you have any suggestions as to how many chunks we should use?
Assignee: nobody → ryanvm
Status: NEW → ASSIGNED
Attachment #8500589 - Flags: review?(catlee)
Completely arbitrary, fwiw. Given the unpredictability of our chunking, I can't say for sure if 20 is enough until it's in production :(
I was hoping to go to 25 (since re-enabling the dom-level* tests is going to increase the total number of tests run by another ~25%), but test-masters.sh says that's a no-go: AssertionError: tst-linux64-spot-840 has 4125 builders; limit is 4084 Playing around with things a bit, it appears that 22 is the limit before having to add more masters (which would leave us at 4080/4084 builders). Chris, what should we do here? Bump the chunks up against the limit or bite the bullet and add more masters?
I'd rather avoid bumping the limit, since that will prevent us from enabling more Mulet builds/tests, which the B2G really wants.
Additionally, I'm almost certainly going to need to add more Android 2.3 chunks in order to re-enable the dom-level mochitests there as well.
Comment on attachment 8500589 [details] [diff] [review] increase the number of chunks to 20 https://hg.mozilla.org/build/buildbot-configs/rev/d997f6adb14d
Attachment #8500589 - Flags: checked-in+
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.