TEST: Attempt to catch gcc~binutils bug with build-ci#32
Draft
TEST: Attempt to catch gcc~binutils bug with build-ci#32
gcc~binutils bug with build-ci#32Conversation
Member
Author
|
In this first attempt, it didn't catch the bug. Was it fixed in the current |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Background
Apologies for hyjacking this repo for unrelated testing!
See ACCESS-NRI/spack-config#95 (comment) (and earlier). We need to see if
build-ciis capable of catching compiler bugs from updates tobuiltins.