Closed Bug 1151699 Opened 7 years ago Closed 7 years ago
Do something about the number of builds and tests run on Cypress
Dunno what it actually needs, since it's just a stew of codenames, but I'm pretty sure it doesn't need what it has, ten or eleven full sets of desktop and Android Firefox builds and tests per day, when the only thing changing between them is a gaia commit, and the Gecko that they are rebuilding and retesting is nine days old. Could be that it wants per-product builds, or whatever it is we actually call only building b2g on commits which only touch b2g/ while building everything on commits that touch Gecko, or it could be that it only wants b2g builds and never wants Android or Firefox, or it could be that it only wants some subset of b2g builds.
We only needs b2g device builds, and there's no interesting tests to run on cypress that we don't run on m-c. It's even very possible that some are broken on cypress because I landed hacks on this "experimental" branch without updating patches until I land back on m-c.
We could just disable these tests entirely, really. There's not a lot happening on cypress, and there are only a few more minor patches that may or may not land on it only.
I closed Cypress, because I can't spend all day every day killing builds to keep it from running thousands of unwanted jobs. If it was a contributor pushing to try like that who kept going after being warned, we would remove his push access.
Severity: major → blocker
(In reply to Fabrice Desré [:fabrice] from comment #1) > We only needs b2g device builds Does this include the emulator builds? Or just nexus/flame/dolphin device builds?
Actually, dolphin appears to be limited to non-twig branches, so it's not currently running on cypress anyway.
(In reply to Michael Shal [:mshal] from comment #4) > (In reply to Fabrice Desré [:fabrice] from comment #1) > > We only needs b2g device builds > > Does this include the emulator builds? Or just nexus/flame/dolphin device > builds? I'm fine with doing only the nexus/flame builds.
I just checked this with builder_lists.sh and it appears to be correct, but I'd appreciate it if you could double-check it.
Attachment #8590399 - Flags: review?(coop)
Comment on attachment 8590399 [details] [diff] [review] disable-cypress Review of attachment 8590399 [details] [diff] [review]: ----------------------------------------------------------------- LGTM (using larch as the example for comparison)
Attachment #8590399 - Flags: review?(coop) → review+
Comment on attachment 8590399 [details] [diff] [review] disable-cypress https://hg.mozilla.org/build/buildbot-configs/rev/9fef2e7bb9cf
Attachment #8590399 - Flags: checked-in+
We should be able to turn cypress back on after a reconfig.
Seems we need to explicitly disable tests too, otherwise the travis checks aren't happy.
Comment on attachment 8591043 [details] [diff] [review] disable-cypress-tests https://hg.mozilla.org/build/buildbot-configs/rev/9ccdc8a458ec
Attachment #8591043 - Flags: checked-in+
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.