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

threadsafe_function test - CI failing on Master since May 4th #994

Closed
mhdawson opened this issue May 10, 2021 · 8 comments
Closed

threadsafe_function test - CI failing on Master since May 4th #994

mhdawson opened this issue May 10, 2021 · 8 comments

Comments

@mhdawson
Copy link
Member

Running test 'objectwrap_worker_thread'
Running test 'promise'
Running test 'reference'
Running test 'run_script'
Running test 'threadsafe_function/threadsafe_function'
FATAL ERROR: DataSourceThread Queue was never closing
Tests aborted with SIGSEGV
Build step 'Conditional steps (multiple)' marked build as failure
Sending e-mails to: [email protected] [email protected] [email protected]
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE

This seems to fail every time now.

@KevinEady I think you know the test best
@legendecas were there any changes in master that you think might have affected this?

@mhdawson
Copy link
Member Author

I wonder if this is related: #994

@mhdawson
Copy link
Member Author

There are no other changes that I can see which are tagged node-api around that time.

@mhdawson
Copy link
Member Author

@indutny FYI

@legendecas
Copy link
Member

legendecas commented May 10, 2021

nodejs/node@7abc7e4 (node-api: faster threadsafe_function) is landed on Node.js core around May 5th 1 AM (GMT). And there are no significant updates in node-addon-api since late April...

@legendecas
Copy link
Member

I can reproduce on local node.js main branch build. Will dig into the problem to seek a quick fix.

@legendecas
Copy link
Member

The failing test case is test/threadsafe_function/threadsafe_function.js.

@legendecas
Copy link
Member

Just found an assumption in the test about the execution timing of tsfn calls. Filed #995 trying to see if the quick fix works across various builds.

@mhdawson
Copy link
Member Author

Resolved in #995, @legendecas thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants