Open Bug 1644462 Opened 4 years ago Updated 4 years ago

New wpt failures in /css/cssom/stylesheet-same-origin.sub.html

Categories

(Core :: DOM: CSS Object Model, defect)

defect

Tracking

()

People

(Reporter: wpt-sync, Unassigned)

References

Details

(Whiteboard: [wpt])

Syncing wpt PR 23771 found new untriaged test failures in CI

Tests Affected

New Tests That Don't Pass

/css/cssom/stylesheet-same-origin.sub.html
Origin-clean check in cross-origin CSSOM Stylesheets (redirect from cross-origin to same-origin): FAIL (Chrome: PASS, Safari: FAIL)
Origin-clean check in loading error CSSOM Stylesheets: FAIL (Chrome: PASS, Safari: FAIL)

CI Results

Gecko CI (Treeherder)
GitHub PR Head

Notes

These updates will be on mozilla-central once bug 1640914 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.

I am trying to understand what happened on the merge, but I have no idea.

According to the CI result in comment 0, the actual error on stylesheet-same-origin.sub.html is;

Unable to find any tests at the path(s):
(snip)
/builds/worker/workspace/build/tests/web-platform/tests/css/cssom/stylesheet-same-origin.sub.html

It looks like either the PR issue or an infra issue. Moreover, the two test cases in question have been marked as FAIL in stylesheet-same-origin.sub.html.ini before the merge.

James, is this one of failures that was misrecognized as a new failure?

Flags: needinfo?(james)

The error is misleading; there seems to be a bug in the test scheduling that we end up starting various wpt jobs when in fact these are only testharness tests. Those jobs are passing, so I agree that these tests were already passing. It seems like a bug in the sync that we thought these were new failures.

That said these subtests are the only ones in the file that are failing, so it seems like a real bug that we should triage.

Flags: needinfo?(james)

Great, thanks!

Thought it's not new failures, I am going to re-use this bug. :)

Severity: -- → S3
You need to log in before you can comment on or make changes to this bug.