Filed by: rvandermeulen [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=588346182&repo=mozilla-release&task=f4cF5AhCRneCC49EBmUE4Q.0
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/f4cF5AhCRneCC49EBmUE4Q/runs/0/artifacts/public/logs/live_backing.log

This is hitting on the 155.0-build1 release graph.

136.0b6 is technically the most correct version, I guess, because it's the first one we shipped, and updates could theoretically be done from that version to an RC. In practice this probably doesn't happen, and the compare-directories.py doesn't support the scenario. Additionally, it's probably better to test an old version on the release channel than on the beta channel, as there is a much greater chance of updates actually happening from 136.0 -> latest.

136.0b6 is technically the most correct version, I guess, because it's the first one we shipped, and updates could theoretically be done from that version to an RC. In practice this probably doesn't happen, and the compare-directories.py doesn't support the scenario. Additionally, it's probably better to test an old version on the release channel than on the beta channel, as there is a much greater chance of updates actually happening from 136.0 -> latest.

firefox-beta Uplift Approval Request

• User impact if declined/Reason for urgency: none
• Code covered by automated testing?: no
• Fix verified in Nightly?: no
• Needs manual QE testing?: no
• Steps to reproduce for manual QE testing: n/a
• Risk associated with taking this patch: low
• Explanation of risk level: Only affects tier2 tests, verified locally
• String changes made/needed?: n/a
• Is Android affected?: no

136.0b6 is technically the most correct version, I guess, because it's the first one we shipped, and updates could theoretically be done from that version to an RC. In practice this probably doesn't happen, and the compare-directories.py doesn't support the scenario. Additionally, it's probably better to test an old version on the release channel than on the beta channel, as there is a much greater chance of updates actually happening from 136.0 -> latest.

firefox-release Uplift Approval Request

• User impact if declined/Reason for urgency: fix failing tests
• Code covered by automated testing?: no
• Fix verified in Nightly?: no
• Needs manual QE testing?: no
• Steps to reproduce for manual QE testing: n/a
• Risk associated with taking this patch: low
• Explanation of risk level: Only affects tier2 tests, verified locally
• String changes made/needed?: n/a
• Is Android affected?: no

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