Pin OS for release pipeline to avoid compiling inconsistently #404
+1
−1
Conversation
This file contains 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
Signed-off-by: ArthurSens <arthursens2005@gmail.com>
|
I'm merging it already because I've already tested it here, and this error is blocking Workspace team with gen78 😬 |
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.
We're currently gettig the error
/lib/x86_64-linux-gnu/libc.so.6: versionGLIBC_2.32' not found` when executing the binary released by our pipeline.Missing OS libs can be a good indicator that the binary is being compiled in a different system than the one it is being executed. Looking at Github docs, I've found out the
ubuntu-latestis currently being used by Ubuntu 20 and Ubuntu 22. Our workspaces however are still using ubuntu 20 as a base image.This PR is pinning the OS of our release pipeline to the same one we use in our workspaces.
Fixes #403