Error if submodule fetch fails.#92214
Conversation
|
r? @kennytm (rust-highfive has picked a reviewer for you, use r? to override) |
|
@bors r+ rollup This makes sense to me, thanks! |
|
📌 Commit 1233ab7 has been approved by |
…ulacrum Error if submodule fetch fails. In CI, if fetching a submodule fails, the script would exit successfully. Later parts of the build will fail due to the missing files, but it is a bit confusing, and I think it would be better to error out earlier. The reason is that in bash, `wait` without arguments will exit 0 even if a background job exits with an error. The solution here is to wait on each individual job, which will return the exit code of the job. This was encountered in rust-lang#92177.
|
This is probably causing errors here: |
|
Oh, sorry about that. I did a bunch of testing when I wrote this and I never saw the tar errors. Those look like legitimate problems with the archives, I'll try to investigate more. @bors r- |
1233ab7 to
31267e8
Compare
|
@Mark-Simulacrum I pushed a fix for the extraction error. On Windows, msys will not use symlinks by default. |
|
@bors r+ rollup=iffy |
|
📌 Commit 31267e8 has been approved by |
|
⌛ Testing commit 31267e8 with merge 9f3945be2c6691c241a804d1d55c6c41cec4c634... |
|
💔 Test failed - checks-actions |
This comment has been minimized.
This comment has been minimized.
273d794 to
72508c7
Compare
For some reason, `tar` behaves differently in such a way that it does not create symlinks on Windows correctly, resulting in `Cannot create symlink to 'ld.gold': No such file or directory` errors.
|
OK, I think this is ready for review again. I had done a bunch of testing on Windows, but didn't have quite the same setup. For some reason, the MSYS2 script causes |
|
@bors r+ rollup=iffy |
|
📌 Commit 43f83bc has been approved by |
|
☀️ Test successful - checks-actions |
|
Finished benchmarking commit (8769f4e): comparison url. Summary: This benchmark run did not return any relevant results. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
In CI, if fetching a submodule fails, the script would exit successfully. Later parts of the build will fail due to the missing files, but it is a bit confusing, and I think it would be better to error out earlier.
The reason is that in bash,
waitwithout arguments will exit 0 even if a background job exits with an error. The solution here is to wait on each individual job, which will return the exit code of the job.This was encountered in #92177.