You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks to all of you for the incredible job you've done with this project!
I tried to run yarn e2e:docker, both with and without the --test-suite=all flag and the second test suite (./tasks/e2e-kitchensink.sh) always fails. However, when running the tests separately, they all pass, including e2e-kitchensink. Also, when changing the order of the test suites in tasks/local-test.sh it is always the second the one that fails.
I believe it's because after e2e-simple.sh has run, the packages are published to the local npm registry (verdaccio), and this is not cleared after the test has finished running. So when the second test suite runs, it tries to publish packages with the same version numbers as the ones published by the first test suite.
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.
First of all, thanks to all of you for the incredible job you've done with this project!
I tried to run
yarn e2e:docker
, both with and without the--test-suite=all
flag and the second test suite (./tasks/e2e-kitchensink.sh
) always fails. However, when running the tests separately, they all pass, includinge2e-kitchensink
. Also, when changing the order of the test suites intasks/local-test.sh
it is always the second the one that fails.I believe it's because after
e2e-simple.sh
has run, the packages are published to the local npm registry (verdaccio), and this is not cleared after the test has finished running. So when the second test suite runs, it tries to publish packages with the same version numbers as the ones published by the first test suite.The text was updated successfully, but these errors were encountered: