666756 - self-serve should be able to "nerf" jobs (suppress dependents)

Status: RESOLVED WONTFIX

(Release Engineering :: General, enhancement, P3)

Description

[Steve Fink [:sfink] [:s:]]

The usual use case would be suppressing jobs for a non-Try tree, without mangling the objdir by cancelling the builds. Currently, if you cancel the build you'll mess things up, but you can't cancel the resulting tests until they get queued up, so you have to wait around for each batch of tests to appear and then pounce on them.

Comment 1

[Chris AtLee [:catlee]]

Would we need this if we had bug 658934 (triggering clobbers after cancelling builds)?

Comment 2

[Steve Fink [:sfink] [:s:]]

(In reply to Chris AtLee [:catlee] from comment #1)
> Would we need this if we had bug 658934 (triggering clobbers after
> cancelling builds)?

I don't think so. Or at least, the priority should be dropped way lower. You might still prefer to nerf builds if 2 dep builds are substantially faster than 1 clobber build, and there's a race where you could cancel a build but before it's cancelled it finishes far enough to trigger off the resulting test jobs. (As long as 'make check' is part of the build job, this is actually a large race window, since the test jobs don't wait for make check to finish.)

That said, I can't think of a reason why the added complexity would be worth it. Maybe in a future world where our build system does proper full-tree dependencies so that dep builds are really fast and reliable, this might again become a substantial win.

Comment 4

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Found in triage. Moving to "Tools", as that feels closest, but if this should be in "GeneralAutomation", please re-triage.

Comment 5

[[e-mail] (:bhearsum)]

Probably won't be fixing this because self serve is going to be deprecated after all scheduling moves to Taskcluster.