Open
Conversation
Following v5.5.0 -> v5.25.0 upgrade, brig crashed on `AMD EPYC 7282` CPU (exposed on `kubernetes2`/`kubernetes3`, see [JIRA Ticket](https://wearezeta.atlassian.net/browse/WPB-24549)). It seems that, since GHC 9.8.1, GHC is more aggressively optimizing for the underlying CPU architecture, the CI build machines being more recent, it prevents older CPUs to run the generated binaries.
2f95483 to
66dea10
Compare
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
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.
Following v5.5.0 -> v5.25.0 upgrade, brig crashed on
AMD EPYC 7282CPU (exposed onkubernetes2/kubernetes3, see JIRATicket).
It seems that, since GHC 9.8.1, GHC is more aggressively optimizing for the underlying CPU architecture, the CI build machines being more recent, it prevents older CPUs to run the generated binaries.
Checklist
changelog.d