Not mutually exclusive, by stand up a new "suite" I meant put the tests in a different location from the taskgraph tests and use a different `subsuite` value. So maybe ~15 minutes of extra effort. Also even if we get taskgraph generation back down to 20s somehow, these would still be *very* expensive tests compared to the others that are usually measured in milliseconds.
Bug 1640902 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Nathan Froyd [:froydnj] from comment #2) > Maybe we could instead invest some effort into making taskgraph generation faster? Not mutually exclusive, by stand up a new "suite" I meant put the tests in a different location from the taskgraph tests and use a different `subsuite` value. So maybe ~10 minutes of extra effort. Also even if we get taskgraph generation back down to 20s somehow, these would still be *very* expensive tests compared to the others that are usually measured in milliseconds. (In reply to Aki Sasaki [:aki] (he/him) (UTC-7) from comment #3) > When hacking on `taskgraph`, we find it useful to run [taskgraph-gen and taskgraph-diff](https://hg.mozilla.org/build/braindump/file/tip/taskcluster/taskgraph-diff). These build various release graphs and on-push graphs on various branches. By generating these graphs against both a clean and patched revision, we can diff to pinpoint what we're changing. > > A while back, I wondered if we could generate these graphs whenever the taskgraph changes. We could then diff against the previous indexed taskgraph generation task's artifacts. These diffs would likely be more useful to humans than automation. This would be awesome. See also bug 1409733.
(In reply to Nathan Froyd [:froydnj] from comment #2) > Maybe we could instead invest some effort into making taskgraph generation faster? Not mutually exclusive, by stand up a new "suite" I meant put the tests in a different location from the taskgraph tests and use a different `subsuite` value. So maybe ~10 minutes of extra effort. Also even if we get taskgraph generation back down to 20s somehow, these would still be *very* expensive tests compared to the others that are usually measured in milliseconds. See also bug 1617598. (In reply to Aki Sasaki [:aki] (he/him) (UTC-7) from comment #3) > When hacking on `taskgraph`, we find it useful to run [taskgraph-gen and taskgraph-diff](https://hg.mozilla.org/build/braindump/file/tip/taskcluster/taskgraph-diff). These build various release graphs and on-push graphs on various branches. By generating these graphs against both a clean and patched revision, we can diff to pinpoint what we're changing. > > A while back, I wondered if we could generate these graphs whenever the taskgraph changes. We could then diff against the previous indexed taskgraph generation task's artifacts. These diffs would likely be more useful to humans than automation. This would be awesome. See also bug 1409733.