> We currently have no autopkgtest logs before snapd hits -proposed
> because we got asked to disable our autopkgtest integration as it
> was using too many resources from the autopkgtest infrastructure.
Since upstream's CI no longer includes checking against Ubuntu as a baseline, this increases the risk that the SRU will stall due to failed autopkgtests in -proposed. However, this is not a blocker for accepting the SRU, it is only a blocker for it being released, so this is an assumed risk.
> We currently have no autopkgtest logs before snapd hits -proposed
> because we got asked to disable our autopkgtest integration as it
> was using too many resources from the autopkgtest infrastructure.
Since upstream's CI no longer includes checking against Ubuntu as a baseline, this increases the risk that the SRU will stall due to failed autopkgtests in -proposed. However, this is not a blocker for accepting the SRU, it is only a blocker for it being released, so this is an assumed risk.