Closed Bug 1665085 Opened 4 years ago Closed 2 months ago

Test failed (timeout): wpt/resource-timing/buffer-full-when-populate-entries

Categories

(Core :: Networking, defect)

80 Branch
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: noam.helfman, Unassigned)

References

(Blocks 1 open bug)

Details

Steps to reproduce:

Follow https://github.com/web-platform-tests/wpt steps to setup test env

wpt serve

Open local URL:
http://web-platform.test:8000/resource-timing/buffer-full-when-populate-entries.html

Actual results:

Test failure with the following message:

Timeout	Test that a buffer full event does not bubble and that resourcetimingbufferfull is called only once per overflow	Test timed out

Expected results:

Test pass:

Pass	Test that a buffer full event does not bubble and that resourcetimingbufferfull is called only once per overflow
Summary: Test failed: wpt/resource-timing/buffer-full-then-increased → Test failed (timeout): wpt/resource-timing/buffer-full-when-populate-entries

Setting a component for this issue in order to get the dev team involved.
If you feel it's an incorrect one please feel free to change it to a more appropriate one.

Component: Untriaged → DOM: Core & HTML
Product: Firefox → Core

What is the point of filing these bugs? We have the failures annotated here.

Do you plan to work on fixing this? Otherwise having bugs on file per each failing test is probably not helpful.

Flags: needinfo?(noam.helfman)

What's the best way to file bugs on failing tests to achieve better compatibility. Having failure expectations is fine, but actually passing the tests in all engines would be better :)

(In reply to Yoav Weiss from comment #3)

What's the best way to file bugs on failing tests to achieve better compatibility. Having failure expectations is fine, but actually passing the tests in all engines would be better :)

In general, it would be better to rely on the in-tree copy of WPT for steps to reproduce and to articulate what's wrong beyond how it manifests in the WPT output.

Confirming based on the in-tree annotation.

Severity: -- → S3
Status: UNCONFIRMED → NEW
Ever confirmed: true
Component: DOM: Core & HTML → Networking

Clear a needinfo that is pending on an inactive user.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit BugBot documentation.

Flags: needinfo?(noam.helfman)

Closing this bug as Incomplete, as I am not sure what is the expected action here.
We already have a system to track failing WPTs

Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.