-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add arm64 static build to GitHub actions and bundle #4552
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Works ✔️ There is a slack conversation ongoing where we could do some manual external testing: https://kubernetes.slack.com/archives/CAZH62UR1/p1612626775090600 /hold |
Codecov Report
@@ Coverage Diff @@
## master #4552 +/- ##
=======================================
Coverage 40.53% 40.53%
=======================================
Files 115 115
Lines 9442 9442
=======================================
Hits 3827 3827
Misses 5182 5182
Partials 433 433 |
9795629 to
54af5ad
Compare
54af5ad to
bbe11d0
Compare
bbe11d0 to
2efc0b3
Compare
|
I have to update the PR once crun 0.18 is available: containers/crun#604 |
2efc0b3 to
8378738
Compare
8378738 to
aaf1e21
Compare
|
/retest |
2037067 to
58014de
Compare
|
LGTM |
58014de to
03bc5a5
Compare
|
@harche: GitHub didn't allow me to request PR reviews from the following users: odinuge. Note that only cri-o members and repo collaborators can review this PR, and authors cannot review their own PRs. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
README.md
Outdated
|
|
||
| ```shell | ||
| > curl -f https://storage.googleapis.com/k8s-conform-cri-o/artifacts/crio-$(git ls-remote https://github.com/cri-o/cri-o master | cut -c1-9).tar.gz -o crio.tar.gz | ||
| > curl https://raw.githubusercontent.com/cri-o/cri-o/master/get | bash |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The url mentioned in #4587 (comment) is still valid right? Because that's what I am using in kubernetes/test-infra#20898
Would it be a good idea to have a complete URL, say as an example only for amd64, mentioned here? Just for someone who might not want to pipe a script from web into bash or someone like me who end up using complete URL in a systemd service file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that still applies. I changed the README.md to mention that URL path, too. But we have to be aware that this could cause a race (CI not finished or failed) in comparison to the script which will always succeed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, ok, then in my case, I will change the systemd service file to first download the script and execute it locally.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, this is way more safe and decouples our CI from the consumer of the script.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. I was wondering, if it's possible to keep the old url around for sometime. It would take me sometime to get this tested and added in test-infra. Until then the periodic job, will keep failing :(
Just checking if it's possible, hate to see the prow dashboard in red :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really like this approach @saschagrunert! The old one was kinda fragile, so thanks!
harche
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks cool @saschagrunert. Just a couple of queries, but otherwise LGTM. :)
53e69a2 to
5cc86ab
Compare
Thank you! Please also note: |
get
Outdated
| #!/usr/bin/env bash | ||
| set -euo pipefail | ||
|
|
||
| ARCH=${1:-amd64} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be nice to just default to empty, and use uname to detec the correct arch.
$ uname -m #x86
x86_64
$ uname -m #arm64
aarch64
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reworked the script to now accept parsed CLI arguments as well as a help output. We now fallback to uname -m (converted to amd64/arm64), too. :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome!! 😄
README.md
Outdated
|
|
||
| ```shell | ||
| > curl -f https://storage.googleapis.com/k8s-conform-cri-o/artifacts/crio-$(git ls-remote https://github.com/cri-o/cri-o master | cut -c1-9).tar.gz -o crio.tar.gz | ||
| > curl https://raw.githubusercontent.com/cri-o/cri-o/master/get | bash |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really like this approach @saschagrunert! The old one was kinda fragile, so thanks!
668c772 to
d6f6b5a
Compare
|
/test kata-containers |
|
@haircommander do you think we can get this one in? |
|
/lgtm |
|
I know I just gave this lgtm, but I've realized I'm hesitant to introduce a script to the top level of the tree /lgtm cancel can we move it to the scripts/ directory? or is there a reason to keep it top-level? |
This adds a new derivation to build statically linked binaries for arm64. Signed-off-by: Sascha Grunert <[email protected]>
d6f6b5a to
4ff8662
Compare
Yes sure, moved the script into the |
|
/lgtm thanks @saschagrunert 😃 |
|
/test integration_fedora |
2 similar comments
|
/test integration_fedora |
|
/test integration_fedora |
|
@saschagrunert: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
/test kata-containers |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This adds a new derivation to build statically linked binaries for
arm64.
Which issue(s) this PR fixes:
Refers to #4551
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?