-
Notifications
You must be signed in to change notification settings - Fork 149
Closed
Labels
CIIssues tied with CI/CD workflows.Issues tied with CI/CD workflows.bugSomething isn't workingSomething isn't workinginternalInternal or build-related changesInternal or build-related changes
Description
Version(s)
ebafbb8
Describe the bug
The generate-windows-launcher job got extremely flaky, seemingly failing very often on the cs download.
We should investigate and try to fix it, as it otherwise forces us to restart jobs to no end.
Example failing build:
Example output:
download error: Caught java.net.ConnectException (Connection timed out: connect) while downloading https://download.libsodium.org/libsodium/releases/libsodium-1.0.18-stable-msvc.zip
1 targets failed
cli[3.3.3].base-image.staticLibDir os.SubprocessException: Result of C:\Users\runneradmin\AppData\Local\Coursier\cache\arc\https\github.com\coursier\coursier\releases\download\v2.1.10\cs-x86_64-pc-win32.zip\cs-x86_64-pc-win32.exe�: 1
os.proc.call(ProcessOps.scala:95)
millbuild.project.settings$CliLaunchers$CliNativeImage.copyLibsodiumStaticTo(settings.sc:239)
millbuild.project.settings$CliLaunchers$CliNativeImage.$anonfun$staticLibDir$2(settings.sc:280)
mill.define.Task$TraverseCtx.evaluate(Task.scala:71)
To Reproduce
Just run any CI job on main, the generate-windows-launcher job will fail ~4 times out of 5.
Expected behaviour
The generate-windows-launcher job should be passing consistently.
Potential solutions
We could try increasing the timeout or retrying the download.
Metadata
Metadata
Assignees
Labels
CIIssues tied with CI/CD workflows.Issues tied with CI/CD workflows.bugSomething isn't workingSomething isn't workinginternalInternal or build-related changesInternal or build-related changes