Skip to content

[test] riscv64 failure in parallel/test-crypto-sign-verify #45065

Description

@kapouer

Version

v18.10.0

Platform

Linux 5.18.0-4-riscv64 #1 SMP Debian 5.18.16-1 (2022-08-10) riscv64 (riscv64)

Subsystem

test

What steps will reproduce the bug?

Run the test.

How often does it reproduce? Is there a required condition?

I don't know. At least once.

What is the expected behavior?

Test succeeds

What do you see instead?

Test fails

Additional information

What do these lines want to achieve exactly ?

const library = {
configurable: true,
set() {
throw new Error('bye, bye, library');
}
};
Object.defineProperty(Object.prototype, 'library', library);
assert.throws(() => {
crypto.createSign('sha1').sign(
`-----BEGIN RSA PRIVATE KEY-----
AAAAAAAAAAAA
-----END RSA PRIVATE KEY-----`);
}, { message: 'bye, bye, library' });

Activity

  1. bnoordhuis commented on Oct 19, 2022

    @bnoordhuis
    Member

    See #27157 for background. In a nutshell, node shouldn't crash (as in: segfault, abort) when JS code tampers with object prototypes.

  2. kapouer commented on Oct 19, 2022

    @kapouer
    ContributorAuthor

    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'.

  3. changed the title [-][test] oddity in parallel/test-crypto-sign-verify[/-] [+][test] riscv64 failure in parallel/test-crypto-sign-verify[/+] on Oct 19, 2022
  4. added
    testIssues and PRs related to Node.js core tests and test infrastructure.
    on Oct 19, 2022
  5. github-actions commented on Jun 23, 2026

    @github-actions
    Contributor

    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.

  6. added
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Jun 23, 2026
  7. github-actions commented on Jul 24, 2026

    @github-actions
    Contributor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.testIssues and PRs related to Node.js core tests and test infrastructure.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions