-
Notifications
You must be signed in to change notification settings - Fork 14
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
Investigate new v12.19.0 segfaults in tests. #93
Comments
I'm more leaning towards segfault in Also the last passed PR workflow had Node References |
Seems to be segfaulting only on
|
Seems like there will be a revert of a change that caused issues with ABI. Need to re-test after the change is reverted on node. |
Waiting for nodejs/node#35777 to "bake" and get released. |
Revert seems to be included for |
@hertzg can you confirm that the segfault is fixed with the rc? |
@MylesBorins ✔️ No segfaults with
|
## [1.4.0](v1.3.9...v1.4.0) (2020-11-09) ### Features * add support for the TCP_USER_TIMEOUT option ([51462f7](51462f7)) ### Bug Fixes * requires node >=10.20.0 instead of >=4 ([b8fe01c](b8fe01c)) * temp monkey patch to allow tests to pass (ref: [#93](#93)) ([4cb944e](4cb944e)) * throw in (set|get)ters when constant == null ([b5f1ce4](b5f1ce4))
Checks re-enabled in #119 as |
Describe the bug
Single test seems to be consistently failing
PR / test-integration (ubuntu-latest, 12) (pull_request) Failing after 59s — test-integration
The error seems to beI'm not sure if it really is the problem as it only affectstcpdump
utility segfaulting butubuntu-latest
withnode-12
so it might be node crashing due to various reasons.The text was updated successfully, but these errors were encountered: