Skip to content

Conversation

@Trott
Copy link
Member

@TrottTrott commented Dec 7, 2016

Checklist
  • make -j8 test (UNIX), or vcbuild test nosign (Windows) passes
  • commit message follows commit guidelines
Affected 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.

@TrottTrott added buffer Issues and PRs related to the buffer subsystem. wip Issues and PRs that are still a work in progress. smartos Issues and PRs related to the SmartOS platform. labels Dec 7, 2016
@nodejs-github-botnodejs-github-bot added the test Issues and PRs related to the tests. label Dec 7, 2016
@Trott
Copy link
MemberAuthor

Trott commented Dec 7, 2016

Refs: #9815 (comment)

@Trott
Copy link
MemberAuthor

Trott commented Dec 7, 2016

@TrottTrott removed the wip Issues and PRs that are still a work in progress. label Dec 7, 2016
@Trott
Copy link
MemberAuthor

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.896

Will try splitting the test up into three files.

@Trott
Copy link
MemberAuthor

Trott commented Dec 7, 2016

OK, split the test into 3. Trying again...

CI: https://ci.nodejs.org/job/node-test-pull-request/5285/

@Trott
Copy link
MemberAuthor

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
Copy link
MemberAuthor

Trott commented Dec 7, 2016

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
Copy link
Contributor

@Trott All the three tests have more than 90% similar code. Can we refactor and put the common code in one file?

@thefourtheye
Copy link
Contributor

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
Copy link
MemberAuthor

Trott 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?

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
Copy link
MemberAuthor

Trott commented Dec 7, 2016

Reduced to just the one test case needed. CI: https://ci.nodejs.org/job/node-test-pull-request/5286/

Trott added a commit to Trott/io.js that referenced this pull request Dec 7, 2016
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
Copy link
MemberAuthor

Trott commented Dec 7, 2016

Landed in cdeb85e. Thanks.

@TrottTrott closed this Dec 7, 2016
addaleax pushed a commit that referenced this pull request Dec 8, 2016
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]>
@italoacasasitaloacasas mentioned this pull request Dec 15, 2016
@MylesBorins
Copy link
Contributor

This is failing when backported to v4.x

is that expected behavior?

=== release test-buffer-creation-regression === Path: sequential/test-buffer-creation-regression FATAL ERROR: v8::Uint8Array::New(Local<ArrayBuffer>, size_t, size_t) length exceeds max allowed value Command: out/Release/node /Users/thealphanerd/code/node/v4.x/test/sequential/test-buffer-creation-regression.js 

@Trott
Copy link
MemberAuthor

test/parallel/test-buffer-creation-regression.js doesn't exist on v4.x-staging, does it? If not then this should be labeled do-not-land-on-v4.x I think...

@MylesBorins
Copy link
Contributor

@Trott this is failing on v6.x too. labelled don't land, feel free to backport

@Trott
Copy link
MemberAuthor

@Trott this is failing on v6.x too. labelled don't land, feel free to backport

Seems like the original test doesn't exist on v6.x either, so yeah, do not land on v6.x.

@thefourtheyethefourtheye mentioned this pull request Feb 5, 2017
3 tasks
@thefourtheye
Copy link
Contributor

I backported this in #11176, along with #9815 (which has the test) and added lts watch v6.x.

jasnell pushed a commit that referenced this pull request Mar 3, 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]>
MylesBorins pushed a commit that referenced this pull request Mar 9, 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]>
@TrottTrott deleted the deflake-smartos branch January 13, 2022 22:44
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bufferIssues and PRs related to the buffer subsystem.smartosIssues and PRs related to the SmartOS platform.testIssues and PRs related to the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

@Trott@thefourtheye@MylesBorins@santigimeno@cjihrig@italoacasas@nodejs-github-bot