[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Uploading rocm 6.4.X in sid



Hi all,

Le 28/09/2025 à 08:44, Christian Kastner a écrit :
Hi all,

On 2025-09-28 00:22, Christian BAYLE wrote:
Should we start to upload all possible rocm 6.4.x into sid ?

Any objection if i start to do this for all package building in sid ?
I just did a quick random sample of some 6.4 packages and GPU
architectures, and all of their tests had failed.

In my opinion, these packages are unfit even for unstable. If they are
uploaded to unstable, then they need RC bugs so that they don't migrate
to testing. At least for the officially support architectures.

this was my point, not to put broken stuffs in unstable indeed, do you think apt.ai.debian.net would be a better place ? are the package queued to ci.rocm.debian.net ? as that would make it easier to read the result (but would make some other confusion about the fact there are not in real debian unstable)

For newcomers looking to contribute, this would be an easy way to get
started [1].

I must admit I was a bit confused as i only see report for 5.7.x and was wondering if it's worth to fix instead of working on 6.4.x

I see for example that rocprim was queued from experimental src
https://ci.rocm.debian.net/packages/r/rocprim/
The queue is a bit misleading. It's long because it seems to be stuck
again for and gfx1011, gfx1012.
Yes :-(

Is the idea to wait that most test are green before uploading, but it
seems that test are not run for package in experimental, or to push in
unstable ?
The tests are run, but experimental is an "add-on" distribution on top
of unstable, so you need to click on the unstable results to see the
experimental ones in the test hisotry, like here for unstable and
gfx1100 [2]. (Incidentally, rocprim 6.4 seems to pass on many
architectures, in contrast to the other 6.4 packages).
Ok, I see ... now

Regards

Christian



Reply to: