ChanServ changed the topic of #freedesktop to: https://www.freedesktop.org infrastructure and online services || for questions about freedesktop.org projects, please see each project's contact || for discussions about specifications, please use https://gitlab.freedesktop.org/xdg or xdg@lists.freedesktop.org
Satan has quit [Remote host closed the connection]
alpernebbi has quit [Ping timeout: 480 seconds]
alpernebbi has joined #freedesktop
ximion has quit []
progandy has joined #freedesktop
jarthur has quit [Ping timeout: 480 seconds]
i-garrison has quit [Ping timeout: 480 seconds]
i-garrison has joined #freedesktop
i-garrison has quit []
i-garrison has joined #freedesktop
bittin_ has quit [Remote host closed the connection]
bittin has joined #freedesktop
pohly has joined #freedesktop
pohly has quit []
fahien has joined #freedesktop
progandy has quit [Ping timeout: 480 seconds]
progandy has joined #freedesktop
AbleBacon has quit [Read error: Connection reset by peer]
fahien has quit []
progandy has quit [Ping timeout: 480 seconds]
progandy has joined #freedesktop
ximion has joined #freedesktop
bittin has quit [Read error: Connection reset by peer]
bittin has joined #freedesktop
<jenatali>
alatiera: any suggestions for what we can try to debug/resolve it?
<jenatali>
Looks like the Mesa CI using that runner got disabled this morning due to the flakes and I'd really prefer not to leave it disabled
mceier has joined #freedesktop
Major_Biscuit has joined #freedesktop
Major_Biscuit has quit [Read error: Connection reset by peer]
Major_Biscuit has joined #freedesktop
Major_Biscuit has quit [Read error: Connection reset by peer]
mceier has quit [Ping timeout: 480 seconds]
___nick___ has joined #freedesktop
mceier has joined #freedesktop
alanc has quit [Remote host closed the connection]
alanc has joined #freedesktop
scrumplex_ has joined #freedesktop
scrumplex has quit [Ping timeout: 480 seconds]
danvet has joined #freedesktop
progandy has quit [Ping timeout: 480 seconds]
<__tim>
how come it's so bad for mesa that it needs to be disabled but works (mostly) fine for gstreamer?
thaller has joined #freedesktop
* __tim
says and gets served with two win dns failures for freetype jobs
thaller has quit [Read error: Connection reset by peer]
thaller has joined #freedesktop
progandy has joined #freedesktop
thaller is now known as Guest7259
Guest7259 has quit [Read error: Connection reset by peer]
thaller has joined #freedesktop
jarthur has joined #freedesktop
i-garrison has quit []
i-garrison has joined #freedesktop
thaller has quit [Read error: Connection reset by peer]
___nick___ has quit [Ping timeout: 480 seconds]
jstein has joined #freedesktop
Major_Biscuit has joined #freedesktop
Major_Biscuit has quit [Ping timeout: 480 seconds]
danvet has quit [Ping timeout: 480 seconds]
<daniels>
__tim: our end-to-end turnaround is approx 20min, so if Windows falls over several times in a row then it blows that out
<__tim>
i wonder if it would make sense to check if there's a correlation between artefact uploads and dns issues
<__tim>
uploads from other jobs on the runner ofc
AbleBacon has joined #freedesktop
<__tim>
(still not clear to me though why mesa jobs would be more prone to such failure than gstreamer jobs; I do understand that failures are annoying and re-runs prolong overall turnaround ofc)
<__tim>
or was that just an explanation of why they've been disabled?
<alatiera>
its not related to uploads or use
<alatiera>
it seems random for the most part
<alatiera>
I will try to mess around with the daemon config on Monday, see if it changes anything