Tests fail for Node.js >= 12
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, node.js
- Domain
- testing
Research direction
Start with the failing assertions in test.js at lines 127, 130, and 136, then run the npm test command shown in the report under Node.js 12 or newer. Done means the three error checks pass and the full suite reports 233 passing tests with no failures.
Written by the indexing model from the issue text.
Description
Sharing the logs:
✗ same error for bad prime
---
operator: equal
expected: 1
actual: 9
at: Test.<anonymous> (/home/nilesh/ups/diffie-hellman/test.js:127:5)
...
✗ same error for bad prime non testable generator
---
operator: equal
expected: 1
actual: 5
at: Test.<anonymous> (/home/nilesh/ups/diffie-hellman/test.js:130:5)
...
✓ same error for good prime wrong generator
✗ same error for good prime non testable generator
---
operator: equal
expected: 0
actual: 4
at: Test.<anonymous> (/home/nilesh/ups/diffie-hellman/test.js:136:5)
...
tests 233
pass 230
fail 3
Failed Tests: There were 3 failures
✗ check errors same error for bad prime
✗ check errors same error for bad prime non testable generator
✗ check errors same error for good prime non testable generator
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! diffie-hellman@5.0.3 test: `node test.js | tspec`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the diffie-hellman@5.0.3 test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/nilesh/.npm/_logs/2020-01-31T15_53_55_954Z-debug.log
- Dominant language
- JavaScript
- Stars
- 95
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from browserify/diffie-hellman
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
browserify/diffie-hellman#30 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
browserify/diffie-hellman#28 ·
-
standalone js file? Open
Difficulty 2/5 1-3 hours Newbie friendliness 30/100
browserify/diffie-hellman#25 · 5 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
browserify/diffie-hellman#24 ·
-
question
browserify/diffie-hellman#22 · 13 comments · 1 assignee ·
All issues in browserify/diffie-hellman
Similar issues
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Automattic/safe-publish#594 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
dream-num/dsh-univer-office#104 ·
-
comp/dashboard invalid P3
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
NousResearch/hermes-agent#121143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
avniproject/avni-webapp#1811 ·
-
area/auroraboot area/webui bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100