Revert "[tools] Use mold linker on Linux debug builds" #23239
Conversation
This reverts commit 22cbc53.
|
The error is either reporting a full disk at the end of the job (e.g. 413) or a failing job with warnings in the log such as |
BetsyMcPhail
added
status: single reviewer ok
There was a problem hiding this comment.
+@sherm1 for both reviews please
Reviewable status: LGTM missing from assignee sherm1(platform)
There was a problem hiding this comment.
@rpoyner-tri do you want to look at this before merging the revert?
Reviewable status: LGTM missing from assignees rpoyner-tri(platform),sherm1(platform)
There was a problem hiding this comment.
Reviewable status: LGTM missing from assignee rpoyner-tri(platform)
|
Note that all 3 of the failures were observed on a single pull request. So there is the possibility that the bug lies with that pull request, not with the mold switch. |
Dear @rpoyner-tri ,
The on-call build cop, @BetsyMcPhail, believes that your PR #22951 may have
broken one or more of Drake's continuous integration builds [1]. It is
possible to break a build even if your PR passed continuous integration
pre-merge because additional platforms are tested post-merge.
The specific build failures under investigation are:
https://drake-jenkins.csail.mit.edu/job/linux-noble-gcc-bazel-experimental-debug/413
https://drake-jenkins.csail.mit.edu/job/linux-noble-gcc-bazel-experimental-debug/416
https://drake-jenkins.csail.mit.edu/job/linux-noble-gcc-bazel-experimental-debug/418
Therefore, the build cop has created this revert PR and started a complete
post-merge build to determine whether your PR was in fact the cause of the
problem. If that build passes, this revert PR will be merged 60 minutes from
now. You can then fix the problem at your leisure, and send a new PR to
reinstate your change.
If you believe your original PR did not actually break the build, please
explain on this thread.
If you believe you can fix the break promptly in lieu of a revert, please
explain on this thread, and send a PR to the build cop for review ASAP.
If you believe your original PR definitely did break the build and should be
reverted, please review and LGTM this PR. This allows the build cop to merge
without waiting for CI results.
For advice on how to handle a build cop revert, see [2].
Thanks!
Your Friendly On-call Build Cop
[1] CI Production Dashboard: https://drake-jenkins.csail.mit.edu/view/Production/
[2] https://drake.mit.edu/buildcop.html#workflow-for-handling-a-build-cop-revert
This change is