Skip to content

test: investigate crash in parallel/test-timers-uncaught-exception #14014

Closed
Closed
test: investigate crash in parallel/test-timers-uncaught-exception#14014
Labels
flaky-testIssues and PRs involving tests that fail intermittently in CI.freebsdIssues and PRs related to the FreeBSD platform.testIssues and PRs related to Node.js core tests and test infrastructure.timersIssues and PRs related to timers, setImmediate(), setInterval(), and setTimeout().

Description

@refack
refack
opened on Jun 30, 2017
  • Version: master
  • Platform: freeBSD11-x64
  • Subsystem: test,timers
1191	parallel/test-timers-uncaught-exception	
duration_ms	0.282
severity	crashed
stack	|-
oh no!
exit code: CRASHED (Signal: 11)

https://ci.nodejs.org/job/node-test-commit-freebsd/10045/nodes=freebsd11-x64/tapResults/

Activity

  1. refack
    added
    freebsdIssues and PRs related to the FreeBSD platform.
    testIssues and PRs related to Node.js core tests and test infrastructure.
    timersIssues and PRs related to timers, setImmediate(), setInterval(), and setTimeout().
    on Jun 30, 2017

  2. refack commented on Jun 30, 2017

    @refack
    refack
    on Jun 30, 2017
    ContributorAuthor

    /cc @nodejs/platform-freebsd

  3. refack
    added
    flaky-testIssues and PRs involving tests that fail intermittently in CI.
    on Jun 30, 2017

  4. misterdjules commented on Jul 1, 2017

    @misterdjules
    misterdjules
    on Jul 1, 2017

    Are there core files generated on these FreeBSD test machines? If so it would be helpful to get a stack trace from that. Otherwise we'll need to reproduce the crash.

    If not, would it be helpful to setup core file generation and cleanup as was done for SmartOS test machines?

  5. Trott commented on Jul 1, 2017

    @Trott
    Trott
    on Jul 1, 2017
    Member

    @nodejs/build Can we accommodate @misterdjules's request above about core files on FreeBSD machines?

  6. refack commented on Jul 3, 2017

    @refack
    refack
    on Jul 3, 2017
    ContributorAuthor

    Should this be a new issue?

    1531	sequential/test-net-listen-shared-ports	
duration_ms	1.72
severity	crashed
stack	oh no!
exit code: CRASHED (Signal: 11)

    https://ci.nodejs.org/job/node-test-commit-freebsd/10110/nodes=freebsd11-x64/

  7. Trott commented on Jul 3, 2017

    @Trott
    Trott
    on Jul 3, 2017
    Member

    Should this be a new issue?

    Since it appears to be the same issue, I suspect we should change the name of this issue and consider it a "oh no, FreeBSD is crashing on tests sometimes!" thing. I'd guess they're probably related if not exactly the same thing.

  8. BridgeAR commented on Sep 28, 2017

    @BridgeAR
    BridgeAR
    on Sep 28, 2017
    Member

    Ping @nodejs/platform-freebsd @nodejs/testing please have a look. It would be great to have a green CI before the next Code & Learn and this might be related to other flaky tests on freebsd as well.

  9. maclover7 commented on Dec 24, 2017

    @maclover7
    maclover7
    on Dec 24, 2017
    Contributor

    Did a stress test, and it looks like this test is working better now. Since no reports for several months, going to close this. Please open if I'm mistaken, or if test starts flaking again :)

  10. maclover7
    closed this as completedon Dec 24, 2017
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

    flaky-testIssues and PRs involving tests that fail intermittently in CI.freebsdIssues and PRs related to the FreeBSD platform.testIssues and PRs related to Node.js core tests and test infrastructure.timersIssues and PRs related to timers, setImmediate(), setInterval(), and setTimeout().

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions