Skip to content
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

test: move ArrayStream to common #4027

Merged
merged 0 commits into from
Nov 27, 2015
Merged

test: move ArrayStream to common #4027

merged 0 commits into from
Nov 27, 2015

Conversation

cjihrig
Copy link
Contributor

@cjihrig cjihrig commented Nov 25, 2015

A number of REPL tests define the same ArrayStream object. This commit moves the repeated code into common.js.

@bnoordhuis
Copy link
Member

LGTM. test/common.js is arguably a mildly odd place for it but putting it in e.g. test/fixtures is weird too.

You could drop it in test/parallel and call it array-stream.js. The test runner will skip over it, it only executes files that start with test-. No strong opinion though, just thinking out loud.

@cjihrig
Copy link
Contributor Author

cjihrig commented Nov 25, 2015

I agree that there isn't a great location for it. My only concern with putting it in test/parallel is that eventually it might be needed in sequential or somewhere else. That's not really a big deal either though.

@bnoordhuis
Copy link
Member

I guess it doesn't really matter, we can always move it later. LGTM.

@mscdex mscdex added repl Issues and PRs related to the REPL subsystem. test Issues and PRs related to the tests. labels Nov 25, 2015
@cjihrig
Copy link
Contributor Author

cjihrig commented Nov 26, 2015

@cjihrig cjihrig closed this Nov 27, 2015
cjihrig added a commit to cjihrig/node that referenced this pull request Nov 27, 2015
A number of REPL tests define the same ArrayStream object. This
commit moves the repeated code into common.js.

PR-URL: nodejs#4027
Reviewed-By: Ben Noordhuis <[email protected]>
@cjihrig cjihrig merged commit f2e319b into nodejs:master Nov 27, 2015
@cjihrig cjihrig deleted the arraystream branch November 27, 2015 02:22
@MylesBorins
Copy link
Contributor

For this to land on LTS we need #4013 to land first, which is blocked by #4026

@cjihrig
Copy link
Contributor Author

cjihrig commented Dec 1, 2015

This could be ported without the other two PRs if you really had your heart set on it. The diff should only be one test introduced in #4013. That said, it's not important.

cjihrig added a commit that referenced this pull request Dec 5, 2015
A number of REPL tests define the same ArrayStream object. This
commit moves the repeated code into common.js.

PR-URL: #4027
Reviewed-By: Ben Noordhuis <[email protected]>
@rvagg rvagg mentioned this pull request Dec 17, 2015
cjihrig added a commit to cjihrig/node that referenced this pull request Jan 7, 2016
A number of REPL tests define the same ArrayStream object. This
commit moves the repeated code into common.js.

PR-URL: nodejs#4027
Reviewed-By: Ben Noordhuis <[email protected]>

Conflicts:
	test/common.js
MylesBorins pushed a commit that referenced this pull request Jan 19, 2016
A number of REPL tests define the same ArrayStream object. This
commit moves the repeated code into common.js.

PR-URL: #4027
Reviewed-By: Ben Noordhuis <[email protected]>

Conflicts:
	test/common.js
@MylesBorins MylesBorins mentioned this pull request Jan 19, 2016
scovetta pushed a commit to scovetta/node that referenced this pull request Apr 2, 2016
A number of REPL tests define the same ArrayStream object. This
commit moves the repeated code into common.js.

PR-URL: nodejs#4027
Reviewed-By: Ben Noordhuis <[email protected]>
jaimecbernardo added a commit to JaneaSystems/node that referenced this pull request Jun 30, 2017
The sequential/test-regress-GH-4027 test is flaky with an increased
system load, failing when the watched file is unlinked before the
first state of the watched file is retrieved.

After increasing the delay before unlinking and calling setTimeout
after watchFile, the flakiness stopped reproducing.

Fixes: nodejs#13800
Trott pushed a commit that referenced this pull request Jul 3, 2017
The sequential/test-regress-GH-4027 test is flaky with an increased
system load, failing when the watched file is unlinked before the
first state of the watched file is retrieved.

After increasing the delay before unlinking and calling setTimeout
after watchFile, the flakiness stopped reproducing.

PR-URL: #14010
Fixes: #13800
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Refael Ackermann <[email protected]>
addaleax pushed a commit that referenced this pull request Jul 11, 2017
The sequential/test-regress-GH-4027 test is flaky with an increased
system load, failing when the watched file is unlinked before the
first state of the watched file is retrieved.

After increasing the delay before unlinking and calling setTimeout
after watchFile, the flakiness stopped reproducing.

