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-primary-error flaky in test-asan job #39655

Open
targos opened this issue Aug 4, 2021 · 13 comments
Open

test-cluster-primary-error flaky in test-asan job #39655

targos opened this issue Aug 4, 2021 · 13 comments
Labels
flaky-test Issues and PRs related to the tests with unstable failures on the CI.

Comments

@targos
Copy link
Member

targos commented Aug 4, 2021

Example: https://github.com/nodejs/node/runs/3238780435?check_suite_focus=true

I think everybody knows about this one but I couldn't find an existing issue

@targos targos added the flaky-test Issues and PRs related to the tests with unstable failures on the CI. label Aug 4, 2021
@targos
Copy link
Member Author

targos commented Aug 4, 2021

=== release test-cluster-primary-error ===
Path: parallel/test-cluster-primary-error
Error: Command: out/Release/node /home/runner/work/node/node/test/parallel/test-cluster-primary-error.js
--- TIMEOUT ---

===
=== 1 tests failed
===
make[1]: *** [Makefile:513: test-ci] Error 1

@lpinca
Copy link
Member

lpinca commented Aug 4, 2021

Perhaps a longer timeout is sufficient?

@lpinca
Copy link
Member

lpinca commented Aug 4, 2021

It's 5 minutes at the moment so I think it is already more than enough.

@tniessen
Copy link
Member

FWIW, this is still one of the main reasons asan regularly fails, often taking hours for a full run (build + tests). Maybe we should temporarily increase the timeout to 10 minutes and see if that helps?

@mhdawson
Copy link
Member

Another failure - #42459

@Trott
Copy link
Member

Trott commented Mar 30, 2022

Another failure - #42459

A link to the action results would be much more useful than a link to the PR, where the previous failing Action will be kind of hidden away. So here!: https://github.com/nodejs/node/runs/5684048217?check_suite_focus=true

@F3n67u
Copy link
Member

F3n67u commented Jun 20, 2022

@mmomtchev
Copy link
Contributor

I have an environment where it fails every time, but only if it is run as part of the full suite, when running the test independently it passes. It fails along several other tests:
https://github.com/mmomtchev/libnode/runs/7118719199?check_suite_focus=true#step:7:11745
I will try to investigate, but if you want to give it a try:

git clone -b failing-unit-test https://github.com/mmomtchev/libnode.git
docker build -t yourname/libnode-ubuntu-bionic:latest .
docker run yourname/libnode-ubuntu-bionic:latest

@gengjiawen
Copy link
Member

@theanarkh landed a fix on #44066.

@jasnell
Copy link
Member

jasnell commented Dec 20, 2022

I'm assuming this is fixed now since #44066 landed? Please re-open if appears to still be flaky.

@debadree25
Copy link
Member

debadree25 commented Feb 28, 2023

This is probably still an issue
Example https://github.com/nodejs/node/actions/runs/4290895133/jobs/7475416200
had seen it at a few other places too but can find the links

Reopening hence

@debadree25 debadree25 reopened this Feb 28, 2023
@theanarkh
Copy link
Contributor

Yes. The PR is closed.

@anonrig
Copy link
Member

anonrig commented Apr 5, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flaky-test Issues and PRs related to the tests with unstable failures on the CI.
Projects
None yet
Development

No branches or pull requests