Skip to content

test-quic-writer-stop-sending is flaky (for me) #63309

Description

@Renegade334

Test

test-quic-writer-stop-sending

Platform

Linux x64

Console output

=== release test-quic-writer-stop-sending ===
Path: parallel/test-quic-writer-stop-sending
node:internal/modules/run_main:107
    triggerUncaughtException(
    ^

AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:

true !== false

    at file:///home/renegade/git/node/test/parallel/test-quic-writer-stop-sending.mjs:54:1 {
  generatedMessage: true,
  code: 'ERR_ASSERTION',
  actual: true,
  expected: false,
  operator: 'strictEqual',
  diff: 'simple'
}

Node.js v27.0.0-pre

Build links

$ git rev-parse HEAD
843dc5f0d5ade521552684a161b4f3798e6baa99
$ tail -n1 config.status
exec ./configure --v8-enable-temporal-support --experimental-quic
$ uname -a
Linux venus 6.8.0-111-generic #111-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 11 23:16:02 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux
$ g++ -v
gcc version 13.3.0 (Ubuntu 13.3.0-6ubuntu2~24.04.1)

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    flaky-testIssues and PRs involving tests that fail intermittently in CI.linuxIssues and PRs related to the Linux platform.quicIssues and PRs related to the QUIC transport implementation.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions