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

Isaacs/fix tests and fail properly #1719

Closed

Conversation

isaacs
Copy link
Contributor

@isaacs isaacs commented Aug 24, 2020

Set the exit code properly when a command fails.

Fix the failure that our CI wasn't detecting for this reason.

This flag no longer exists.  We just always exit now when we're done.
Also, test this with a mock, so that tests pass in CI.
@isaacs isaacs requested a review from ruyadorno August 24, 2020 22:25
@isaacs isaacs requested a review from a team as a code owner August 24, 2020 22:25
@isaacs isaacs changed the base branch from latest to release/v7.0.0-beta August 24, 2020 22:25
@@ -323,6 +323,9 @@ t.test('npm.load', t => {
])
t.same(consoleLogs, [['@foo']])
})

// need this here or node 10 will improperly end the promise ahead of time
await new Promise((res) => setTimeout(res))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is crazy hacky, would love to learn about the edge case going on here

ruyadorno pushed a commit that referenced this pull request Aug 25, 2020
* Also, test this with a mock, so that tests pass in CI.
* test: streamline snapshot on config test
* test: add workaround for node 10's broken promises
* test: make cache dir cross-platform consistent in config test

PR-URL: #1719
Credit: @isaacs
Close: #1719
Reviewed-by: @ruyadorno
@ruyadorno ruyadorno closed this Aug 25, 2020
@isaacs isaacs deleted the isaacs/fix-tests-and-fail-properly branch October 2, 2020 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants