1834319 - Investigate `popover` tests failing only on Android release

Status: RESOLVED FIXED

(Core :: DOM: Core & HTML, defect)

Comment 1

[Mirko Brodesser (:mbrodesser-Igalia)]

popover-inside-display-none.html:

• If only that test is executed on Try, it passes: https://treeherder.mozilla.org/jobs?repo=try&revision=005073672ba023f28550ab7ab94718879076eb98&selectedTaskRun=ffJk4zLaSfqvVep3czoftw.0.
• In an older Try run, the test times out, after the preceding test timed out: https://treeherder.mozilla.org/logviewer?job_id=416535756&repo=mozilla-central&lineNumber=6413. The same happened during a Try run from today: https://treeherder.mozilla.org/logviewer?job_id=417767837&repo=try&lineNumber=1899.

Therefore, it could be that the timeout on Try was a consequence of the previous timeout.

Comment 2

[Mirko Brodesser (:mbrodesser-Igalia)]

James: ./mach try fuzzy seems to lack support for enabling more logging (e.g. via --debug-test) for this case, is there another convenient way to enable more logging?

Comment 3

[Mirko Brodesser (:mbrodesser-Igalia)]

Aryx: can you answer #c2 or recommend someone who might know?

Comment 4

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

To workaround the issue, the value of the variable storing the switch's state can be changed to True here.

Julian's notes might also be of interest.

Comment 5

[Mirko Brodesser (:mbrodesser-Igalia)]

Aryx: thanks, giving it a Try.

Thanks for the link to the notes too, didn't know them.

Comment 6

[Mirko Brodesser (:mbrodesser-Igalia)]

(In reply to Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout) from comment #4)

To workaround the issue, the value of the variable storing the switch's state can be changed to True here.

Julian's notes might also be of interest.

Try run for this: https://treeherder.mozilla.org/jobs?repo=try&revision=caea0986dbce8004d317e94dd22f46e2ab8c7e14.

Comment 7

[Mirko Brodesser (:mbrodesser-Igalia)]

Try run for this: https://treeherder.mozilla.org/jobs?repo=try&revision=caea0986dbce8004d317e94dd22f46e2ab8c7e14.

The failure reproduced there, but nothing new was logged. Investigating other logging options.

Comment 8

[Mirko Brodesser (:mbrodesser-Igalia)]

./mach --log-mach-level=debug [...] could provide more insight. An attempt to hack that in is at https://treeherder.mozilla.org/jobs?repo=try&revision=566ceb799ca5ca6db9f117e5c70cf482b7803e6a.

Comment 9

[Mirko Brodesser (:mbrodesser-Igalia)]

(In reply to Mirko Brodesser (:mbrodesser-Igalia) from comment #8)

./mach --log-mach-level=debug [...] could provide more insight. An attempt to hack that in is at https://treeherder.mozilla.org/jobs?repo=try&revision=566ceb799ca5ca6db9f117e5c70cf482b7803e6a.

The hack didn't enable the desired logging.

For the record: changing https://searchfox.org/mozilla-central/source/testing/mozharness/scripts/web_platform_tests.py#333-347 could work (Thanks to jgraham for the hint).

Pausing work on this since the test failure is expected to disappear with bug 1838556.

Comment 10

[Mirko Brodesser (:mbrodesser-Igalia)]

Symptoms fixed by bug 1838556.