-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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: support writing test output to file #934
Closed
Closed
Conversation
This file contains 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
This is a minimal effort to support test output written both to stdout and file in order to get our buildbots understanding test output.
LGTM. |
Another LGTM. |
rvagg
pushed a commit
that referenced
this pull request
Feb 24, 2015
This is a minimal effort to support test output written both to stdout and file in order to get our buildbots understanding test output. PR-URL: #934 Reviewed-By: Chris Dickinson <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
love it, thanks for doing the work @jbergstroem landed in a7bdce2 |
This was referenced Feb 24, 2015
petkaantonov
pushed a commit
to petkaantonov/io.js
that referenced
this pull request
Feb 25, 2015
This is a minimal effort to support test output written both to stdout and file in order to get our buildbots understanding test output. PR-URL: nodejs#934 Reviewed-By: Chris Dickinson <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
orangemocha
added a commit
to orangemocha/node
that referenced
this pull request
Jun 9, 2015
This is a minimal effort to support test output written both to stdout and file in order to get our buildbots understanding test output. Cherry picked from jbergstroem/node@3194073 Original commit message follows: PR-URL: nodejs/node#934 Reviewed-By: Chris Dickinson <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Conflicts: tools/test.py
orangemocha
added a commit
to orangemocha/node
that referenced
this pull request
Jul 7, 2015
This is a minimal effort to support test output written both to stdout and file in order to get our buildbots understanding test output. Cherry picked from jbergstroem/node@3194073 Original commit message follows: PR-URL: nodejs/node#934 Reviewed-By: Chris Dickinson <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Conflicts: tools/test.py
orangemocha
added a commit
to orangemocha/node
that referenced
this pull request
Jul 8, 2015
This is a minimal effort to support test output written both to stdout and file in order to get our buildbots understanding test output. Cherry picked from jbergstroem/node@3194073 Original commit message follows: PR-URL: nodejs/node#934 Reviewed-By: Chris Dickinson <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Conflicts: tools/test.py
orangemocha
added a commit
to orangemocha/node
that referenced
this pull request
Jul 8, 2015
This is a minimal effort to support test output written both to stdout and file in order to get our buildbots understanding test output. Cherry picked from jbergstroem/node@3194073 Original commit message follows: PR-URL: nodejs/node#934 Reviewed-By: Chris Dickinson <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Conflicts: tools/test.py
orangemocha
added a commit
to nodejs/node-v0.x-archive
that referenced
this pull request
Jul 10, 2015
This is a minimal effort to support test output written both to stdout and file in order to get our buildbots understanding test output. Cherry picked from jbergstroem/node@3194073 Original commit message follows: PR-URL: nodejs/node#934 Reviewed-By: Chris Dickinson <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Conflicts: tools/test.py Reviewed-By: Julien Gilli <[email protected]> PR-URL: #25653
orangemocha
added a commit
to orangemocha/node
that referenced
this pull request
Jul 14, 2015
This is a minimal effort to support test output written both to stdout and file in order to get our buildbots understanding test output. Cherry picked from jbergstroem/node@3194073 Original commit message follows: PR-URL: nodejs/node#934 Reviewed-By: Chris Dickinson <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Conflicts: tools/test.py Conflicts: tools/test.py
orangemocha
added a commit
to orangemocha/node
that referenced
this pull request
Jul 15, 2015
This is a minimal effort to support test output written both to stdout and file in order to get our buildbots understanding test output. Cherry picked from jbergstroem/node@3194073 Original commit message follows: PR-URL: nodejs/node#934 Reviewed-By: Chris Dickinson <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Conflicts: tools/test.py Conflicts: tools/test.py
orangemocha
added a commit
to nodejs/node-v0.x-archive
that referenced
this pull request
Jul 17, 2015
This is a minimal effort to support test output written both to stdout and file in order to get our buildbots understanding test output. Cherry picked from jbergstroem/node@3194073 Original commit message follows: PR-URL: nodejs/node#934 Reviewed-By: Chris Dickinson <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Conflicts: tools/test.py Conflicts: tools/test.py PR-URL: #25686 Reviewed-By: Julien Gilli <[email protected]>
jBarz
pushed a commit
to ibmruntimes/node
that referenced
this pull request
Nov 4, 2016
This is a minimal effort to support test output written both to stdout and file in order to get our buildbots understanding test output. Cherry picked from jbergstroem/node@3194073 Original commit message follows: PR-URL: nodejs/node#934 Reviewed-By: Chris Dickinson <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Conflicts: tools/test.py Reviewed-By: Julien Gilli <[email protected]> PR-URL: nodejs#25653
Closed
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.
This is a minimal effort to support test output written both to stdout and file in order to get our buildbots understanding test output.
On request I can convert all printing to go through the logger, but I didn't really see the need.
/r @rvagg