-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI (buildkite): ensure passing --output-sync when passing -j #42511
Conversation
To be at feature-parity with old buildbots.
Could you explain what this does? |
Just FYI, right now we are only running Buildkite agents on the newer AMDCI machines, but eventually, as we transition everything from Buildbot to Buildkite, we may end up running some Buildkite agents on some of the older machines as well. |
But if your concern (about old machines) is only about having too old a version of |
Yes, our grand plan is to not have ancient tool versions anymore, just ancient glibc versions. |
We need to update the coverage pipeline signature before merging this PR. |
I updated the signature. |
Looks like a I missed the ASAN builder, but I don't see where it called make -j Separately, the linux32 trampolines seem to have an error in them (according to the linker) @staticfloat |
To be at feature-parity with old buildbots. (cherry picked from commit 82f60b4)
To be at feature-parity with old buildbots. (cherry picked from commit 82f60b4)
To be at feature-parity with old buildbots. (cherry picked from commit 82f60b4)
…ng#42511) To be at feature-parity with old buildbots.
…ng#42511) To be at feature-parity with old buildbots.
To be at feature-parity with old buildbots. (cherry picked from commit 82f60b4)
To be at feature-parity with old buildbots (assuming the buildkite workers aren't ancient dinosaurs like some of the buildbots).