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

benchmark: fix child-process-exec-stdout on win #7178

Conversation

bzoz
Copy link
Contributor

@bzoz bzoz commented Jun 6, 2016

Checklist
  • the commit message follows commit guidelines
Affected core subsystem(s)

benchmark

Description of change

This benchmark fails on Windows when trying to execute command which
is more than 32k in size. This commits skips this one case when running
under Windows.

cc @nodejs/benchmarking

This benchmark fails on Windows when trying to execute command which
is more than 32k in size. This commits skips this one case when running
under Windows.
@nodejs-github-bot nodejs-github-bot added the benchmark Issues and PRs related to the benchmark subsystem. label Jun 6, 2016
@thefourtheye
Copy link
Contributor

thefourtheye commented Jun 6, 2016

cc @nodejs/platform-windows

@mscdex mscdex added child_process Issues and PRs related to the child_process subsystem. windows Issues and PRs related to the Windows platform. labels Jun 6, 2016
@mscdex
Copy link
Contributor

mscdex commented Jun 6, 2016

/cc @Trott

@Trott
Copy link
Member

Trott commented Jun 6, 2016

LGTM

1 similar comment
@orangemocha
Copy link
Contributor

LGTM

orangemocha pushed a commit that referenced this pull request Jun 10, 2016
This benchmark fails on Windows when trying to execute command which
is more than 32k in size. This commits skips this one case when running
under Windows.

PR-URL: #7178
Reviewed-By: Trott - Rich Trott <rtrott@gmail.com>
Reviewed-By: orangemocha - Alexis Campailla <orangemocha@nodejs.org>
@orangemocha
Copy link
Contributor

CI is green: https://ci.nodejs.org/job/node-test-pull-request/2974/

Landed in 5386b23. Thanks!

evanlucas pushed a commit that referenced this pull request Jun 16, 2016
This benchmark fails on Windows when trying to execute command which
is more than 32k in size. This commits skips this one case when running
under Windows.

PR-URL: #7178
Reviewed-By: Trott - Rich Trott <rtrott@gmail.com>
Reviewed-By: orangemocha - Alexis Campailla <orangemocha@nodejs.org>
@evanlucas evanlucas mentioned this pull request Jun 16, 2016
@MylesBorins
Copy link
Contributor

MylesBorins commented Jul 11, 2016

@orangemocha should this be landed in lts?

@orangemocha
Copy link
Contributor

@thealphanerd I would say yes, though it's not critical.

MylesBorins pushed a commit that referenced this pull request Jul 14, 2016
This benchmark fails on Windows when trying to execute command which
is more than 32k in size. This commits skips this one case when running
under Windows.

PR-URL: #7178
Reviewed-By: Trott - Rich Trott <rtrott@gmail.com>
Reviewed-By: orangemocha - Alexis Campailla <orangemocha@nodejs.org>
MylesBorins pushed a commit that referenced this pull request Jul 14, 2016
This benchmark fails on Windows when trying to execute command which
is more than 32k in size. This commits skips this one case when running
under Windows.

PR-URL: #7178
Reviewed-By: Trott - Rich Trott <rtrott@gmail.com>
Reviewed-By: orangemocha - Alexis Campailla <orangemocha@nodejs.org>
@MylesBorins MylesBorins mentioned this pull request Jul 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
benchmark Issues and PRs related to the benchmark subsystem. child_process Issues and PRs related to the child_process subsystem. windows Issues and PRs related to the Windows platform.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants