You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[test] riscv64 failure in parallel/test-crypto-sign-verify #45065
Oh, ok. It's just odd that it's not in its own test.
On the other hand, that test fails on riscv64 - as if the "library" property wasn't changed, and the initial openssl error is caught, not the 'bye, bye, library'.
changed the title [-][test] oddity in parallel/test-crypto-sign-verify[/-][+][test] riscv64 failure in parallel/test-crypto-sign-verify[/+]on Oct 19, 2022
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
Activity
bnoordhuis commentedon Oct 19, 2022
See #27157 for background. In a nutshell, node shouldn't crash (as in: segfault, abort) when JS code tampers with object prototypes.
kapouer commentedon Oct 19, 2022
Oh, ok. It's just odd that it's not in its own test.
On the other hand, that test fails on riscv64 - as if the "library" property wasn't changed, and the initial openssl error is caught, not the 'bye, bye, library'.
[-][test] oddity in parallel/test-crypto-sign-verify[/-][+][test] riscv64 failure in parallel/test-crypto-sign-verify[/+]github-actions commentedon Jun 23, 2026
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
github-actions commentedon Jul 24, 2026
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.