ci: use 20.04 on x86_64-gnu-nopt builder#79536
Merged
bors merged 1 commit intorust-lang:masterfrom Dec 10, 2020
Merged
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Switch the
x86_64-gnu-noptbuilder to use Ubuntu 20.04.Ubuntu 20.04 has a more recent gdb version than Ubuntu 16.04 (9.1 vs 7.11.1), which is required for #77117, as 16.04's gdb 7.11.1 crashes in some cases with Split DWARF.
x86_64-gnu-noptis chosen because it runs compare modes, which is how Split DWARF testing is implemented in #77117.I've not confirmed that the issue is resolved with gdb 9.1 (Feb 2020), but system was using gdb 9.2 (May 2020) and that was fine and it seems more likely to me that the bug was resolved between gdb 7.11.1 (May 2016) and gdb 9.1.
Updating a builder to use 20.04 was suggested by @Mark-Simulacrum in #77117 (comment). I'm not sure if this is the only change that is required - if more are necessary then I'm happy to do that.
r? @pietroalbini
cc @Mark-Simulacrum