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: bp fix for test-http-get-pipeline-problem.js #3013

Closed
wants to merge 1 commit into from

Conversation

mhdawson
Copy link
Member

backport fix for test-http-get-pipeline-problem.js from master
to 0.12.X. We've been seeing an intermittent failure
in runs for zLinux with SLES 12. We confirmed that this fix
resolves the issue so would like it in 0.12.X

The original commit does not apply cleanly as the paths were
changed, but the actual change is identical. The original commit was:

3ba4f71

backport fix for test-http-get-pipeline-problem.js from master
to 0.12.X.  We've been seeing an intermittent failure
in runs for zLinux with SLES 12.  We confirmed that this fix
resolves the issue so would like it in 0.12.X

The original commit does not apply cleanly as the paths were
changed, but the actual change is identical.  The original commit was:

nodejs@3ba4f71
@mhdawson
Copy link
Member Author

@jasnell can you review. If it looks ok do I need to do anything extra after landing it to add it to the 0.12.8 release proposal ?

@mhdawson mhdawson added test Issues and PRs related to the tests. land-on-v0.12 labels Sep 22, 2015
@mhdawson mhdawson self-assigned this Sep 22, 2015
@mscdex mscdex added the http Issues or PRs related to the http subsystem. label Sep 23, 2015
@jasnell
Copy link
Member

jasnell commented Sep 29, 2015

LGTM!

@mhdawson
Copy link
Member Author

@jasnell is there something needed to get this into the next 12.X release ?

@Trott
Copy link
Member

Trott commented Feb 23, 2016

Is this something that's going to get into 0.12.x at some point? Or is this something that should be closed? /cc @jasnell @mhdawson

@mhdawson
Copy link
Member Author

mhdawson commented Mar 1, 2016

Based on this from the commit message I would like it in 0.12.X

  • We've been seeing an intermittent failure in runs for zLinux with SLES 12.
    We confirmed that this fix resolves the issue so would like it in 0.12.X

@mhdawson
Copy link
Member Author

@jasnell @thealphanerd

@jasnell
Copy link
Member

jasnell commented Mar 10, 2016

@rvagg @thealphanerd ... Not quite sure why this wasn't landed in one of the recent v0.12 updates. I can get it landed into staging today but wanted to check first in case there was a reason not to.

@rvagg
Copy link
Member

rvagg commented Mar 14, 2016

No reason, just a broken workflow on my part that didn't properly take labels into account. I'm also not in a position to land this, without any access to, or understanding of zLinux. It has an LGTM so it could be landed by either @mhdawson or @jasnell.

We'll be doing another v0.12 soon enough, there's a few minor things backed up for both it and 0.10.

jasnell pushed a commit that referenced this pull request Mar 14, 2016
backport fix for test-http-get-pipeline-problem.js from master
to 0.12.X.  We've been seeing an intermittent failure
in runs for zLinux with SLES 12.  We confirmed that this fix
resolves the issue so would like it in 0.12.X

The original commit does not apply cleanly as the paths were
changed, but the actual change is identical.  The original commit was:

3ba4f71

PR-URL: #3013
Reviewed-By: Rod Vagg <[email protected]>
Reviewed-By: James M Snell <[email protected]>
@jasnell
Copy link
Member

jasnell commented Mar 14, 2016

Landed in v0.12-staging in 154098a

@jasnell jasnell closed this Mar 14, 2016
@mhdawson mhdawson deleted the backport branch May 9, 2016 22:38
jBarz pushed a commit to ibmruntimes/node that referenced this pull request Nov 4, 2016
backport fix for test-http-get-pipeline-problem.js from master
to 0.12.X.  We've been seeing an intermittent failure
in runs for zLinux with SLES 12.  We confirmed that this fix
resolves the issue so would like it in 0.12.X

The original commit does not apply cleanly as the paths were
changed, but the actual change is identical.  The original commit was:

nodejs/node@3ba4f71

PR-URL: nodejs/node#3013
Reviewed-By: Rod Vagg <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
http Issues or PRs related to the http subsystem. test Issues and PRs related to the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants