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
alanc has quit [Remote host closed the connection]
alanc has joined #freedesktop
<eric_engestrom>
daniels: not sure which MR robclark was looking at, but on an MR of mine, `radeonsi-raven-piglit-quick_shader:amd64` was queued for 83 minutes before it started running: https://gitlab.freedesktop.org/mesa/mesa/-/jobs/38942503
<eric_engestrom>
(a couple of hours ago)
vbenes has joined #freedesktop
<daniels>
eric_engestrom: ugh, I have no idea what happened there - not sure if it was network issues or something else as I can't see an obvious cause
<eric_engestrom>
daniels: could be the issue where the runner doesn't pick up the job until another job arrives?
<daniels>
eric_engestrom: I don't think so, because we do have the scheduled pipeline which actively pushes jobs in all the time and that was queued for ages too
<daniels>
also the total pipeline completion time can be a bit of a red herring because of the performance jobs which get triggered after the fact ...
<eric_engestrom>
so, I was thinking "wouldn't it be nice if we could see the pipeline jobs as a gantt chart to easily see which jobs are taking too long or starting too late?" so I looked it up... and someone did that: https://gitlab.com/gitlab-org/gitlab/-/issues/236018#note_398910317
<eric_engestrom>
I only had to change the host, project name and pipeline id, and it works
<bentiss>
eric_engestrom: nice! doo you think it would make sense to add that processing at the end of any pipelines, in a job that would run all the time, even if the pipeline failed?
<daniels>
eric_engestrom: oooh
<eric_engestrom>
bentiss: exporting it as a json artifact, or embedding catapult to generate the html and artifact that?
<eric_engestrom>
but yes, good idea
<bentiss>
eric_engestrom: whatever is easier ;) but having a one click access to that information for a pipeline like mesa makes sense IMO :)
<eric_engestrom>
is there an image I can use that is guaranteed to have parallel, curl, and jq? or should I use alpine and install those?
<eric_engestrom>
(parallel is optional, I can rewrite it as a loop)
<eric_engestrom>
if I should use alpine, how do I make it go through harbour to avoid hitting dockerhub directly?
<eric_engestrom>
`$CI_REGISTRY_IMAGE/alpine` I guess?
<daniels>
I'd just add it to the ci-fairy image or something
<daniels>
that way it's a known quantity
<daniels>
(with alpine you'd still have to pull the apks every time)
<bentiss>
we could even have a backup for all official groups (mesa/wayland/libinput/gstreamer/etc...) so it's easier to dig through them if we ever need
<daniels>
bentiss: hmm, we shouldn't need to back up pages though since they can be reproduced from pipelines
<bentiss>
pages take only 7GB, so peanuts
karolherbst has joined #freedesktop
karolherbst_ has quit [Ping timeout: 480 seconds]
ximion has joined #freedesktop
abrotman_ is now known as abrotman
yossarian has joined #freedesktop
miracolix has quit [Ping timeout: 480 seconds]
gchini has quit [Quit: Leaving]
ximion has quit [Quit: Detached from the Matrix]
AbleBacon has joined #freedesktop
nehsou^ has quit [Read error: Connection reset by peer]
nehsou^ has joined #freedesktop
gchini has joined #freedesktop
Guest9266 is now known as ocrete
mvlad has quit [Ping timeout: 480 seconds]
Haaninjo has joined #freedesktop
<Ford_Prefect>
I'm getting ssh timeouts while trying to git push -- anyone else seeing this too?
<Ford_Prefect>
And it's fine now O_O
danvet has quit [Ping timeout: 480 seconds]
yossarian has quit []
Guest9309 has joined #freedesktop
vkareh has quit [Quit: WeeChat 3.6]
miracolix has joined #freedesktop
Guest9309 has quit []
bnieuwenhuizen_ has joined #freedesktop
bnieuwenhuizen has quit [Ping timeout: 480 seconds]