Open Bug 1957100 Opened 7 months ago Updated 6 months ago

skip-fails doesn't work well when we have relative paths in a manifest

Categories

(Testing :: General, defect, P2)

defect

Tracking

(Not tracked)

People

(Reporter: jmaher, Unassigned)

Details

here is an example of a test living in 2 manifests:

browser/base/content/test/static/browser.toml
["browser_all_files_referenced.js"]
devtools/client/framework/test/browser.toml
["../../../../browser/base/content/test/static/browser_all_files_referenced.js"]

if the test is failing in the devtools/client/framework/test/browser.toml manifest, we end up not skipping it. This could be because we make some decisions to work most of the time and save a lot of logic/code to pick the first or last manifest in a multi manifest scenario.

Either way, to make skip-fails work more reliably we should consider addressing this. This is an edge case as it appears there are 9 instances of this currently in the tree.

The severity field is not set for this bug.
:jmaher, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(jmaher)
Severity: -- → S2
Flags: needinfo?(jmaher)
Priority: -- → P2
You need to log in before you can comment on or make changes to this bug.