Re: Preliminary launch of ci.rocm.debian.net
On 2023-08-02 00:23, Christian Kastner wrote:
> (1) There's no automatic scheduling yet. Jobs can only be submitted
> manually. This will be addressed very soon.
I have the first draft of this up and running on ci.rocm.debian.net, so
from now on, your uploads of ROCm packages will trigger an autopkgtest!
It's a rough prototype of a utility that tracks the Archive, and submits
jobs whenever a newer version of a package is discovered in a
distribution -- so by uploads, or through migrations.
It doesn't track dependency or reverse dependency changes yet; that
problem is a bit more subtle. But the machinery is there.
[Side note: the Archive gets updated every 6hrs, I think? So it might
take time for your uploads to get noticed.]
> (2) There seems to be a RabbitMQ issue in bookworm; both readers and
> writers seem to block occasionally.
Well, one issue was the consumer_timeout default of 30mins. ACKs from
tests running longer than that were ignored, and that eventually stalled
the queue.
Those are no longer a problem.
But for some reason, workers still go AWOL after a certain period of
idling/inactivity.
> (3) I've underestimated the resources requirements. Last Sunday,
> I naively scheduled jobs for unstable+testing for all packages
> with autopkgtests. Well, some tests run for hours, they even
> timed out (3h). I need to increase the limit.
This wasn't too bad after all. We do have a few long-running packages
(rocfft now [1], rocblas soon), but most packages need less than 10 minutes.
> (4) I've not looked into getting tests done in experimental, which
> debci treats as unstable + an extra APT source.
This is still on my TODO list, but mostly from the scheduling side.
experimental isn't a full distribution like unstable or testing, and
packages can disappear, so tracking the Archive is not as
straightforward as the other cases.
Best,
Christian
[1] https://salsa.debian.org/rocm-team/debci
[2] https://ci.rocm.debian.net/packages/r/rocfft/unstable/amd64+gfx1030/
Reply to: