★ wanayoo — archive 1999 https://github.com/nodejs/node/pull/25011Nouvelle recherche | Portail wanayoo
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

Jump to bottom

build: add a space to clarify skipping crypto msg #25011

Closed
wants to merge 2 commits into from
Closed

build: add a space to clarify skipping crypto msg #25011

wants to merge 2 commits into from

Conversation

danbev
Copy link
Member

@danbev danbev commented Dec 13, 2018 •
edited

This commit adds a space to the message that is displayed for tests that
are skipped when node was built --without-ssl. For example, this is what
is currently displayed:

"release test-https-agent-additional-optionsSkipping as node was compiled
without crypto support"

After this change this will be:

"release test-https-agent-additional-options: Skipping as node was compiled
without crypto support"
Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines

@nodejs-github-bot
Copy link
Contributor

@nodejs-github-bot nodejs-github-bot commented Dec 13, 2018

@danbev build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/1922/pipeline

@nodejs-github-bot nodejs-github-bot added the test label Dec 13, 2018
@danbev
build: add a space to clarify skipping crypto msg
bead436 
This commit adds a space to the message that is displayed for tests that
are skipped when node was built --without-ssl. For example, this is what
is currently displayed:
"release test-https-agent-additional-optionsSkipping as node was
compiled without crypto support"

After this change this will be:
"release test-https-agent-additional-options Skipping as node was
compiled without crypto support"
@danbev danbev force-pushed the build-without-ssl-skipping-msg branch from 01b4894 to bead436 Compare Dec 13, 2018
BridgeAR
BridgeAR approved these changes Dec 13, 2018
View changes
Copy link
Member

@BridgeAR BridgeAR left a comment

LGTM but I would even go a bit further and add a colon or something like that to make it even more clear.

@danbev
Copy link
Member Author

@danbev danbev commented Dec 14, 2018

CI: https://ci.nodejs.org/job/node-test-pull-request/19504/

@Trott
Copy link
Member

@Trott Trott commented Dec 14, 2018

Resume Build CI: https://ci.nodejs.org/job/node-test-pull-request/19510/

@Trott
Copy link
Member

@Trott Trott commented Dec 14, 2018 •
edited

Re-run ARM CI: https://ci.nodejs.org/job/node-test-commit-arm/20809/ ✔️

@Trott
Copy link
Member

@Trott Trott commented Dec 14, 2018 •
edited

ARM was the only red result in the last CI run with a pair of addon failures seen elsewhere on ARM CI runs, and the re-run of ARM is green, so CI is effectively green.

@danbev
Copy link
Member Author

@danbev danbev commented Dec 17, 2018

Landed in 1631052.

@danbev danbev closed this Dec 17, 2018
@danbev danbev deleted the build-without-ssl-skipping-msg branch Dec 17, 2018
@thefourtheye
Copy link
Contributor

@thefourtheye thefourtheye commented Dec 17, 2018 •
edited

@danbev The landed commit is missing the metadata.

@danbev
Copy link
Member Author

@danbev danbev commented Dec 17, 2018

@thefourtheye :( Thanks, I'm going to fix and force push.

pull bot pushed a commit to zys-contrib/node that referenced this issue Dec 17, 2018
@danbev
build: add a space to clarify skipping crypto msg
a361b94 
This commit adds a space to the message that is displayed for tests that
are skipped when node was built --without-ssl. For example, this is what
is currently displayed:
"release test-https-agent-additional-optionsSkipping as node was
compiled without crypto support"

After this change this will be:
"release test-https-agent-additional-options: Skipping as node was
compiled without crypto support"

PR-URL: nodejs#25011
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
MylesBorins pushed a commit that referenced this issue Dec 25, 2018
@danbev @MylesBorins
build: add a space to clarify skipping crypto msg
4513516 
This commit adds a space to the message that is displayed for tests that
are skipped when node was built --without-ssl. For example, this is what
is currently displayed:
"release test-https-agent-additional-optionsSkipping as node was
compiled without crypto support"

After this change this will be:
"release test-https-agent-additional-options: Skipping as node was
compiled without crypto support"

PR-URL: #25011
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
@MylesBorins MylesBorins mentioned this pull request Dec 25, 2018
Merged
refack pushed a commit to refack/node that referenced this issue Jan 14, 2019
@danbev @refack
build: add a space to clarify skipping crypto msg
ceb823a 
This commit adds a space to the message that is displayed for tests that
are skipped when node was built --without-ssl. For example, this is what
is currently displayed:
"release test-https-agent-additional-optionsSkipping as node was
compiled without crypto support"

After this change this will be:
"release test-https-agent-additional-options: Skipping as node was
compiled without crypto support"

PR-URL: nodejs#25011
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
BethGriggs pushed a commit that referenced this issue Apr 17, 2019
@danbev @BethGriggs
build: add a space to clarify skipping crypto msg
ec896f9 
This commit adds a space to the message that is displayed for tests that
are skipped when node was built --without-ssl. For example, this is what
is currently displayed:
"release test-https-agent-additional-optionsSkipping as node was
compiled without crypto support"

After this change this will be:
"release test-https-agent-additional-options: Skipping as node was
compiled without crypto support"

PR-URL: #25011
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
BethGriggs pushed a commit that referenced this issue Apr 28, 2019
@danbev @BethGriggs
build: add a space to clarify skipping crypto msg
e5b7eb7 
This commit adds a space to the message that is displayed for tests that
are skipped when node was built --without-ssl. For example, this is what
is currently displayed:
"release test-https-agent-additional-optionsSkipping as node was
compiled without crypto support"

After this change this will be:
"release test-https-agent-additional-options: Skipping as node was
compiled without crypto support"

PR-URL: #25011
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
@BethGriggs BethGriggs mentioned this pull request May 1, 2019
Merged
MylesBorins pushed a commit that referenced this issue May 16, 2019
@danbev @MylesBorins
build: add a space to clarify skipping crypto msg
5760e41 
This commit adds a space to the message that is displayed for tests that
are skipped when node was built --without-ssl. For example, this is what
is currently displayed:
"release test-https-agent-additional-optionsSkipping as node was
compiled without crypto support"

After this change this will be:
"release test-https-agent-additional-options: Skipping as node was
compiled without crypto support"

PR-URL: #25011
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
@beevelop beevelop mentioned this pull request May 29, 2019
Closed
@beevelop beevelop mentioned this pull request May 29, 2019
Closed
@beevelop beevelop mentioned this pull request May 29, 2019
Closed
@beevelop beevelop mentioned this pull request May 29, 2019
Closed
@beevelop beevelop mentioned this pull request May 29, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@thefourtheye thefourtheye

@lpinca lpinca

@richardlau richardlau

@BridgeAR BridgeAR

Assignees
No one assigned
Labels
test
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
7 participants
@danbev @nodejs-github-bot @Trott @thefourtheye @lpinca @richardlau @BridgeAR