Re: Debian ROCm CI troubles
On 2025-08-11 23:17, Christian Kastner wrote:
> The other problem is not with debci but debci-scheduler. There are at least two distinct issues. One is that python-apt complains about a missing deb-src entry for stable-backports when it clearly exists. Another is the state of experimental. I cannot look into these right now, this will happen sometime during the week. Work is busy.
The 8.1 upload of debci-scheduler fixed the second issue. The first
issue went away by itself; must have been some transient state of
experimental.
I've cleared all open jobs and all queues and let the scheduler run again.
>> If there are folks on this list that want to lend a hand but aren't sure how to help out with ROCm, then I would suggest that contributing to the DebCI would be greatly beneficial.
Cory, the more I think about it, the more clear it is that the most
reasonable solution would be for you yourself to step in. You assembled
and currently host most of ci.rocm.debian.net's workers. You were the
first "beta" user of features I developed. Your strong connection to the
CI is why I gave you root access two years ago.
And the AMD folks currently taking over the ROCm packaging tasks
probably benefit the most from this CI, so dedicating work time for this
should be an easy sell internally.
This shouldn't be mistaken as a burden -- this is an opportunity. Rather
than being operationally dependent on a resource with limited
availability, this will eventually give you resp. AMD full operational
control, and give you insight that you might be able to share with other
QA departments within AMD.
I've fixed this now, but as I said previously, I'm currently preoccupied
with other projects, and will be for the foreseeable future.
Best,
Christian
Reply to: