ci: separate the windows CI tests into build and test#6
Conversation
Because the compiler-cli tests modify node_modules, this can cause failures on windows CI specifically as node_modules are symlinked to rather than copied. By running the test and build actions in separate commands, all of the tests are built to be executed before and tests are executed and modify the node_modules content.
|
Hello, your commit has a 89% probability of containing an issue |
|
It looks like we've not been able to train a model on this repo. Check out why at www.solittlecode.com |
|
Hello, your commit has a 89% probability of containing an issue |
|
Hello, your commit has a 89% probability of containing an issue |
|
Hello, your commit has a 84% probability of containing an issue |
|
Hello, your commit has a 84% probability of containing an issue |
|
Hello, your commit has a 89% probability of containing an issue |
5 similar comments
|
Hello, your commit has a 89% probability of containing an issue |
|
Hello, your commit has a 89% probability of containing an issue |
|
Hello, your commit has a 89% probability of containing an issue |
|
Hello, your commit has a 89% probability of containing an issue |
|
Hello, your commit has a 89% probability of containing an issue |
Because the compiler-cli tests modify node_modules, this can cause
failures on windows CI specifically as node_modules are symlinked
to rather than copied. By running the test and build actions in
separate commands, all of the tests are built to be executed before
and tests are executed and modify the node_modules content.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information