Skip to content

ci: arm segfault #749

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

Merged
merged 4 commits into from
Feb 20, 2025
Merged

ci: arm segfault #749

merged 4 commits into from
Feb 20, 2025

Conversation

jusito
Copy link
Member

@jusito jusito commented Feb 17, 2025

The CI failed for arm64 build with segfault during compilation. We guessed that its an issue with outdated clang-14 and an clang upgrade would maybe fix it, the recent changed allowed this. But it seems its a QEMU issue.

The reworked Dockerfile is still a benefit but probably will not fix it. For that I increased the ubuntu version to 24.04, including the dependency installation script. Is there a specific distro / version we want to support - beside 20.04/24.04?

Some deps seems not directly used so removed?

  • apt: graphviz
  • pip3: Pygments pyyaml wllvm python3-sphinx

@jusito jusito marked this pull request as ready for review February 17, 2025 12:23
@jusito jusito force-pushed the ci/fix-arm-build branch 2 times, most recently from 68dd8b6 to 761f007 Compare February 18, 2025 14:02
@jusito
Copy link
Member Author

jusito commented Feb 18, 2025

@fabianbs96

  1. Changed os to 20.04 for the runner and created follow up issue Own CI environment is required due to 20.04 brownout and outdated swift toolchain. #750
  2. Added PHASAR_TARGET_ARCH="" and removed PHASAR_BUILD_IR=$RUN_TESTS
  3. It seems the expected jobs need to be updated.

@fabianbs96 fabianbs96 merged commit 74baa2a into development Feb 20, 2025
5 checks passed
@fabianbs96 fabianbs96 deleted the ci/fix-arm-build branch February 20, 2025 17:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants