Bump uraimo/run-on-arch-action from 2 to 3#715
Conversation
|
Yippee! Those really annoying segfaults appear to be fixed in this update to However, it's a major version update and I'll do a little manual testing first before merging. @zherczeg You are using Whatever it is though, some security update went out which enabled more aggressive ASLR, so code was being mapped to a randomised layout inside a larger address space than before. That in turn was incompatible with some assumptions in older versions of Qemu (before v7). The Qemu interpreter was JITing the s390x/ppc64le code into x64 but with invalid assumptions about the range of allowed pointers. That is why the GCC compiler (and in fact all processes run by Qemu inside the docker image) would segfault randomly. You could get lucky and the build might pass, so clearly the segfault probability is very low, since a lot of processes get spawned by a code build! This update to Qemu v9 ought to fix things... or at least, I can hope. |
Bumps [uraimo/run-on-arch-action](https://github.com/uraimo/run-on-arch-action) from 2 to 3. - [Release notes](https://github.com/uraimo/run-on-arch-action/releases) - [Commits](uraimo/run-on-arch-action@ac33288...1c358dc) --- updated-dependencies: - dependency-name: uraimo/run-on-arch-action dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
12f5378 to
1e7f6ec
Compare
Bumps uraimo/run-on-arch-action from 2 to 3.
Release notes
Sourced from uraimo/run-on-arch-action's releases.
... (truncated)
Commits
1c358dcTagged v3 from refs/tags/v3.0.0 [skip ci]4141da8Update README.md2b92569Update README.md93517bcFixes #14207bea26Cleanup testing changes5a70806Update issue #160 testba35852Update branch for issue 160 test51a6e8bChange qemu-static imagec908d6bDump current QEMU version used by qemu-user-static1470574Revert "Downgrade QEMU to 7.0.0-7", still Segmentation fault (core dumped)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)