On Tue, May 19, 2020 at 5:23 PM Paul Moore <paul@xxxxxxxxxxxxxx> wrote: > > On Tue, May 19, 2020 at 6:16 PM William Roberts > <bill.c.roberts@xxxxxxxxx> wrote: > > On Tue, May 19, 2020 at 5:00 PM Paul Moore <paul@xxxxxxxxxxxxxx> wrote: > > > On Tue, May 19, 2020 at 11:15 AM <bill.c.roberts@xxxxxxxxx> wrote: > > ... > > > > > +dnf install -y \ > > > > > > Another speaking from experience comment: you probably want to add > > > "--allowerasing" and "--skip-broken" to the dnf command line. If you > > > can cope with the extra overhead, I would even suggest a "dnf clean > > > all -y" at the start. > > > > I don't see why we couldn't. > > > > Not really sure if it matters for those first two things, considering > > that were starting > > in the same state each time. Its not like we need to work on a system > > that's already > > been played with. > > FWIW, the VM I use for my automated kernel testing doesn't get played > with (other than to fix dnf/Rawhide problems) and I can tell you from > experience that Rawhide finds itself broken in new and exciting ways > :) > > You are using a stable Fedora release so it probably won't be too bad, > I'm just trying to share some of the lessons I've learned. > Sure, and I appreciate that. It actually doesn't add any time, to give you an idea the CI build time went from 14 to 11 mins. So that'll show you how much jitter there is. Ill send a V2 all fixed up shortly