PR-URL: #14010
Fixes: #13800
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Refael Ackermann <[email protected]>
@addaleax addaleax mentioned this pull request Jul 11, 2017
addaleax pushed a commit that referenced this pull request Jul 18, 2017
The sequential/test-regress-GH-4027 test is flaky with an increased
system load, failing when the watched file is unlinked before the
first state of the watched file is retrieved.

After increasing the delay before unlinking and calling setTimeout
after watchFile, the flakiness stopped reproducing.

PR-URL: #14010
Fixes: #13800
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Refael Ackermann <[email protected]>
Fishrock123 pushed a commit that referenced this pull request Jul 19, 2017
The sequential/test-regress-GH-4027 test is flaky with an increased
system load, failing when the watched file is unlinked before the
first state of the watched file is retrieved.

After increasing the delay before unlinking and calling setTimeout
after watchFile, the flakiness stopped reproducing.

PR-URL: #14010
Fixes: #13800
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Refael Ackermann <[email protected]>
MylesBorins pushed a commit that referenced this pull request Aug 15, 2017
The sequential/test-regress-GH-4027 test is flaky with an increased
system load, failing when the watched file is unlinked before the
first state of the watched file is retrieved.

After increasing the delay before unlinking and calling setTimeout
after watchFile, the flakiness stopped reproducing.

PR-URL: #14010
Fixes: #13800
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Refael Ackermann <[email protected]>
MylesBorins pushed a commit that referenced this pull request Aug 15, 2017
The sequential/test-regress-GH-4027 test is flaky with an increased
system load, failing when the watched file is unlinked before the
first state of the watched file is retrieved.

After increasing the delay before unlinking and calling setTimeout
after watchFile, the flakiness stopped reproducing.

PR-URL: #14010
Fixes: #13800
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Refael Ackermann <[email protected]>
MylesBorins pushed a commit that referenced this pull request Aug 16, 2017
The sequential/test-regress-GH-4027 test is flaky with an increased
system load, failing when the watched file is unlinked before the
first state of the watched file is retrieved.

After increasing the delay before unlinking and calling setTimeout
after watchFile, the flakiness stopped reproducing.

PR-URL: #14010
Fixes: #13800
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Refael Ackermann <[email protected]>
@MylesBorins MylesBorins mentioned this pull request Aug 16, 2017
ryzokuken added a commit to ryzokuken/node that referenced this pull request Mar 6, 2018
Rename the test appropriately alongside mentioning the subsystem
Also, make a few basic changes to make sure the test conforms
to the standard test structure

Refs: nodejs#19105
Refs: https://github.com/nodejs/node/blob/master/doc/guides/writing-tests.md#test-structure
devsnek pushed a commit that referenced this pull request Mar 8, 2018
Rename the test appropriately alongside mentioning the subsystem
Also, make a few basic changes to make sure the test conforms
to the standard test structure

Refs: #19105
Refs: https://github.com/nodejs/node/blob/master/doc/guides/writing-tests.md#test-structure

PR-URL: #19161
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Gireesh Punathil <[email protected]>
targos pushed a commit that referenced this pull request Mar 17, 2018
Rename the test appropriately alongside mentioning the subsystem
Also, make a few basic changes to make sure the test conforms
to the standard test structure

Refs: #19105
Refs: https://github.com/nodejs/node/blob/master/doc/guides/writing-tests.md#test-structure

PR-URL: #19161
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Gireesh Punathil <[email protected]>
@targos targos mentioned this pull request Mar 18, 2018
MylesBorins pushed a commit that referenced this pull request Mar 20, 2018
Rename the test appropriately alongside mentioning the subsystem
Also, make a few basic changes to make sure the test conforms
to the standard test structure

Refs: #19105
Refs: https://github.com/nodejs/node/blob/master/doc/guides/writing-tests.md#test-structure

PR-URL: #19161
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Gireesh Punathil <[email protected]>
MayaLekova pushed a commit to MayaLekova/node that referenced this pull request May 8, 2018
Rename the test appropriately alongside mentioning the subsystem
Also, make a few basic changes to make sure the test conforms
to the standard test structure

Refs: nodejs#19105
Refs: https://github.com/nodejs/node/blob/master/doc/guides/writing-tests.md#test-structure

PR-URL: nodejs#19161
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Gireesh Punathil <[email protected]>
trivikr pushed a commit to trivikr/node that referenced this pull request Sep 15, 2018
Rename the test appropriately alongside mentioning the subsystem
Also, make a few basic changes to make sure the test conforms
to the standard test structure

Refs: nodejs#19105
Refs: https://github.com/nodejs/node/blob/master/doc/guides/writing-tests.md#test-structure

PR-URL: nodejs#19161
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Gireesh Punathil <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
repl Issues and PRs related to the REPL subsystem. test Issues and PRs related to the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants