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 benchmark-dgram to sequential #21144

Closed

Conversation

apapirovski
Copy link
Member

This test uses hardcoded ports, it should not be located in parallel.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • commit message follows commit guidelines

This test uses hardcoded ports, it should not be located in parallel.
@apapirovski apapirovski added the test Issues and PRs related to the tests. label Jun 5, 2018
@apapirovski
Copy link
Member Author

@apapirovski
Copy link
Member Author

Please 👍 here to approve fast-tracking.

@trivikr 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 Trott added the fast-track PRs that do not need to wait for 48 hours to land. label 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
Copy link
Member

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?

Copy link
Member

@Trott Trott left a 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.

@Trott
Copy link
Member

Trott commented Jun 6, 2018

Landed in d0943bc

@Trott Trott closed this Jun 6, 2018
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>
@MylesBorins MylesBorins mentioned this pull request Jun 6, 2018
@apapirovski apapirovski deleted the fix-move-dgram-to-sequential branch June 7, 2018 13:40
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants