-
Notifications
You must be signed in to change notification settings - Fork 109
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
RPM build workflow failing for github actions #1156
Comments
Looks like this seems to be a bug in usermode, https://pagure.io/usermode/issue/12. Since we cannot devise a working workaround for this we will have to disable the workflow if something must land. For now we will block on this until priority changes. |
Maybe we should consider switching to Packit for RPM test builds |
Looks like the RPM builds when switching to Ubuntu 22.04 runners: coreos/coreos-installer#1590 We can probably use that as a workaround while we work on switching the RPM test build to Packit. |
Would need to be switched in https://github.com/coreos/repo-templates/blob/main/rust/rpm-test.yml |
Builds are failing on Ubuntu 24.04 due to a bug in mock/usermode [1]. Revert back to Ubuntu 22.04 for now, likely until we move to Packit for building test RPMs. [1] coreos/afterburn#1156 See: coreos/coreos-installer#1589 See: coreos/afterburn#1156
This could be seccomp-related. One test to do is to go back to latest Ubuntu, but add |
Trying that in coreos/coreos-installer#1592 |
Bug
Environment
Github action
Expected Behavior
RPM build completes successfully after pushing valid changes.
Actual Behavior
Currently when trying to land a PR into Afterburn you see that your RPM build will fail.
RPM build warnings: mv *.src.rpm $outdir munmap_chunk(): invalid pointer /__w/_temp/f0dea351-4870-4fd7-bae0-07d688f3703d.sh: line 3: 362 Aborted (core dumped) mock --rebuild --enablerepo=updates-testing rpms/*.src.rpm
Note: I have been unable to reproduce this locally. this seems to be limited to the github action environment.
Reproduction Steps
Other Information
The text was updated successfully, but these errors were encountered: