Skip to content

Correctly handle riscv64 chroots#1899

Merged
kwk merged 1 commit intofedora-llvm-team:mainfrom
kwk:add-riscv64-and-x86_64_v2-as-chroot-archs
Jan 29, 2026
Merged

Correctly handle riscv64 chroots#1899
kwk merged 1 commit intofedora-llvm-team:mainfrom
kwk:add-riscv64-and-x86_64_v2-as-chroot-archs

Conversation

@kwk
Copy link
Copy Markdown
Collaborator

@kwk kwk commented Jan 28, 2026

  • Add missing arch to allowed_archs_as_regex_str
    The chroot_pattern in config.py couldn't be filtered to remove
    riscv64 chroots before this patch because
    it thought that is was an unknown architecture.

  • While riscv64 indeed IS a known architecutre now,
    we still don't want to build for it.
    When sanitizing the chroots to be used in the config
    we remove all riscv64 chroots.

@kwk kwk requested a review from tbaederr January 28, 2026 09:11
@kwk kwk self-assigned this Jan 28, 2026
@kwk kwk added enhancement New feature or request github/workflow labels Jan 28, 2026

>>> allowed_archs_as_regex_str()
'(aarch64|i386|ppc64le|s390x|x86_64)'
'(aarch64|i386|ppc64le|s390x|x86_64|riscv64|x86_64_v2)'
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does allowed_archs need to be updated as well?

Also, what effect is this going to have? Are we doing to start building for these chroots as well?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was lazy and only ran the tests on github. Sorry, you're right. I need to update that as well. Let me check if the sanitization filters them out.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nikic can you please recheck? I've modified the chroot sanitization to exclude all riscv64 chroots for now. The x86_64_v2 wasn't an error so far but I simply saw the architecture pop up. Should we run into problems with it we need to handle it as well I've removed it from this PR.

@kwk kwk force-pushed the add-riscv64-and-x86_64_v2-as-chroot-archs branch from b3badc7 to c3c1dca Compare January 28, 2026 10:01
* Add missing arch to allowed_archs_as_regex_str
  The `chroot_pattern` in `config.py` couldn't be filtered to remove
  `riscv64` chroots before this patch because
  it thought that is was an unknown architecture.

* While riscv64 indeed IS a known architecutre now,
  we still don't want to build for it.
  When sanitizing the chroots to be used in the config
  we remove all riscv64 chroots.
@kwk kwk force-pushed the add-riscv64-and-x86_64_v2-as-chroot-archs branch from c3c1dca to 30562f7 Compare January 28, 2026 10:02
@kwk kwk changed the title Add missing archs to allowed_archs_as_regex_str Correctly handle riscv64 chroots Jan 28, 2026
Copy link
Copy Markdown
Collaborator

@nikic nikic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kwk kwk merged commit e955051 into fedora-llvm-team:main Jan 29, 2026
6 checks passed
@kwk kwk deleted the add-riscv64-and-x86_64_v2-as-chroot-archs branch January 29, 2026 14:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request github/workflow

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants