test: add test-fs-read-buffer-to-string-fail as pass and flaky to all platforms - #14495
Closed
Jeyanthinath wants to merge 4 commits into
Closed
test: add test-fs-read-buffer-to-string-fail as pass and flaky to all platforms#14495Jeyanthinath wants to merge 4 commits into
Jeyanthinath wants to merge 4 commits into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
refack
approved these changes
Jul 26, 2017
cjihrig
approved these changes
Jul 26, 2017
Copy link
Copy Markdown
Member
|
I'm kind of -1, until my suggestion in #14430 (comment) gets tried out. |
Sorry, something went wrong.
For consistency with 4.x and 8.x. This commit also contains a forward port of nodejs#14232 to confirm that 4.x and 6.x behave identically with respect to the port argument. PR-URL: nodejs#14234 Refs: nodejs#14205 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
root_cert_vector currently has file scope and external linkage, but is only used in the NewRootCertsStore function. If this is not required to be externally linked perhaps it can be changed to be static and function scoped instead. PR-URL: nodejs#12788 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Shigeki Ohtsu <ohtsu@ohtsu.org>
root_cert_store is defined as extern in node_crypto.h but only used in node_crypto.cc. It is then set using SSL_CTX_set_cert_store. The only usages of SSL_CTX_get_cert_store are in node_crypto.cc which would all be accessing the same X509_STORE through the root_cert_store pointer as far as I can tell. Am I missing something here? This commit suggests removing it from the header and making it static in node_crypto.cc. PR-URL: nodejs#13194 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
MylesBorins
force-pushed
the
v6.x-staging
branch
from
7b8fcf8 to
f4691bb
Compare
August 1, 2017 07:09
Copy link
Copy Markdown
Member
|
I think this would require rebasing (again), I'm 👍 in flagging it as flaky. |
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
|
@Jeyanthinath I'll help with the rebasing... |
Sorry, something went wrong.
PR-URL: nodejs#14495 Fixes: nodejs#14430 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Copy link
Copy Markdown
Contributor
|
@nodejs/lts I keep forgetting what's the policy on landing to staging, so FYC... |
Sorry, something went wrong.
MylesBorins
force-pushed
the
v6.x-staging
branch
from
782b8bb to
e79c054
Compare
August 12, 2017 00:11
Merged
This was referenced Sep 5, 2017
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #14430 [v6.x] test: investigate test-fs-read-buffer-tostring-fail