1732336 - New wpt failures in /css/css-pseudo/highlight-paired-cascade-004.html

Status: NEW

(Core :: Layout: Generated Content, Lists, and Counters, defect)

Description

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Syncing wpt PR 30813 found new untriaged test failures in CI

Tests Affected

New Tests That Don't Pass

/css/css-pseudo/highlight-paired-cascade-004.tentative.html: TIMEOUT (Chrome: PASS, Safari: FAIL)

CI Results

Gecko CI (Treeherder)
GitHub PR Head

Notes

These updates will be on mozilla-central once bug 1732067 lands.

Note: this bug is for tracking fixing the issues and is not
owned by the wpt sync bot.

This bug is linked to the relevant tests by an annotation in
https://github.com/web-platform-tests/wpt-metadata. These annotations
can be edited using the wpt interop dashboard
https://jgraham.github.io/wptdash/

If this bug is split into multiple bugs, please also update the
annotations, otherwise we are unable to track which wpt issues are
already triaged. Resolving as duplicate or closing this issue should
be cause the bot to automatically update or remove the annotation.

Comment 1

[Daniel Holbert [:dholbert]]

Hmm, this seems to be passing in-tree -- we don't have any .ini failure-annotation file for this test -- but it is still timing out on wpt.fyi as shown here: https://wpt.fyi/results/css/css-pseudo/highlight-cascade/highlight-paired-cascade-004.html

I don't know offhand why it'd be timing out.

Comment 2

[Daniel Holbert [:dholbert]]

(maybe it has something to do with the fact that the test updates its location.href dynamically?

https://searchfox.org/mozilla-central/rev/b41bb321fe4bd7d03926083698ac498ebec0accf/testing/web-platform/tests/css/css-pseudo/highlight-cascade/highlight-paired-cascade-004.html#27

<script>location.href = "#:~:text=quick";</script>

I wonder if that navigation confuses something about our test harness on wpt.fyi such that the test falls over or we can't tell whether it passed.

Comment 3

[Daniel Holbert [:dholbert]]

(See also bug 1857144 comment 3 about another wpt that's dynamically updating its window.location.href, which I suspect might be going against what WPTs typically expect to happen...)