Uh oh!
There was an error while loading. Please reload this page.
test: remove magic numbers in test-gc-http-client-onerror - #24943
Conversation
Trott
commented
Dec 10, 2018
Trott
commented
Dec 10, 2018
Stress test on master (with Stress test on this PR with same parameters: |
bnoordhuis
commented
Dec 10, 2018
Relevant failure: https://ci.nodejs.org/job/node-test-commit-linux/23914/nodes=centos6-64-gcc6/console If I had to guess, it's because of the removal of the early return in getall(). |
Trott
commented
Dec 10, 2018
Yeah, there's a few of those. Not sure how to re-implement an early return without restoring some kind of magic number but I'll think about it.... |
BridgeAR
commented
Dec 12, 2018
@Trott it should be sufficient to add another variable (e.g., |
502e7a7 to
aeb2138CompareTrott
commented
Dec 13, 2018
92b8899 to
011027aCompareTrott
commented
Dec 13, 2018
Trott
commented
Dec 13, 2018
Remove magic numbers (500, 10, 100) from the test. Instead, detect when GC has started and stop sending requests at that point. On my laptop, this results in 16 or 20 requests per run instead of 500. Fixes: nodejs#23089
Trott
commented
Dec 14, 2018
Worked out the puzzle. This works now. Could use some reviews! |
Trott
commented
Dec 15, 2018
Needs a review or two. /ping @nodejs/testing |
Trott
commented
Dec 16, 2018
Bump. |
Trott
commented
Dec 17, 2018
Landed in 47ecf20 |
Remove magic numbers (500, 10, 100) from the test. Instead, detect when GC has started and stop sending requests at that point. On my laptop, this results in 16 or 20 requests per run instead of 500. Fixes: nodejs#23089 PR-URL: nodejs#24943 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Remove magic numbers (500, 10, 100) from the test. Instead, detect when GC has started and stop sending requests at that point. On my laptop, this results in 16 or 20 requests per run instead of 500. Fixes: nodejs#23089 PR-URL: nodejs#24943 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Remove magic numbers 500 and 10 from the test. Instead, detect when GC
has started and stop sending requests at that point.
On my laptop, this results in 68 or 72 requests per run instead of 500.
Fixes: #23089
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes