Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test-cluster-worker-isdead crash #24496

Closed
Fishrock123 opened this issue Nov 19, 2018 · 3 comments
Closed

test-cluster-worker-isdead crash #24496

Fishrock123 opened this issue Nov 19, 2018 · 3 comments
Labels
arm Issues and PRs related to the ARM platform. cluster Issues and PRs related to the cluster subsystem. flaky-test Issues and PRs related to the tests with unstable failures on the CI.

Comments

@Fishrock123
Copy link
Contributor

From #24389

CI run: https://ci.nodejs.org/job/node-test-commit-arm/20123

Detail: https://ci.nodejs.org/job/node-test-commit-arm/20123/nodes=ubuntu1604-arm64/testReport/junit/(root)/test/parallel_test_cluster_worker_isdead/

Output:

crashed (-4)

...
¯\_(ツ)_/¯

@Fishrock123 Fishrock123 added cluster Issues and PRs related to the cluster subsystem. build Issues and PRs related to build files or the CI. arm Issues and PRs related to the ARM platform. flaky-test Issues and PRs related to the tests with unstable failures on the CI. and removed build Issues and PRs related to build files or the CI. labels Nov 19, 2018
@Trott
Copy link
Member

Trott commented Nov 26, 2018

Marginally more information preserved here before it gets wiped from CI:

09:42:32 not ok 306 parallel/test-cluster-worker-isdead
09:42:32   ---
09:42:32   duration_ms: 0.141
09:42:32   severity: crashed
09:42:32   exitcode: -4
09:42:32   stack: |-

Host was test-packetnet-ubuntu1604-arm64-1

@cjihrig
Copy link
Contributor

cjihrig commented May 14, 2019

@Trott do you know if this is still an issue?

@Trott
Copy link
Member

Trott commented May 14, 2019

@Trott do you know if this is still an issue?

I haven't seen it and ncu-ci walk isn't finding it, so I think this can probably be closed. (Can always be reopened if it recurs or someone manages to come up with a repro.)

@Trott Trott closed this as completed May 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arm Issues and PRs related to the ARM platform. cluster Issues and PRs related to the cluster subsystem. flaky-test Issues and PRs related to the tests with unstable failures on the CI.
Projects
None yet
Development

No branches or pull requests

3 participants