Confirmed users
656
edits
Sheriffing/Manifest Scheduling: Difference between revisions
Jump to navigation
Jump to search
→Push Continuity
| Line 27: | Line 27: | ||
The main issue is that under "manifest scheduling" the same mochitest-1 task on push A, will run a completely different set of tests as it does on push B. In other words, it will no longer be possible to filter Treeherder by task label to identify test-level regressions (though it should still work for many types of infra related issues). Instead, sheriffs will need to filter Treeherder by "test path". Read this [https://medium.com/@armenzg/filter-treeherder-jobs-by-test-or-manifest-path-af0e1ae74e61 blog post] for details of the feature. | The main issue is that under "manifest scheduling" the same mochitest-1 task on push A, will run a completely different set of tests as it does on push B. In other words, it will no longer be possible to filter Treeherder by task label to identify test-level regressions (though it should still work for many types of infra related issues). Instead, sheriffs will need to filter Treeherder by "test path". Read this [https://medium.com/@armenzg/filter-treeherder-jobs-by-test-or-manifest-path-af0e1ae74e61 blog post] for details of the feature. | ||
[[File:Test path.png | [[File:Test path.png|UI showing active filter for a test path]] | ||
[[File:Filtered tasks.png | [[File:Filtered tasks.png|Push showing tasks that executed the same test path]] | ||