[resource timing] Improve document.domain tests (reland)

[chromium-wpt-export-bot]

This CL is a fixed up reland of [1], which was reverted due to a rename
in entry-invariants.js that it was relying on.

[1] https://chromium-review.googlesource.com/c/chromium/src/+/2878852

Bug: 1171767, 1208054
Change-Id: I436bf6973e4399d142ce45e77c07f26d0e7e1cd1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2888667
Reviewed-by: Tom McKee <[email protected]>
Commit-Queue: Yoav Weiss <[email protected]>
Cr-Commit-Position: refs/heads/master@{#881945}

[wpt-pr-bot]

The review process for this patch is being conducted in the Chromium project.

[yoavweiss]

Looking at the Chrome and Firefox logs, I don't see any issue with the test this actually adds... Halp?

[KyleJu]

Looking at the Chrome and Firefox logs, I don't see any issue with the test this actually adds... Halp?

Looking at the logs, it looks like that unrelated tests are triggered and run, which led to timeout. I think it is safe to force merge.

[KyleJu]

@jpchase timeout on Firefox and Chrome and seems to be unrelated. Could you admin merge?

[jpchase]

@jpchase timeout on Firefox and Chrome and seems to be unrelated. Could you admin merge?

I would agree, except the reverted version of the PR (#28901) also had timeouts that appear to be similar:
https://github.com/web-platform-tests/wpt/pull/28901/checks?check_run_id=2558118969

Meanwhile, other PRs have recently ran successfully (e.g. #28963).

@KyleJu would you rebase and rerun the checks on this PR? I'd like to see if that can rule out the timeout being somehow related to these changes (even though we don't have reason to suspect so).

[KyleJu]

@jpchase timeout on Firefox and Chrome and seems to be unrelated. Could you admin merge?

I would agree, except the reverted version of the PR (#28901) also had timeouts that appear to be similar:
https://github.com/web-platform-tests/wpt/pull/28901/checks?check_run_id=2558118969

Meanwhile, other PRs have recently ran successfully (e.g. #28963).

Note that Chrome/Firefox checks are running against PR changes. so #28963 is probably not indicative of the status of checks in this PR because they are running different sets of tests. I am suspecting common/get-host-info.sub.js is the reason why so many unrelated tests are triggered and run

@KyleJu would you rebase and rerun the checks on this PR? I'd like to see if that can rule out the timeout being somehow related to these changes (even though we don't have reason to suspect so).

Yea rebase and rerun sound like a good idea.

[foolip]

Perhaps there are multiple things going on here, but I see at least some of the stability jobs have timed out, which is #7660. When this happens, I just link to that issue and admin merge.

@past FYI, this is a pretty common source of issues, and pretty high up on my list of things we should fix in WPT CI.

[KyleJu]

@jpchase Still timing out. I think we can admin merge this PR

[jpchase]

@jpchase Still timing out. I think we can admin merge this PR

Yes, agreed to admin merge.