-
-
Notifications
You must be signed in to change notification settings - Fork 37.1k
test-quic-writer-stop-sending is flaky (for me) #63309
Copy link
Copy link
Closed
Labels
flaky-testIssues and PRs involving tests that fail intermittently in CI.Issues and PRs involving tests that fail intermittently in CI.linuxIssues and PRs related to the Linux platform.Issues and PRs related to the Linux platform.quicIssues and PRs related to the QUIC transport implementation.Issues and PRs related to the QUIC transport implementation.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
Description
Activity
Metadata
Metadata
Assignees
Labels
flaky-testIssues and PRs involving tests that fail intermittently in CI.Issues and PRs involving tests that fail intermittently in CI.linuxIssues and PRs related to the Linux platform.Issues and PRs related to the Linux platform.quicIssues and PRs related to the QUIC transport implementation.Issues and PRs related to the QUIC transport implementation.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
Test
test-quic-writer-stop-sending
Platform
Linux x64
Console output
Build links
Additional information
On my system, the timeout of 100ms is insufficient for the stream state to propagate, and this assertion fails ~100% of the time. Extending the timeout arbitrarily to 1000ms appears to settle things.
cc: @nodejs/quic