ALHP/ALHP.GO
7
43
Fork 8
Code Issues 28 Pull Requests Projects Releases Wiki Activity

python-aotriton and python-triton candidates for the blacklist? #284

New Issue
Open
opened 2026-01-11 09:19:29 +01:00 by BS86 · 4 comments
BS86 commented 2026-01-11 09:19:29 +01:00
Copy Link

python-aotriton and python-triton take several hours to build (per feature level that is).
In addition, python-aotriton is first compiled with LTO and then again without LTO meaning with the 5-6 hours each takes, that package alone takes up 32-36 hours on the build system.
python-triton also fails because of memory limit exceeded

python-aotriton and python-triton take several hours to build (per feature level that is). In addition, python-aotriton is first compiled with LTO and then again without LTO meaning with the 5-6 hours each takes, that package alone takes up 32-36 hours on the build system. python-triton also fails because of memory limit exceeded
anonfunc commented 2026-01-11 21:12:00 +01:00
Owner
Copy Link

If python-aotriton failed the LTO built, it will be permanently downgraded to non-lto builds. I'll have a look at python-triton, I think release frequency is probalby something to look at.

If `python-aotriton` failed the LTO built, it will be permanently downgraded to non-lto builds. I'll have a look at `python-triton`, I think release frequency is probalby something to look at.
BS86 commented 2026-01-11 21:23:03 +01:00
Author
Copy Link

If my memory does not fail me, python-aotriton already did that LTO --> non-LTO thing in december and also sometime earlier last year and now does it again.

If my memory does not fail me, `python-aotriton` already did that LTO --> non-LTO thing in december and also sometime earlier last year and now does it again.
anonfunc commented 2026-01-11 21:25:09 +01:00
Owner
Copy Link

We lost some of the LTO build failure data when the SSD failed mid last year, if it was not rebuild since then we could have another non-lto rebuild. Otherwise this would be a bug.

We lost some of the LTO build failure data when the SSD failed mid last year, if it was not rebuild since then we could have another non-lto rebuild. Otherwise this would be a bug.
BS86 commented 2026-01-12 10:52:51 +01:00
Author
Copy Link

it was built in November and December, I think that means there is a bug. For build frequency, have a look:
https://gitlab.archlinux.org/archlinux/packaging/packages/python-aotriton/-/commits/main
it looks like it has some releases on its own but needs to be rebuilt for python and ROCm releases.

it was built in November and December, I think that means there is a bug. For build frequency, have a look: https://gitlab.archlinux.org/archlinux/packaging/packages/python-aotriton/-/commits/main it looks like it has some releases on its own but needs to be rebuilt for python and ROCm releases.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
blocked upstream
bug
Something is not working
 build-failure
package build fails
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 informational
Provides information about something
 invalid
Something is wrong
 invalid/corrupt package
Package needs to be rebuild
 packaging issue
priority: high
High priority
 question
More information is needed
 support
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
anonfunc
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ALHP/ALHP.GO#284
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?