Open
Bug 1665523
Opened 4 years ago
Updated 4 years ago
Runnable jobs not showing when using test path filtering
Categories
(Tree Management :: Treeherder: Frontend, defect)
Tree Management
Treeherder: Frontend
Tracking
(Not tracked)
NEW
People
(Reporter: CosminS, Unassigned)
References
Details
Runnable jobs are not shown on a push that a test didn't initially ran on.
Steps to repro:
- open a TH push with all jobs showing, eg: https://treeherder.mozilla.org/#/jobs?repo=autoland&revision=59fd9216fd8121d332d4b99da79c9b59bd1e42d5
- add a test path filter, eg: browser/components/newtab/test/browser/
- click the add new jobs, no runnable jobs are showing
- remove the test path filter and all the runnable jobs are showing
This does not happen on a push that scheduled that test initially, for eg the push right below https://tinyurl.com/yy9686y9
It would come in handy for the sheriffs to be able to trigger jobs that contain a specific test in order to better track failures on tree when necessary.
Comment 1•4 years ago
|
||
This is likely because we fetch the manifests_by_task.gz
file. I am fairly sure this only has the initial-run tasks/manifests. So we'd need to expand the coverage of this filtering to include a complete list. I don't know off the top of my head where such a list resides. But there probably IS one in Taskcluster somewhere.
You need to log in
before you can comment on or make changes to this bug.
Description
•