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' }); |
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 ?
node/test/parallel/test-crypto-sign-verify.js
Lines 34 to 47 in ef17711