| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | test: scale keepalive timeouts for slow machines | Ben Noordhuis | 2019-12-08 | 1 | -4/+4 |
| | | | | | | | | | | | | | | | | | The test was using fixed timeouts and that seems to be causing sporadic test failures on pi1-docker host (which is a very slow machine.) Fixes: https://github.com/nodejs/node/issues/30828 PR-URL: https://github.com/nodejs/node/pull/30834 Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Gabriel Schulhof <gabriel.schulhof@intel.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> | ||||
| * | test: move timing-sensitive test to sequential | Rich Trott | 2017-11-17 | 1 | -0/+79 |
| test-https-server-keep-alive-timeout relies on server timeouts and whatnot that will be inherently unreliable on a busy host. The test fails when run with a high `-j` value and higher `--repeat` value passed to `tools/test.py`. Move the test to `sequential`. PR-URL: https://github.com/nodejs/node/pull/16775 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Khaidi Chu <i@2333.moe> Reviewed-By: James M Snell <jasnell@gmail.com> | |||||
 |
index : delta/node-new.git | |
| github.com: nodejs/node.git |
| summaryrefslogtreecommitdiff |