On Tue, Jul 12, 2022 at 4:33 AM Daniel P. Berrangé <berra...@redhat.com> wrote:
> On Tue, Jul 12, 2022 at 03:56:54PM +0530, Richard Henderson wrote: > > On 7/12/22 15:43, Daniel P. Berrangé wrote: > > > On Tue, Jul 12, 2022 at 03:28:58PM +0530, Richard Henderson wrote: > > > > This is a collection of fixes required to get CI back to green. > > > > Given that 2 of 3 apply to cirrus, I had to push them to staging to > > > > even try them. Since it worked, I've now pushed them to master. > > > > > > FWIW, it is possible to test Cirrus CI fixes in your own personal > > > fork too, but it needs a little extra setup first, detailed in > > > > > > .gitlab-ci.d/cirrus/README.rst > > > > How many of the 'github' strings therein should really be 'gitlab'? > > None actually, this is all part of the (gross) hack. Cirrus CI officially > only integrates with GitHub, so we need a dummy GitHub repo there. Once > the job starts though, it actually pulls the real code from gitlab. > Yea, fun times that hack... :( Warner
