Friday, 2022-05-13

*** rlandy|bbl is now known as rlandy|out00:18
*** Guest0 is now known as prometheanfire00:29
*** dviroel|afk is now known as dviroel|out01:26
*** ysandeep|rover|out is now known as ysandeep|rover04:50
*** jpena|off is now known as jpena07:02
*** jpodivin_ is now known as jpodivin07:15
*** ysandeep|rover is now known as ysandeep|rover|lunch07:40
*** lajoskatona_ is now known as lajoskatona07:42
*** ysandeep|rover|lunch is now known as ysandeep|rover08:49
opendevreviewMerged openstack/ptgbot master: Update Bot to Show Room Descriptions  https://review.opendev.org/c/openstack/ptgbot/+/84157509:31
*** rlandy|out is now known as rlandy10:09
opendevreviewLajos Katona proposed openstack/openstack-zuul-jobs master: Remove legacy pike only jobs for networking projects  https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/84171410:29
*** dviroel|out is now known as dviroel11:00
*** dasm|off is now known as dasm14:01
*** ykarel_ is now known as ykarel15:05
*** dviroel is now known as dviroel|lunch15:12
*** ysandeep|rover is now known as ysandeep|out15:55
*** dviroel|lunch is now known as dviroel16:00
elodillesfungi: as usual, i'll run the eol'd branch removal script to clean up some old branches that were EOL'd lately16:11
elodillesclarkb: ^^^16:11
fungithanks for the heads up!16:14
fungithere's nothing going on which should interfere with that work, so feel free to proceed16:14
clarkbyup should be fine16:15
elodillesack, thanks!16:19
*** gibi is now known as gibi_pto16:39
*** jpena is now known as jpena|off16:59
mnaserhmm19:41
mnaseri've got a failure on this19:41
mnaser> ERROR: Could not find a version that satisfies the requirement os-brick===5.2.019:41
mnaserstable/yoga and stable/xena failures19:42
mnaserbut https://mirror.gra1.ovh.opendev.org/pypi/simple/os-brick/ exists?19:43
mnaser5.2.0 has been out for months already19:44
fungiwe saw a similar failure for pbr yesterday. likely pypi yet again serving us outdated backup copies of package indices19:48
melwitthas anyone seen a thing where a job consistently passes the check queue but then consistently fails the gate queue afterwards?20:13
melwittI can't think what kind of difference there would be20:13
clarkbmelwitt: we tell people to not change behavior based on the pipeline.20:59
clarkbit is theoretically possible for code to take different actions based on that.20:59
clarkbin infra land we have container building jobs and in check they simply build and test with them. In the gate they upload to docker hub too. We name the jobs completely differently to make that apparent though21:00
melwittthanks. maybe this is a really unlucky coincidence21:00
clarkbmnaser: fungi: I continue to think I'm the wrong person to engage pypi about this but I think it would be helpful if someone could engage them about the security concerns related to that behavior21:01
fungiagreed. i'm personally daunted by the mountain of evidence they're going to demand for proof that there's a problem, and the first thing they're going to insist on is that we reproduce it without any proxies, but it's so intermittent that direct reproduction on demand is very challenging21:06
clarkbya its the sort of problem where you just need to humor the person reporting it and add more monitoring21:17
clarkbI mean in thoery they should be able to check logs on the backup backend and confirm things are hitting it21:17
clarkbbut it is definitely unfair to pin that on us21:17
*** dasm is now known as dasm|off21:18
*** dviroel is now known as dviroel|out21:57

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!