lf-edge
more pkgs: no more package bumping
Description
use automatic hashes provided by linuxkit to avoid having to bump manually like crazy
this is doing the same as https://github.com/lf-edge/eve/pull/5190 but for other packages
PR dependencies
- Bump of Linuxkit with this feature included
- https://github.com/lf-edge/eve/pull/5227
How to test and validate this PR
There are no specific steps to validate, common EVE Test Plan should cover the functionality.
Changelog notes
internal change
PR Backports
For all current LTS branches, please state explicitly if this PR should be backported or not. This section is used by our scripts to track the backports, so, please, do not omit it.
Here is the list of current LTS branches (it should be always up to date):
- 14.5-stable: no
- 13.4-stable: no
Checklist
- [x] I've provided a proper description
- [x] I've added the proper documentation
- [x] I've tested my PR on amd64 device
- [x] I've tested my PR on arm64 device
- [x] I've written the test verification instructions
- [x] I've set the proper labels to this PR
And the last but not least:
- [x] I've checked the boxes above, or I've provided a good reason why I didn't check them.
Please, check the boxes above after submitting the PR in interactive mode.
arm64/nvidia: 2025-09-17T12:15:37.6729557Z Error: error building "lfedge/eve-vector:0238d6694e978cae3f7c3c8ce888d68aa363de7a": error building for arch arm64: failed to solve: ResourceExhausted: process "/bin/sh -c cargo build --release $VECTOR_FEATURES" did not complete successfully: cannot allocate memory
If a single PR changes too many files there will be an issue to generate/apply patch and Yetus will complain, we see this a lot for PRs updating vendor files, that's the case for this one as well:
2025-09-18T09:00:05.8643968Z HEAD is now at 6fbb49bdf Merge c29c97c5cdba9632a46ccb743533f8444ae1c3de into d3defeded2a3596fa016f92f036deb8fe27c5cfa
2025-09-18T09:00:06.0839227Z Previous HEAD position was 6fbb49bdf Merge c29c97c5cdba9632a46ccb743533f8444ae1c3de into d3defeded2a3596fa016f92f036deb8fe27c5cfa
2025-09-18T09:00:06.0849591Z Switched to a new branch 'master'
2025-09-18T09:00:06.0850246Z Branch 'master' set up to track remote branch 'master' from 'origin'.
2025-09-18T09:00:06.5896571Z Already up to date.
2025-09-18T09:00:06.6824146Z Already on 'master'
2025-09-18T09:00:06.6831991Z Your branch is up to date with 'origin/master'.
2025-09-18T09:00:07.3016668Z HEAD is now at fdc3a4eee Kernel update - [amd64-generic]
2025-09-18T09:00:07.4455121Z ERROR: GH:5219 does not apply to master.
2025-09-18T09:00:07.4478270Z ##[endgroup]
2025-09-18T09:00:07.4478632Z ##[group]Generating Reports . . .
@christoph-zededa I see you have some commits in the PR that were picked up from master, do you need to rebase the branch?
@christoph-zededa I see you have some commits in the PR that were picked up from master, do you need to rebase the branch?
done
@christoph-zededa I guess https://github.com/lf-edge/eve/pull/5228 can be closed then in favor of this one
@christoph-zededa I guess #5228 can be closed then in favor of this one
ok, feel free to close it then.
@christoph-zededa I guess #5228 can be closed then in favor of this one
ok, feel free to close it then.
Actually I removed that commit right now because of https://github.com/lf-edge/eve/pull/5228#discussion_r2363694810
2025-09-20T02:37:11.5982545Z #9 8.105 ERROR: Failed to create usr/lib/llvm13/lib/libLLVMAArch64CodeGen.a: No space left on device
2025-09-20T02:37:11.5982545Z #9 8.105 ERROR: Failed to create usr/lib/llvm13/lib/libLLVMAArch64CodeGen.a: No space left on device
Which runner?
2025-09-20T02:37:11.5982545Z #9 8.105 ERROR: Failed to create usr/lib/llvm13/lib/libLLVMAArch64CodeGen.a: No space left on device
Which runner?
Unfortunately I cannot find it anymore - it was in 'Go Tests'. Let's see if it fails again ...
2025-09-20T02:37:11.5982545Z #9 8.105 ERROR: Failed to create usr/lib/llvm13/lib/libLLVMAArch64CodeGen.a: No space left on device
Which runner?
Unfortunately I cannot find it anymore - it was in 'Go Tests'. Let's see if it fails again ...
it should be this one:
Unfortunately when I click on it, I get to a pipeline running for about 30 minutes. For sure 2:43am GMT+2 is more than 30 minutes ago.
minutes ago.
We run go tests on free GitHub provided runners, they have limitation on disk size, if it becomes too much we can always switch to SH runners
We run go tests on free GitHub provided runners, they have limitation on disk size, if it becomes too much we can always switch to SH runners
it happened again; seems like we should do that ...
Moving this into draft as we should first solve https://github.com/linuxkit/linuxkit/pull/4176