-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
Assertion `!flush_tasks_' failed in parallel/test-worker-memory #30850
Labels
c++
Issues and PRs that require attention from people who are familiar with C++.
duplicate
Issues and PRs that are duplicates of other issues or PRs.
v8 platform
Issues and PRs related to Node's v8::Platform implementation.
Comments
bnoordhuis
added
the
c++
Issues and PRs that require attention from people who are familiar with C++.
label
Dec 8, 2019
Also, duplicate of #30846 I guess? Did this happen locally for you? |
Oh, I searched for I'll close this out in favor of #30846. |
bnoordhuis
added
the
duplicate
Issues and PRs that are duplicates of other issues or PRs.
label
Dec 8, 2019
addaleax
added
the
v8 platform
Issues and PRs related to Node's v8::Platform implementation.
label
Feb 18, 2020
This was referenced Apr 13, 2021
Open
This was referenced Sep 17, 2021
This was referenced Sep 29, 2022
This was referenced Oct 5, 2022
This was referenced Oct 8, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
c++
Issues and PRs that require attention from people who are familiar with C++.
duplicate
Issues and PRs that are duplicates of other issues or PRs.
v8 platform
Issues and PRs related to Node's v8::Platform implementation.
Today's master, commit a9abc17:
Presumably a race condition because I've only seen it happen once. I ran the test in a loop for a while but no dice.
#30324 probably either introduced or surfaced this. (It introduced the check but it's possible the errant behavior existed before that. Also that CHECK should probably be CHECK_NULL.)
cc @addaleax @laverdet
The text was updated successfully, but these errors were encountered: