镜像站点 · 本页由第三方 GitHub 只读镜像提供，非 GitHub 官方站点，不接受任何登录或凭据输入。前往 github.com
Skip to content

test/parallel/test-worker-http2-stream-terminate.js #43084

Closed
#45438
Closed
test/parallel/test-worker-http2-stream-terminate.js#43084
#45438
Labels
async_hooksIssues and PRs related to the async hooks subsystem.flaky-testIssues and PRs involving tests that fail intermittently in CI.

Description

@RaisinTen
RaisinTen
opened on May 13, 2022

Test

test-worker-http2-stream-terminate

Platform

node-test-binary-windows-js-suites

Console output

21:46:33 not ok 773 parallel/test-worker-http2-stream-terminate
21:46:33   ---
21:46:33   duration_ms: 16.879
21:46:33   severity: crashed
21:46:33   exitcode: 3221225477
21:46:33   stack: |-
21:46:33     Error: async hook stack has become corrupted (actual: 5, expected: 28983)
21:46:33      1: 00007FF67A2BAD6F node_api_throw_syntax_error+174655
21:46:33      2: 00007FF67A2B2E3C node_api_throw_syntax_error+142092
21:46:33      3: 00007FF67A1B756A node::PromiseRejectCallback+3658
21:46:33      4: 00007FF67A2E07E3 v8::internal::compiler::Operator::EffectOutputCount+547
21:46:33      5: 00007FF67AC9419D v8::internal::Builtins::code+248653
21:46:33      6: 00007FF67AC93DA9 v8::internal::Builtins::code+247641
21:46:33      7: 00007FF67AC9406C v8::internal::Builtins::code+248348
21:46:33      8: 00007FF67AC93ED0 v8::internal::Builtins::code+247936
21:46:33      9: 000002503B14853D 
21:46:33   ...

Platform

smartos20-64

Console output

19:50:30 not ok 2984 parallel/test-worker-http2-stream-terminate
19:50:30   ---
19:50:30   duration_ms: 17.692
19:50:30   severity: fail
19:50:30   exitcode: 1
19:50:30   stack: |-
19:50:30     Error: async hook stack has become corrupted (actual: 335, expected: 368)
19:50:30      1: 133dc99 node::AsyncHooks::FailWithCorruptedAsyncStack(double) [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
19:50:30      2: 1305294 node::AsyncWrap::PopAsyncContext(v8::FunctionCallbackInfo<v8::Value> const&) [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
19:50:30      3: 16630a1 v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo) [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
19:50:30      4: 1662637 v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<false>(v8::internal::Isolate*, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::FunctionTemplateInfo>, v8::internal::Handle<v8::internal::Object>, v8::internal::BuiltinArguments) [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
19:50:30      5: 1662b57 v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
19:50:30      6: fffffc7fb9b07b39 
19:50:30      7: fffffc7fb1c5622a 
19:50:30      8: fffffc7fb1c56b14 
19:50:30      9: fffffc7fb1c5b4f9 
19:50:30     10: fffffc7fb9a8ba90 
19:50:30     11: fffffc7fb1c73b67 
19:50:30     12: 1fe02dc Builtins_JSEntryTrampoline [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
19:50:30     13: 1fe0003 Builtins_JSEntry [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
19:50:30     14: 174b022 v8::internal::(anonymous namespace)::Invoke(v8::internal::Isolate*, v8::internal::(anonymous namespace)::InvokeParams const&) [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
19:50:30     15: 174c094 v8::internal::Execution::Call(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>*) [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
19:50:30     16: 161e1e0 v8::Function::Call(v8::Local<v8::Context>, v8::Local<v8::Value>, int, v8::Local<v8::Value>*) [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
19:50:30     17: 12ed4d6 node::InternalMakeCallback(node::Environment*, v8::Local<v8::Object>, v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*, node::async_context) [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
19:50:30     18: 12ed6ba node::MakeCallback(v8::Isolate*, v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*, node::async_context) [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
19:50:30     19: 1337bf3 node::Environment::CheckImmediate(uv_check_s*) [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
19:50:30     20: 1fbbf29 uv__run_check [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
19:50:30     21: 1fb44c4 uv_run [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
19:50:30     22: 12ee776 node::SpinEventLoop(node::Environment*) [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
19:50:30     23: 14bdeaf node::worker::Worker::Run() [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
19:50:30     24: 14be439 node::worker::Worker::StartThread(v8::FunctionCallbackInfo<v8::Value> const&)::{lambda(void*)#1}::_FUN(void*) [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
19:50:30     25: fffffc7fef036b6c _thrp_setup [/lib/amd64/libc.so.1]
19:50:30     26: fffffc7fef036e80 _lwp_start [/lib/amd64/libc.so.1]
19:50:30   ...

Platform

freebsd12-x64

Console output

06:15:51 not ok 2822 parallel/test-worker-http2-stream-terminate
06:15:57   ---
06:15:57   duration_ms: 7.851
06:15:57   severity: fail
06:15:57   exitcode: 1
06:15:57   stack: |-
06:15:57     Error: async hook stack has become corrupted (actual: 11, expected: 10888)
06:15:57      1: 0x3349f06 node::AsyncHooks::FailWithCorruptedAsyncStack(double) [/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/out/Release/node]
06:15:57      2: 0x32e17ad node::AsyncHooks::pop_async_context(double) [/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/out/Release/node]
06:15:57      3: 0x32ee439 node::AsyncWrap::PopAsyncContext(v8::FunctionCallbackInfo<node::AsyncWrap::PopAsyncContext::Value> const&) [/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/out/Release/node]
06:15:57      4: 0x35b1b28 v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo) [/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/out/Release/node]
06:15:57      5: 0x35b163e v8::internal::Isolate*<v8::internal::Object> v8::internal::Builtins::InvokeApiFunction(v8::internal::Isolate*, bool, v8::internal::Handle<v8::internal::HeapObject>(int, v8::internal::Object*, v8::internal::HeapObject) [/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/out/Release/node]
06:15:57   ...

Build links

Additional information

No response

Activity

  1. RaisinTen
    added
    flaky-testIssues and PRs involving tests that fail intermittently in CI.
    on May 13, 2022

  2. F3n67u commented on May 29, 2022

    @F3n67u
    F3n67u
    on May 29, 2022
    Contributor

    This flaky test causes a lot of Jenkins build failure, see nodejs/reliability#292. Can we mark this test as flaky?

  3. RaisinTen commented on May 30, 2022

    @RaisinTen
    RaisinTen
    on May 30, 2022
    MemberAuthor

    Temporarily marking the test flaky until someone comes up with a proper fix sounds reasonable to me given that it is causing so many CI failures.

  4. mhdawson commented on Jun 14, 2022

    @mhdawson
    mhdawson
    on Jun 14, 2022
    Member

    Another failure - https://ci.nodejs.org/job/node-test-binary-windows-js-suites/15103/

  5. RaisinTen
    added a commit that references this issue on Jun 14, 2022

    test: mark test-worker-http2-stream-terminate flaky on Windows

    74bb0d5

  6. RaisinTen commented on Jun 14, 2022

    @RaisinTen
    RaisinTen
    on Jun 14, 2022
    MemberAuthor

    Sent #43425 to mark the test as flaky on Windows.

  7. nodejs-github-bot
    added a commit that references this issue on Jun 18, 2022

    test: mark test-worker-http2-stream-terminate flaky on Windows

    61c7103

  8. F3n67u commented on Jun 29, 2022

    @F3n67u
    F3n67u
    on Jun 29, 2022
    Contributor

    Sent #43425 to mark the test as flaky on Windows.

    Hi @RaisinTen the test-worker-http2-stream-terminate test is still failing on other platforms, such as ubuntu, freebsd. Can we mark this test as flaky on all platforms?

    Reason parallel/test-worker-http2-stream-terminate
    Type JS_TEST_FAILURE
    Failed PR 6 (#43569, #43585, #43519, #43580, #43589, #43567)
    Appeared test-digitalocean-freebsd12-x64-1, test-digitalocean-freebsd12-x64-2, test-digitalocean-alpine311_container-x64-1, test-digitalocean-alpine312_container-x64-1, test-digitalocean-alpine312_container-x64-2, test-digitalocean-ubuntu1804_sharedlibs_container-x64-6, test-digitalocean-ubuntu1804_sharedlibs_container-x64-4, test-digitalocean-ubuntu1804_sharedlibs_container-x64-8, test-joyent-smartos20-x64-3
    First CI https://ci.nodejs.org/job/node-test-pull-request/44852/
    Last CI https://ci.nodejs.org/job/node-test-pull-request/44919/

    This data is extracted from today's nodejs/reliability#315

  9. RaisinTen commented on Jun 29, 2022

    @RaisinTen
    RaisinTen
    on Jun 29, 2022
    MemberAuthor

    Can we mark this test as flaky on all platforms?

    @F3n67u Sounds good to me

  10. F3n67u commented on Jun 29, 2022

    @F3n67u
    F3n67u
    on Jun 29, 2022
    Contributor

    I created a pr to move test-worker-http2-stream-terminate flaky on all platforms: #43620.

  11. RaisinTen commented on Jul 10, 2022

    @RaisinTen
    RaisinTen
    on Jul 10, 2022
    MemberAuthor

    cc @nodejs/async_hooks

    For some reason the ids don't match up

    node/src/env-inl.h

    Line 183 in b20838a

    async_id_fields_[kExecutionAsyncId] != async_id)) {

  12. RaisinTen
    added
    async_hooksIssues and PRs related to the async hooks subsystem.
    on Jul 10, 2022
  13. targos
    added 2 commits that reference this issue on Jul 12, 2022

    test: mark test-worker-http2-stream-terminate flaky on Windows

    5c0a24d

    test: mark test-worker-http2-stream-terminate flaky on Windows

    d9571cb
  14. targos
    added a commit that references this issue on Jul 31, 2022

    test: mark test-worker-http2-stream-terminate flaky on Windows

    68a1383

  15. 8 remaining items

  16. juanarbol
    added a commit that references this issue on Oct 11, 2022

    test: tune down parallelism for some flaky tests

    5ed4f43

  17. ywave620 commented on Oct 17, 2022

    @ywave620
    ywave620
    on Oct 17, 2022
    Contributor

    Hey, there. I would like to investigates into this issue. Is there any recent failure? I searched in the CI system, https://github.com/nodejs/reliability/issues?q=is%3Aissue+is%3Aopen+test-worker-http2-stream-terminate, it looks like this test has paased consistently since 2022-07-15

  18. Trott commented on Nov 12, 2022

    @Trott
    Trott
    on Nov 12, 2022
    Member

    Hey, there. I would like to investigates into this issue. Is there any recent failure? I searched in the CI system, https://github.com/nodejs/reliability/issues?q=is%3Aissue+is%3Aopen+test-worker-http2-stream-terminate, it looks like this test has paased consistently since 2022-07-15

    I don't think it will show up in those reports now that it is marked as unreliable. I think the only way to make progress on this is to figure out how to cause the issue on your own machine or else to remove the unreliable designation in parallel.status and see if it starts causing failures again.

  19. Trott commented on Nov 12, 2022

    @Trott
    Trott
    on Nov 12, 2022
    Member

    I don't think it will show up in those reports now that it is marked as unreliable. I think the only way to make progress on this is to figure out how to cause the issue on your own machine or else to remove the unreliable designation in parallel.status and see if it starts causing failures again.

    I suppose we could also try running it in CI with the stress test job and have it ignore the flaky designation, treating failures as failures.

  20. nodejs-github-bot
    closed this as completedin #45438on Nov 14, 2022
  21. nodejs-github-bot
    added a commit that references this issue on Nov 14, 2022

    test: remove flaky designation for test-worker-http2-stream-terminate

    badc631
  22. ruyadorno
    added a commit that references this issue on Nov 21, 2022

    test: remove flaky designation for test-worker-http2-stream-terminate

    00a3b5f
  23. guangwong
    added 2 commits that reference this issue on Jan 3, 2023

    test: tune down parallelism for some flaky tests

    1f4dbba

    test: tune down parallelism for some flaky tests

    ad6fd81
  24. danielleadams
    added 2 commits that reference this issue on Jan 3, 2023

    test: remove flaky designation for test-worker-http2-stream-terminate

    85c634d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    async_hooksIssues and PRs related to the async hooks subsystem.flaky-testIssues and PRs involving tests that fail intermittently in CI.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions