yarn build failure in CI #3849
Comments
godber
pushed a commit
that referenced
this issue
Dec 16, 2024
This PR makes the following changes: - Adds the `--verbose` flag to the root package.json `build` script and removes `--silent` from `YARN_SETUP_ARGS`. This will hopefully reveal why the script fails occasionally. ref: #3849 - Replace unmaintained `porty` library with `get-port` library. - Within the teraslice package, many tests use `findPort()` to get a random port to start a server on. The implementation did not actually return a random port and made conflicts more likely. Update `findPort()` to use `get-port`, increase the port range, and get a truly random port in that range. ref: #3848 - When starting services, log all TCP ports just before calling `docker run`. This should give us more information about why the `docker run` commands occasionally fail with a `port already in use` error. ref: #3848
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Occasionally the
yarn buildstep will fail in CI, but no errors are shown. I am thinking we could run the command in verbose mode so we can at least see the issue and be able to resolve it in the future.The text was updated successfully, but these errors were encountered: