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: rename regression tests with descriptive file names (pt. 4) #19332

Closed
wants to merge 1 commit into from

Conversation

ryzokuken
Copy link
Contributor

@ryzokuken ryzokuken commented Mar 13, 2018

Rename the tests appropriately alongside mentioning the subsystem
Also, make a few basic changes to make sure the tests conform to the standard test structure

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

Checklist

  • test/parallel/test-regress-GH-io-1068.js
  • test/parallel/test-regress-GH-io-1811.js
  • test/parallel/test-regress-GH-node-9326.js

Additional files renamed

  • timers-regress-GH-9765
  • test-tls-pfx-gh-5100-regr
  • test-tls-regr-gh-5108

@nodejs-github-bot nodejs-github-bot added the test Issues and PRs related to the tests. label Mar 13, 2018
@ryzokuken
Copy link
Contributor Author

PSA: Naming commits poorly on purpose so that it's easier to rebase it in the end.

@joyeecheung
Copy link
Member

@lpinca lpinca added the wip Issues and PRs that are still a work in progress. label Mar 14, 2018
@lpinca
Copy link
Member

lpinca commented Mar 14, 2018

@ryzokuken added "in progress" label as I assumed you want to rename more tests from the checklist in the description. Let me know If I'm wrong.

@ryzokuken
Copy link
Contributor Author

ryzokuken commented Mar 15, 2018

@lpinca you're quite right, thanks. Sorry for not being able to reply immediately.

@ryzokuken
Copy link
Contributor Author

@joyeecheung the original 3 have been fixed and that ends the list in #19105. Thus, I'm adding the "Fixes: ..." reference, let me know if I shouldn't.

@lpinca lpinca removed the wip Issues and PRs that are still a work in progress. label Mar 16, 2018
@@ -1,5 +1,10 @@
'use strict';
require('../common');

// This test ensures Node doesn't crash on hitting Ctrl+C in order to terminate
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: can you please use "Node.js"?

if (!common.hasCrypto)
common.skip('missing crypto');
const fixtures = require('../common/fixtures');

// This test ensures that Node doesn't incur a segfault while accessing TLSWrap
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ditto.

'use strict';
require('../common');

// This test ensures that node doesn't crash on `process.stdin.emit("end")`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same thing.

@ryzokuken
Copy link
Contributor Author

@lpinca done.

@lpinca
Copy link
Member

lpinca commented Mar 16, 2018

@lpinca lpinca added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Mar 16, 2018

// Change kMaxLength for zlib to trigger the error without having to allocate
// large Buffers.
const buffer = require('buffer');
Copy link
Member

@lpinca lpinca Mar 16, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ryzokuken it seems that the order of these requires was part of the test. This test is now failing on all machines. Please revert this particular change.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My bad. Fixing this in a sec.

@lpinca lpinca removed the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Mar 16, 2018
@ryzokuken
Copy link
Contributor Author

@lpinca done. I shouldn't have meddled with it in the first place.

@lpinca
Copy link
Member

lpinca commented Mar 17, 2018

@ryzokuken
Copy link
Contributor Author

@lpinca they passed! 🎉

@lpinca lpinca added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Mar 18, 2018
@lpinca
Copy link
Member

lpinca commented Mar 18, 2018

@ryzokuken would you mind squashing commits? Thank you.

@ryzokuken
Copy link
Contributor Author

@lpinca sure! Just give me a second.

Rename the tests appropriately alongside mentioning the subsystem
Also, make a few basic changes to make sure the tests conform to the standard test structure

1. Renamed test-regress-GH-io-1068 to test-tty-stdin-end
2. Renamed test-regress-GH-io-1811 to test-zlib-kmaxlength-rangeerror
3. Renamed test-regress-GH-node-9326 to test-kill-segfault-freebsd
4. Renamed test-timers-regress-nodejsGH-9765 to test-timers-setimmediate-infinite-loop
5. Renamed test-tls-pfx-nodejsgh-5100-regr to test-tls-pfx-authorizationerror
6. Renamed test-tls-regr-nodejsgh-5108 to test-tls-tlswrap-segfault

Fixes: nodejs#19105
Refs: nodejs#19105
Refs: https://github.com/nodejs/node/blob/master/doc/guides/writing-tests.md#test-structure
@ryzokuken
Copy link
Contributor Author

@lpinca looks good enough?

@lpinca
Copy link
Member

lpinca commented Mar 18, 2018

@ryzokuken
Copy link
Contributor Author

@lpinca any idea what could've gone wrong?

@lpinca
Copy link
Member

lpinca commented Mar 18, 2018

AIX failure is not related, will land this later.

@lpinca
Copy link
Member

lpinca commented Mar 18, 2018

Landed in d54e0f8.

lpinca pushed a commit that referenced this pull request Mar 18, 2018
Rename the tests appropriately alongside mentioning the subsystem.
Also, make a few basic changes to make sure the tests conform to the
standard test structure.

- Rename test-regress-GH-io-1068 to test-tty-stdin-end
- Rename test-regress-GH-io-1811 to test-zlib-kmaxlength-rangeerror
- Rename test-regress-GH-node-9326 to test-kill-segfault-freebsd
- Rename test-timers-regress-GH-9765 to test-timers-setimmediate-infinite-loop
- Rename test-tls-pfx-gh-5100-regr to test-tls-pfx-authorizationerror
- Rename test-tls-regr-gh-5108 to test-tls-tlswrap-segfault

PR-URL: #19332
Fixes: #19105
Reviewed-By: Gireesh Punathil <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Weijia Wang <[email protected]>
Reviewed-By: Yuta Hiroto <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Shingo Inoue <[email protected]>
@lpinca lpinca closed this Mar 18, 2018
@lpinca
Copy link
Member

lpinca commented Mar 18, 2018

There are a few more that weren't listed in the tracking issue:

test/parallel/test-arm-math-exp-regress-1376.js
test/parallel/test-buffer-regression-649.js
test/parallel/test-dgram-regress-4496.js
test/parallel/test-dns-regress-7070.js
test/parallel/test-http-agent-maxsockets-regress-4050.js

@ryzokuken
Copy link
Contributor Author

@lpinca Indeed! I'd be making another PR covering these shortly. Thanks.

@lpinca
Copy link
Member

lpinca commented Mar 18, 2018

@ryzokuken awesome, thank you.

MylesBorins pushed a commit that referenced this pull request Mar 20, 2018
Rename the tests appropriately alongside mentioning the subsystem.
Also, make a few basic changes to make sure the tests conform to the
standard test structure.

- Rename test-regress-GH-io-1068 to test-tty-stdin-end
- Rename test-regress-GH-io-1811 to test-zlib-kmaxlength-rangeerror
- Rename test-regress-GH-node-9326 to test-kill-segfault-freebsd
- Rename test-timers-regress-GH-9765 to test-timers-setimmediate-infinite-loop
- Rename test-tls-pfx-gh-5100-regr to test-tls-pfx-authorizationerror
- Rename test-tls-regr-gh-5108 to test-tls-tlswrap-segfault

PR-URL: #19332
Fixes: #19105
Reviewed-By: Gireesh Punathil <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Weijia Wang <[email protected]>
Reviewed-By: Yuta Hiroto <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Shingo Inoue <[email protected]>
MylesBorins pushed a commit that referenced this pull request Mar 20, 2018
Rename the tests appropriately alongside mentioning the subsystem.
Also, make a few basic changes to make sure the tests conform to the
standard test structure.

- Rename test-regress-GH-io-1068 to test-tty-stdin-end
- Rename test-regress-GH-io-1811 to test-zlib-kmaxlength-rangeerror
- Rename test-regress-GH-node-9326 to test-kill-segfault-freebsd
- Rename test-timers-regress-GH-9765 to test-timers-setimmediate-infinite-loop
- Rename test-tls-pfx-gh-5100-regr to test-tls-pfx-authorizationerror
- Rename test-tls-regr-gh-5108 to test-tls-tlswrap-segfault

PR-URL: #19332
Fixes: #19105
Reviewed-By: Gireesh Punathil <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Weijia Wang <[email protected]>
Reviewed-By: Yuta Hiroto <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Shingo Inoue <[email protected]>
@targos targos mentioned this pull request Mar 20, 2018
@tniessen tniessen removed the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Mar 24, 2018
BethGriggs pushed a commit that referenced this pull request Dec 3, 2018
Rename the tests appropriately alongside mentioning the subsystem.
Also, make a few basic changes to make sure the tests conform to the
standard test structure.

- Rename test-regress-GH-io-1068 to test-tty-stdin-end
- Rename test-regress-GH-io-1811 to test-zlib-kmaxlength-rangeerror
- Rename test-regress-GH-node-9326 to test-kill-segfault-freebsd
- Rename test-timers-regress-GH-9765 to test-timers-setimmediate-infinite-loop
- Rename test-tls-pfx-gh-5100-regr to test-tls-pfx-authorizationerror
- Rename test-tls-regr-gh-5108 to test-tls-tlswrap-segfault

PR-URL: #19332
Fixes: #19105
Reviewed-By: Gireesh Punathil <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Weijia Wang <[email protected]>
Reviewed-By: Yuta Hiroto <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Shingo Inoue <[email protected]>
@BethGriggs BethGriggs mentioned this pull request Dec 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test Issues and PRs related to the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.