Open Bug 1943674 Opened 14 days ago Updated 14 days ago

Resolve why --power-test causes permafails on certain mobile platforms and browsers

Categories

(Testing :: Raptor, defect)

defect

Tracking

(Not tracked)

People

(Reporter: aglavic, Unassigned)

References

(Depends on 1 open bug)

Details

(Whiteboard: [fxp])

For the speedometer2 test on s24 and p6 for geckoview_example, chrome-m and car running the test with --power-test causes the tests to perma fail.
The current fix has been to just remove the --power-test for the combinations that are failing since but this problem may come up for other platforms and browsers.

Depends on: 1919024
Whiteboard: [fxp]

The failure happens because there's data in the extra section of the browsertime results. This causes it to take some different paths in results/output that aren't expected for benchmarks. No clean way to resolve it without moving the logic to python support scripts.

You need to log in before you can comment on or make changes to this bug.