On 3/8/21 7:14 PM, Do Not Reply wrote: > Detected one or more Cirrus-CI cron-triggered jobs have failed recently: > > Cron build 'v2.2' Failed: https://cirrus-ci.com/build/5420095921979392 > Cron build 'v3.0' Failed: https://cirrus-ci.com/build/4721329234509824 The v2.2 branch had most of it's testing disabled yesterday...after that cirrus-cron job ran. Ignore it. The v3.0 branch APIv2 flake is getting very annoying, failing every day with 'bind: address already in use'. Jhon, Was there a fix or some change made on master (where it doesn't flake) that could be backported to the v3.0 branch? -- Chris Evich (he/him), RHCA III Senior Quality Assurance Engineer If it ain't broke, yain't tryin' hard 'nough.

Jhon, You can probably ignore this. We've since disabled most testing on the v3.0 branch. Unless you're chasing something and need logs, in that case I may be able to point you at some - Just let me know what you're after. -- Chris Evich (he/him), RHCA III Senior Quality Assurance Engineer If it ain't broke, yain't tryin' hard 'nough. On 4/8/21 12:27 PM, Jhon Honce wrote: > Do you have logs with the flake I can troll? Must be some timing/race > condition. I've never seen it locally. > > On Tue, Mar 9, 2021 at 9:20 AM Chris Evich <cevich(a)redhat.com > <mailto:cevich@redhat.com>> wrote: > > Jhon, > > Was there a fix or some change made on master (where it doesn't flake) > that could be backported to the v3.0 branch?