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

test: Fix yarn run <failing script> test on Windows #6222

Merged

Conversation

Gudahtt
Copy link
Member

@Gudahtt Gudahtt commented Aug 3, 2018

Summary

This test was failing on Windows with the following error:

'false' is not recognized as an internal or external command,
operable program or batch file.

The script used for this test is false. This is valid in Bash, but is
not valid in cmd.exe. It has been replaced with exit 1, which will
exit with a status of 1 in both Bash and cmd.exe

The reason this test was passing on AppVeyor is that they have Cygwin
installed by default. This includes a binary called false.

Test plan

N/A

This test was failing on Windows with the following error:
```
'false' is not recognized as an internal or external command,
operable program or batch file.
```

The script used for this test is `false`. This is valid in Bash, but is
not valid in cmd.exe. It has been replaced with `exit 1`, which will
exit with a status of `1` in both Bash and cmd.exe

The reason this test was passing on AppVeyor is that they have Cygwin
installed by default. This includes a binary called `false`.
@Gudahtt Gudahtt force-pushed the fix-run-failing-test-script-on-windows branch from f8b6b4b to b6c841d Compare August 3, 2018 21:02
@Gudahtt Gudahtt changed the title Fix yarn run <failing script> test on Windows test: Fix yarn run <failing script> test on Windows Aug 5, 2018
@arcanis arcanis merged commit 3fda537 into yarnpkg:master Aug 6, 2018
@arcanis
Copy link
Member

arcanis commented Aug 6, 2018

👍

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