Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 34.2k
test: move long-running test to sequential#10161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
Conversation
Trott commented Dec 7, 2016 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
Trott commented Dec 7, 2016
Refs: #9815 (comment) |
Trott commented Dec 7, 2016
Trott commented Dec 7, 2016
Meh...passed on SmartOs 15 64-bit, but barely didn't time out: ok 1255 sequential/test-buffer-creation-regression --- duration_ms: 58.896Will try splitting the test up into three files. |
Trott commented Dec 7, 2016
OK, split the test into 3. Trying again... |
Trott commented Dec 7, 2016
These results seem more like it: ok 1255 sequential/test-buffer-creation-regression-1 --- duration_ms: 0.428 ...ok 1256 sequential/test-buffer-creation-regression-2 --- duration_ms: 9.35 ...ok 1257 sequential/test-buffer-creation-regression-3 --- duration_ms: 16.939 |
Trott commented Dec 7, 2016 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
CI is all green ✅ . I'd like to expedite landing this because this issue is significantly impacting CI results. Reviews, anyone? @nodejs/testing @thefourtheye |
thefourtheye commented Dec 7, 2016
@Trott All the three tests have more than 90% similar code. Can we refactor and put the common code in one file? |
thefourtheye commented Dec 7, 2016
Apart from that, I believe the second test itself is enough as regression. Can we modify the original test and remove other two cases? |
Trott commented Dec 7, 2016
For me, at least, running v7.2.0, only the final test case fails. Happy to get rid of the other two and just keep that one, if that works. |
test-buffer-creation-regression is flaky on some SmartOS hosts in CI, timing out. Move to sequential so it does not compete with other tests for resources. Reduce three test cases to just the one needed to identify the regression.
Trott commented Dec 7, 2016
Reduced to just the one test case needed. CI: https://ci.nodejs.org/job/node-test-pull-request/5286/ |
test-buffer-creation-regression is flaky on some SmartOS hosts in CI, timing out. Move to sequential so it does not compete with other tests for resources. Reduce three test cases to just the one needed to identify the regression. PR-URL: nodejs#10161 Reviewed-By: Santiago Gimeno <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Italo A. Casas <[email protected]>
Trott commented Dec 7, 2016
Landed in cdeb85e. Thanks. |
test-buffer-creation-regression is flaky on some SmartOS hosts in CI, timing out. Move to sequential so it does not compete with other tests for resources. Reduce three test cases to just the one needed to identify the regression. PR-URL: #10161 Reviewed-By: Santiago Gimeno <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Italo A. Casas <[email protected]>
MylesBorins commented Dec 20, 2016
This is failing when backported to v4.x is that expected behavior? |
Trott commented Dec 20, 2016
|
MylesBorins commented Jan 23, 2017
@Trott this is failing on v6.x too. labelled don't land, feel free to backport |
Trott commented Jan 23, 2017
Seems like the original test doesn't exist on v6.x either, so yeah, do not land on v6.x. |
thefourtheye commented Feb 5, 2017
test-buffer-creation-regression is flaky on some SmartOS hosts in CI, timing out. Move to sequential so it does not compete with other tests for resources. Reduce three test cases to just the one needed to identify the regression. PR-URL: #10161 Reviewed-By: Santiago Gimeno <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Italo A. Casas <[email protected]> Backport-Of: #10161 PR-URL: #11176 Reviewed-By: James M Snell <[email protected]>
test-buffer-creation-regression is flaky on some SmartOS hosts in CI, timing out. Move to sequential so it does not compete with other tests for resources. Reduce three test cases to just the one needed to identify the regression. PR-URL: #10161 Reviewed-By: Santiago Gimeno <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Italo A. Casas <[email protected]> Backport-Of: #10161 PR-URL: #11176 Reviewed-By: James M Snell <[email protected]>
Checklist
make -j8 test(UNIX), orvcbuild test nosign(Windows) passesAffected core subsystem(s)
test buffer
Description of change
test-buffer-creation-regression is flaky on some SmartOS hosts in CI,
timing out. Move to sequential to it does not compete with other tests
for resources.