Re: ROCm 6.1: should we start uploading components to unstable?
Hi Cory,
On 2024-09-24 20:21, Cordell Bloor wrote:
> We have good coverage of ROCm functionality in the continuous
> integration system. If the test results indicate that these packages are
> working, I have no concerns about uploading to unstable. In my opinion,
> mixing and matching package versions is of no concern as long as we have
> the test coverage to prove it works.
Agreed.
> When uploading, I would start at the bottom of the dependency tree and
> move up. If nothing else, it slightly reduces the number of autopkgtests
> that will be scheduled for rdepends. That would be roct-thunk-interface
> first, rocr-runtime second and amdsmi third.
I just did another upload of roct-thunk-interface to experimental that
merely adds some barely-mentionable polishing.
I found really minor/pedantic nitpicks in my final review and I thought
I'd use the occasion to trigger one final round of tests.
I'm aiming for an upload to unstable tomorrow.
Best,
Christian
Reply to: