Skip to content

Investigate flaky parallel/test-async-hooks-http-parser-destroy on OS X #28112

Closed

Description

@sam-github

Seems to be failing regularly:

For all above, failures are identical:

timeout
assert.js:89
  throw new AssertionError(obj);
  ^

AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:
+ actual - expected ... Lines skipped

  [
-   1288,
    156,

Perhaps it should be marked flaky? I'm not sure how common it has to be to deserve the marking.

  • Version:
  • Platform:
  • Subsystem:

Activity

  1. added
    httpIssues and PRs related to the http subsystem.
    testIssues and PRs related to Node.js core tests and test infrastructure.
    macosIssues and PRs related to the macOS platform.
    async_hooksIssues and PRs related to the async hooks subsystem.
    flaky-testIssues and PRs involving tests that fail intermittently in CI.
    on Jun 6, 2019
  2. Flarna commented on Jun 13, 2019

    @Flarna
    Member

    The test duration in failed cases seems to be significant longer as in the pass case. Not sure if duration_ms: 120.95 is really in milli seconds - as a wild guess I would say it's in sec and therefore 2 minutes which would match the default http timeout used by node as far as I know.

    I have no access to OS X so hard for me to work on this.

  3. Trott commented on Jun 13, 2019

    @Trott
    Member

    The test duration in failed cases seems to be significant longer as in the pass case. Not sure if duration_ms: 120.95 is really in milli seconds - as a wild guess I would say it's in sec and therefore 2 minutes which would match the default http timeout used by node as far as I know.

    I have no access to OS X so hard for me to work on this.

    duraion_ms is unfortunate, but it's a tap thing so we can't/shouldn't change it. It is duration in seconds.

    It fails at 120 seconds because that's the timeout duration in the test runner.

    So it gets caught in a deadlock or infinite loop or waiting for an event that never actually fires or (unlikely but possible) maybe just takes too darned long to run and would complete if it had more time or...

  4. Flarna commented on Jun 13, 2019

    @Flarna
    Member

    Hmm, maybe add some more counters, e.g. one for HTTPINCOMINGMESSAGE and HTTPCLIENTREQUEST, one for client responses and then assert on them first before the diff of the list to get some hint what is hanging.

    Or hope that some OS X users gives a try to reproduce this locally and debug.

  5. sam-github commented on Jun 13, 2019

    @sam-github
    ContributorAuthor

    @Flarna Are you willing to PR that change, ☝️ ? It would be very helpful if you have time to start looking into this.

  6. Flarna commented on Jun 13, 2019

    @Flarna
    Member

    Sure, will take a look in a free slot during next days.

    created #28253

  7. Flarna commented on Jun 28, 2019

    @Flarna
    Member

    Is this still valid? PR is open since quite a while now...

  8. lpinca commented on Jul 13, 2019

    @lpinca
    Member

    I can't reproduce locally but I'm on macOS 10.14 not 10.11.

  9. Flarna commented on Sep 14, 2019

    @Flarna
    Member

    Has #28253 fixed the flaky parallel/test-async-hooks-http-parser-destroy on OS X? Don't know how to query CI statistics.

  10. Trott commented on Sep 15, 2019

    @Trott
    Member

    Has #28253 fixed the flaky parallel/test-async-hooks-http-parser-destroy on OS X? Don't know how to query CI statistics.

    Used ncu-ci from node-core-utils to check and couldn't find any async-hooks test failures other than test-statwatcher.js. So I think we can conclude that this isn't a problem and plan to re-open if that's wrong and someone notices it poppingup again.

    Thanks, @Flarna!

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.httpIssues and PRs related to the http subsystem.macosIssues and PRs related to the macOS platform.testIssues and PRs related to Node.js core tests and test infrastructure.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions