-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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 benchmark-dgram to sequential #21144
Closed
apapirovski
wants to merge
1
commit into
nodejs:master
from
apapirovski:fix-move-dgram-to-sequential
Closed
test: move benchmark-dgram to sequential #21144
apapirovski
wants to merge
1
commit into
nodejs:master
from
apapirovski:fix-move-dgram-to-sequential
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This test uses hardcoded ports, it should not be located in parallel.
Please 👍 here to approve fast-tracking. |
targos
approved these changes
Jun 5, 2018
cjihrig
approved these changes
Jun 5, 2018
joyeecheung
approved these changes
Jun 5, 2018
trivikr
approved these changes
Jun 6, 2018
trivikr
added
the
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
label
Jun 6, 2018
Trott
reviewed
Jun 6, 2018
@@ -4,6 +4,10 @@ require('../common'); | |||
|
|||
const runBenchmark = require('../common/benchmark'); | |||
|
|||
// Because the dgram benchmarks use hardcoded ports, this should be in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: Maybe mention common.PORT
?
Trott
approved these changes
Jun 6, 2018
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with or without my nit addressed. +1 to fast-tracking.
Landed in d0943bc |
Trott
pushed a commit
to Trott/io.js
that referenced
this pull request
Jun 6, 2018
This test uses hardcoded ports, it should not be located in parallel. PR-URL: nodejs#21144 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
MylesBorins
pushed a commit
that referenced
this pull request
Jun 6, 2018
This test uses hardcoded ports, it should not be located in parallel. PR-URL: #21144 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
fast-track
PRs that do not need to wait for 48 hours to land.
test
Issues and PRs related to the tests.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This test uses hardcoded ports, it should not be located in parallel.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes