1829047 - do not schedule tasks that have no active tests when pushing to try with custom paths

Status: RESOLVED FIXED

(Testing :: General, enhancement, P2)

Description

[Joel Maher ( :jmaher ) (UTC -8)]

there are a few cases where pushing to try and scheduling a path can yield a list of tasks that are orange due to no tasks ran. Here is an example:
./mach try fuzzy -q "'debug | 'opt" browser/base/content/test/static toolkit/components/pdfjs/test

One major cause here is we have manifests that reference tests from another directory:
https://searchfox.org/mozilla-central/source/devtools/client/framework/test/browser.ini#172-176

So our logic for chunking/test selection doesn't account for that.

A simple fix is to keep track of these manifests that reference other directories and are active for the given task, then when we find a scenario that we are running specific paths, we can check to see if the paths are referenced in the other directories- if they are we know they are active and can keep scheduling the task, if there are no references then we can remove the task from the list to be scheduled.

Comment 1

[Joel Maher ( :jmaher ) (UTC -8)]

Attachment: Bug 1829047 - do not schedule task if all tests are skipped. r=ahal!

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/da2fe40c90e3
do not schedule task if all tests are skipped. r=ahal

Comment 3

[Narcis Beleuzu [:NarcisB]]

https://hg.mozilla.org/mozilla-central/rev/da2fe40c90e3