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
karolherbst has quit [Remote host closed the connection]
<eric_engestrom>
daniels: lava-collabora-acer-chromebox-cxi4-puff seems to have a lot of network issues, it often times out while uploading results to s3
<eric_engestrom>
it's a bit frustrating because the tests pass but the job fails and has to re-run, and roughly 2 out of 3 times it fails on that last step and has to be retried manually before marge sees the failure and/or times out
<daniels>
eric_engestrom: feel free to just zap the CML jobs until it's properly fixed then
<eric_engestrom>
!31624 for instance took almost 2h (luckily no-one else was in the queue so it got to run longer)
<eric_engestrom>
"zap" you mean disable with a `.` dot?
<daniels>
yeah
<eric_engestrom>
ack
<daniels>
I know people are looking at why a firmware upgrade made the puffs (sometimes horribly) worse for networking, but yeah, looks like it's not yet sorted
<eric_engestrom>
ack, good to know it's a known issue :)
<eric_engestrom>
I'm actually moving it to nightly instead of disabling it entirely
<daniels>
'k
<daniels>
thanks
karolherbst3 has quit []
karolherbst has joined #freedesktop
<__tim>
btw, it seems to me that something is off with the image caches with the new runner setup - I frequently see jobs pulling images that should really be cached already because it's like the #1 gstreamer main branch image in use
<__tim>
does that sound familiar/expected?
Haaninjo has joined #freedesktop
swatish2 has quit [Ping timeout: 480 seconds]
karenw has joined #freedesktop
karenw is now known as Guest418
swatish2 has joined #freedesktop
jturney has joined #freedesktop
abhimanyu1 has quit []
airlied_ has joined #freedesktop
airlied has quit [Ping timeout: 480 seconds]
airlied has joined #freedesktop
airlied_ has quit [Ping timeout: 480 seconds]
Caterpillar has joined #freedesktop
abhimanyu1 has joined #freedesktop
jsa1 has quit [Ping timeout: 480 seconds]
swatish2 has quit [Ping timeout: 480 seconds]
Guest418 has quit [Remote host closed the connection]
<karolherbst>
looks like alpine-build-testing didn't start in time either
<karolherbst>
(started past the timeout)
<Venemo>
well, let's waste another round of CI resources on this, then
<karolherbst>
looks like CI is a bit overloaded
<Venemo>
i reassigned to marge
<karolherbst>
yeah.... I think we might need to be more lax on the pipeline timeout, but still strict on job timeouts
<karolherbst>
or something
<karolherbst>
but there are also other issues, not sure if they got resolved, like the pipeline won't be aborted if marge moved on, but there have been an issue about it somewhere
<karolherbst>
looks like debian-testing-asan is quite heavy on the pipeline
<karolherbst>
huh... wait
<karolherbst>
I think there is a bug in the dependency tree...
<karolherbst>
alpine-build-testing seems to depend on debian-testing-asan mhhh...
<karolherbst>
looks like most of the later jobs depend on debian-testing-asan
<karolherbst>
but somebody else needs to judge if that's fine or not
<Venemo>
I guess the logic behind that decision is, don't even run the other jobs when the address sanitizer finds issues
<Venemo>
it makes sense
<karolherbst>
yeah.. maybe
<karolherbst>
but the main issue with your pipeline was, that a lot of jobs were stuck in queued state anyway
<karolherbst>
lost 20 minutes alone on that
mceier has quit [Ping timeout: 480 seconds]
jsa2 has quit [Ping timeout: 480 seconds]
<daniels>
yeah, if we can't start builds within 20 minutes, there's little chance of things completing on time
Haaninjo has quit [Quit: Ex-Chat]
sima has quit [Ping timeout: 480 seconds]
<mairacanal>
hey, I'm trying to push a patch to drm-misc-next-fixes (as we are currently in the merge window), but it seems that my access to the branch is being denied
<mairacanal>
i see "remote: GitLab: You are not allowed to push code to protected branches on this project" when I use dim push-branch, but when I use ssh -T git@gitlab.freedesktop.org, I get a "Welcome to GitLab, @mairacanal!", so I believe I'm properly logged
<mairacanal>
anyone has any idea about this?
vx has quit [Quit: G-Line: User has been permanently banned from this network.]