Skip to content

ppc64le job with ubuntu-rolling started failing when running run-on-arch-install.sh #160

Closed

Description

@pllim

Hello and thank you for this action. I started seeing failure in our downstream ppc64le using this action and wondering if the error means anything to you because I cannot make sense of it. I am not an expert in this architecture. Hope you could help or point us to someone/somewhere. 🙏

Detailed log:

Activity

  1. martin-g commented on Jan 24, 2025

    @martin-g
    Contributor
  2. added a commit that references this issue on Jan 24, 2025
  3. pllim commented on Jan 24, 2025

    @pllim
    ContributorAuthor

    Thank you for your reply. I tried it in astropy/astropy#17666 but I get Segmentation fault (core dumped). 😬

  4. martin-g commented on Jan 28, 2025

    @martin-g
    Contributor

    No idea ...
    You may try this workaround - pyenv/pyenv#2239 (comment)

  5. added a commit that references this issue on Jan 28, 2025
  6. roshkhatri commented on Feb 13, 2025

    @roshkhatri

    We are seeing similar issue with building our C project building on aarch64/ubuntu 20.04 and aarch64/ubuntu 22.04, which was working fine around Jan 7th.

    We are facing the following error:

    make[2]: *** [<builtin>: ldblib.o] Segmentation fault (core dumped)
      make[2]: Leaving directory '/home/runner/work/valkey/valkey/deps/lua/src'
      make[1]: *** [Makefile:102: lua] Error 2
      make[1]: Leaving directory '/home/runner/work/valkey/valkey/deps'
      make: [Makefile:415: persist-settings] Error 2 (ignored)
          CC adlist.o
      In file included from adlist.c:34:
      zmalloc.h:50:10: fatal error: jemalloc/jemalloc.h: No such file or directory
         50 | #include <jemalloc/jemalloc.h>
            |          ^~~~~~~~~~~~~~~~~~~~~
      compilation terminated.
      make: *** [Makefile:467: adlist.o] Error 1
      make: Leaving directory '/home/runner/work/valkey/valkey/src'
      Error: The process '/home/runner/work/_actions/uraimo/run-on-arch-action/v2/src/run-on-arch.sh' failed with exit code 2
    

    more logs can be found here: https://github.com/valkey-io/valkey/actions/runs/13295059183/job/37124939339

    I have no idea why this would fail without any changes in code.

    Please let me know if know any workaround that would resolve this.

    Also, Thank you so much for this action, it has been very helpful.

    EDIT: We just moved to github hosted arm runner which works for the project. Thanks!

  7. anr2me commented on Feb 27, 2025

    @anr2me

    May be an issue with QEMU, similar to tonistiigi/binfmt#215

  8. pllim commented on Feb 27, 2025

    @pllim
    Author
  9. reopened this on Feb 27, 2025
  10. uraimo commented on Feb 28, 2025

    @uraimo
    Owner

    Hi all, following the discussion ongoing at tonistiigi/binfmt#215 it looks like that updating QEMU to 9.2.2 should fix the issue, I'm testing it on a branch and keeping track of the results that everyone is reporting.
    As for the issue itself, I think it can be described as "sporadic segmentation faults", since even with a specific test case from CRoaring I cannot reliably replicate the issue every time.

    If this works I will release a new major release, 3.0.0, since this is a pretty big update from the QEMU 7.2.0 that is in use right now through multiarch/qemu-user-static (that has not been updated for 2 years) and I don't want to introduce regressions for people using older OS releases and that could be tracking 2.x.

    I'm also doing some tests with 7.0.0-7 since it's available and there are reports of 7.0.0 non being affected by this issue.

  11. kleisauke commented on Feb 28, 2025

    @kleisauke

    I can confirm that using QEMU 9.2.2 from tonistiigi/binfmt:latest fixes this. Tested this by pinning this GitHub action to 51a6e8b, see commit: kleisauke/sharp@ffd30a6.

  12. added a commit that references this issue on Feb 28, 2025
  13. uraimo commented on Feb 28, 2025

    @uraimo
    Owner

    3.0.0 has been published.

  14. pllim commented on Feb 28, 2025

    @pllim
    ContributorAuthor

    Thank you! Looks promising over at astropy/astropy#17827

  15. anr2me commented on Mar 12, 2025

    @anr2me

    It seems the segfault issue is coming back again

     #9 272.9 Setting up automake (1:1.16.3-2) ...
      #9 272.9 update-alternatives: using /usr/bin/automake-1.16 to provide /usr/bin/automake (automake) in auto mode
      #9 272.9 Setting up libltdl-dev:arm64 (2.4.6-15) ...
      #9 272.9 Processing triggers for libc-bin (2.31-13+deb11u11) ...
      #9 273.0 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
      #9 273.5 Segmentation fault (core dumped)
      #9 273.5 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
      #9 273.9 Segmentation fault (core dumped)
      #9 273.9 dpkg: error processing package libc-bin (--configure):
      #9 273.9  installed libc-bin package post-installation script subprocess returned error exit status 139
      #9 274.0 Errors were encountered while processing:
      #9 274.0  libc-bin
      #9 274.1 E: Sub-process /usr/bin/dpkg returned an error code (1)
      #9 ERROR: process "/bin/sh -c chmod +x /root/run-on-arch-install.sh && /root/run-on-arch-install.sh" did not complete successfully: exit code: 100
      ------
       > [3/3] RUN chmod +x /root/run-on-arch-install.sh && /root/run-on-arch-install.sh:
      272.8 Setting up libcurl4-openssl-dev:arm64 (7.74.0-1.3+deb11u14) ...
      272.8 Setting up libsigsegv2:arm64 (2.13-1) ...
      using /usr/bin/automake-1.16 to provide /usr/bin/automake (automake) in auto mode
      272.9 Setting up libltdl-dev:arm64 (2.4.6-15) ...
      272.9 Processing triggers for libc-bin (2.31-13+deb11u11) ...
      273.0 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
      273.5 Segmentation fault (core dumped)
      273.5 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
      273.9 Segmentation fault (core dumped)
      
      ------
      Dockerfile.none.none:3
      --------------------
         1 |     FROM --platform=linux/arm64 arm64v8/debian:bullseye
         2 |     COPY ./run-on-arch-install.sh /root/run-on-arch-install.sh
         3 | >>> RUN chmod +x /root/run-on-arch-install.sh && /root/run-on-arch-install.sh
      --------------------
      ERROR: failed to solve: process "/bin/sh -c chmod +x /root/run-on-arch-install.sh && /root/run-on-arch-install.sh" did not complete successfully: exit code: 100
      Error: The process '/home/runner/work/_actions/uraimo/run-on-arch-action/v3/src/run-on-arch.sh' failed with exit code 1
    

    Some one post about it yesterday at tonistiigi/binfmt#215 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions