-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
assert: fix actual & expected input #19925
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 makes sure the actual and expected values on the error thrown by `assert.throws` etc. are always as they should be.
nodejs-github-bot
added
the
assert
Issues and PRs related to the assert subsystem.
label
Apr 11, 2018
Many of the failures seem related to #18994 |
mcollina
approved these changes
Apr 12, 2018
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Can you rebase? The CI failures should be solved. |
New CI as requested: https://ci.nodejs.org/job/node-test-pull-request/14223/ |
BridgeAR
added
the
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
label
Apr 12, 2018
trivikr
approved these changes
Apr 12, 2018
jasnell
approved these changes
Apr 12, 2018
Landed in 7101107 |
BridgeAR
added a commit
to BridgeAR/node
that referenced
this pull request
Apr 13, 2018
This makes sure the actual and expected values on the error thrown by `assert.throws` etc. are always as they should be. PR-URL: nodejs#19925 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
jasnell
pushed a commit
that referenced
this pull request
Apr 16, 2018
This makes sure the actual and expected values on the error thrown by `assert.throws` etc. are always as they should be. PR-URL: #19925 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
BridgeAR
added a commit
to BridgeAR/node
that referenced
this pull request
May 1, 2018
This makes sure the actual and expected values on the error thrown by `assert.throws` etc. are always as they should be. PR-URL: nodejs#19925 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
assert
Issues and PRs related to the assert subsystem.
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
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 makes sure the actual and expected values on the error thrown
by
assert.throws
etc. are always as they should be.Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes