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
tr4gic_3rr0r has joined #freedesktop
karolherbst has quit [Ping timeout: 480 seconds]
jturney has quit [Ping timeout: 480 seconds]
tr4gic_3rr0r has quit [Remote host closed the connection]
tr4gic_3rr0r has joined #freedesktop
karolherbst has joined #freedesktop
scrumplex has joined #freedesktop
scrumplex_ has quit [Ping timeout: 480 seconds]
alanc has quit [Remote host closed the connection]
tr4gic_3rr0r has quit [Ping timeout: 480 seconds]
alanc has joined #freedesktop
jturney has joined #freedesktop
JanC is now known as Guest14794
JanC has joined #freedesktop
phire_ has joined #freedesktop
phire is now known as Guest14795
phire_ is now known as phire
JanC is now known as Guest14796
JanC has joined #freedesktop
Guest14794 has quit [Ping timeout: 480 seconds]
Guest14795 has quit [Ping timeout: 480 seconds]
Guest14796 has quit [Ping timeout: 480 seconds]
JanC is now known as Guest14799
JanC has joined #freedesktop
Guest14799 has quit [Ping timeout: 480 seconds]
JanC is now known as Guest14800
JanC has joined #freedesktop
Guest14800 has quit [Ping timeout: 480 seconds]
lack has quit [Quit: Signing off]
lack has joined #freedesktop
JanC is now known as Guest14807
JanC has joined #freedesktop
Guest14807 has quit [Ping timeout: 480 seconds]
swatish2 has joined #freedesktop
JanC is now known as Guest14808
JanC has joined #freedesktop
Guest14808 has quit [Ping timeout: 480 seconds]
swatish2 has quit [Ping timeout: 480 seconds]
alarumbe has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
AbleBacon has joined #freedesktop
swatish2 has joined #freedesktop
sima has joined #freedesktop
JanC is now known as Guest14812
JanC has joined #freedesktop
JanC is now known as Guest14813
JanC has joined #freedesktop
Guest14812 has quit [Ping timeout: 480 seconds]
Guest14813 has quit [Ping timeout: 480 seconds]
swatish2 has quit [Ping timeout: 480 seconds]
swatish2 has joined #freedesktop
ximion has quit [Remote host closed the connection]
swatish21 has joined #freedesktop
swatish2 has quit [Ping timeout: 480 seconds]
jsa1 has joined #freedesktop
Caterpillar has quit [Quit: Konversation terminated!]
Caterpillar has joined #freedesktop
mattst88_ has joined #freedesktop
mattst88 has quit [Read error: Connection reset by peer]
Caterpillar has quit [Quit: Konversation terminated!]
Caterpillar has joined #freedesktop
gnuiyl has quit [Quit: Leaving]
gnuiyl has joined #freedesktop
JanC is now known as Guest14818
JanC has joined #freedesktop
Guest14818 has quit [Ping timeout: 480 seconds]
jsa1 has quit [Ping timeout: 480 seconds]
fantom has quit [Ping timeout: 480 seconds]
fantom has joined #freedesktop
<MrCooper> according to comments on https://lwn.net/Articles/1017315/, snapshot.debian.org should be robust for usage in CI now
jsa1 has joined #freedesktop
<sergi> bentiss: Hi there, I realized many scheduled pipelines aren't triggered when the cron plan. In the "next run" field, the "mesa nightly" say "3 hours ago": https://gitlab.freedesktop.org/mesa/mesa/-/pipeline_schedules
<sergi> It should have been triggered 3 hours ago, but it wasn't. The same is happening with, at least, https://gitlab.freedesktop.org/gfx-ci/mesa-performance-tracking/-/pipeline_schedules and https://gitlab.freedesktop.org/gfx-ci/ci-uprev/-/pipeline_schedules. Perhaps there is some service that needs a kick.
<bentiss> sergi: please try a manual run of the schedule pipeline. Often when they do not run is because the pipeline rules create an invalid config (missing job most of the time), but this silently fails
i-garrison has quit []
fantom has quit [Ping timeout: 480 seconds]
fantom has joined #freedesktop
<sergi> bentiss: I did that yesterday. I saw the "mesa nightly" running, but not the others, and thought there may be something particular with them. So, I triggered them manually, thinking that perhaps it was a transient situation just for them. But this morning, all those scheduled pipelines show this "ago".
AbleBacon has quit [Read error: Connection reset by peer]
i-garrison has joined #freedesktop
<sergi> Probably someone already triggered the "mesa nightly" yesterday. Yesterday's manual trigger on mesa-perfirmance-tracking and ci-uprev work as expected.
JanC is now known as Guest14823
JanC has joined #freedesktop
Guest14823 has quit [Ping timeout: 480 seconds]
JanC is now known as Guest14824
JanC has joined #freedesktop
Guest14824 has quit [Ping timeout: 480 seconds]
mripard has joined #freedesktop
swatish21 has quit [Ping timeout: 480 seconds]
swatish2 has joined #freedesktop
andy-turner has joined #freedesktop
<mupuf> I did trigger one manually too
<mupuf> forgot when
mripard has quit [Quit: WeeChat 4.6.1]
haaninjo has joined #freedesktop
swatish2 has quit [Ping timeout: 480 seconds]
swatish2 has joined #freedesktop
haaninjo has quit [Quit: Ex-Chat]
swatish21 has joined #freedesktop
swatish2 has quit [Ping timeout: 480 seconds]
alarumbe has joined #freedesktop
guludo has joined #freedesktop
swatish21 has quit [Ping timeout: 480 seconds]
swatish2 has joined #freedesktop
<pq> generic CI being hammered? just wondering the 15 minute queueing time and counting.
<mupuf> pq: or Marge being particularly active
<pq> alright
<pq> Marge pushed anything 40 minutes ago
tr4gic_3rr0r has joined #freedesktop
<pq> I got running now, oh yeah
<pq> hmm, random "no such image" runner failures
jsa1 has quit [Ping timeout: 480 seconds]
<pq> CI job 24 minutes queued and counting, aha, marge pushed some Mesa stuff 10 minutes ago.
<dj-death> any idea what's going on in this runner : https://gitlab.freedesktop.org/mesa/mesa/-/jobs/75481114 ?
jsa1 has joined #freedesktop
<pq> maybe LAVA did not pick up the job and it timed out?
<pq> does this also occupy job slots in runners while it's waiting for LAVA? Could that explain the long job queue times?
<pq> nah, different runners
mvlad has joined #freedesktop
<valentine> dj-death: No runners were available in the lab, and the job timed out. I restarted them and they got picked up now
<dj-death> valentine: thanks
<dj-death> valentine: some of them are going offline or just super busy?
<kxkamil2> do we have native arm/arm64 runners?
<valentine> dj-death: just busy for the most part - and I also had a job running
<valentine> kxkamil2: yes, there are native arm64 fd.o shared runners
<kxkamil2> any guide how to use them?
<valentine> You can use them just like the x86 runners, after adding tags: aarch64
<kxkamil2> nice, do we have other archs? armhf?
<kxkamil2> ppc64le?
jsa1 has quit [Ping timeout: 480 seconds]
<eric_engestrom> sergi: about the missing nightly pipelines, see https://gitlab.freedesktop.org/mesa/mesa/-/issues/13057, and I've been triggering them by hand every morning in the meantime
<eric_engestrom> kxkamil2: no, only x86_64 (default if you don't specify) and aarch64
<eric_engestrom> I've been trying to run the xorg/util `release.sh` to make a mesa release, but it fails with `Error: the path "/srv/mesa.freedesktop.org/www/archive" on the web server does not exist.`, but when I manually ssh into annarchy I see it:
<eric_engestrom> eric_engestrom@annarchy:~$ ls -ld /srv/mesa.freedesktop.org/www/archive/
<eric_engestrom> drwxrwxr-x+ 8 brianp mesa 36864 Apr 23 17:56 /srv/mesa.freedesktop.org/www/archive/
<eric_engestrom> not quite sure what to do here :(
<eric_engestrom> (re-running release.sh, on the off chance that it works next time)
<eric_engestrom> nope, same result :(
jsa1 has joined #freedesktop
<daniels> kxkamil2: the aarch64 runners can run armhf
JerryXiao has quit [Read error: Connection reset by peer]
JerryXia1 has joined #freedesktop
ximion has joined #freedesktop
tr4gic_3rr0r has quit [Ping timeout: 480 seconds]
jsa1 has quit [Ping timeout: 480 seconds]
jsa1 has joined #freedesktop
<jrayhawk> eric_engestrom: Can you run that as 'bash -x release.sh' and see what the failing ssh command is?
<jrayhawk> '$USER_NAME$hostname' looks suspiciously like a thing that will never work
<eric_engestrom> oh
<eric_engestrom> thanks jrayhawk that helped me
<eric_engestrom> I actually changed my .ssh/config a few days ago, and it no longer changes the default user for annarchy
<eric_engestrom> fixed, trying again
Traneptora has quit [Quit: Quit]
<eric_engestrom> yep, it works now :P
<eric_engestrom> thanks again jrayhawk 🙏
JanC is now known as Guest14848
JanC has joined #freedesktop
Guest14848 has quit [Ping timeout: 480 seconds]
swatish2 has quit [Ping timeout: 480 seconds]
jsa2 has joined #freedesktop
jsa1 has quit [Ping timeout: 480 seconds]
swatish2 has joined #freedesktop
AbleBacon has joined #freedesktop
tr4gic_3rr0r has joined #freedesktop
JanC is now known as Guest14851
JanC has joined #freedesktop
Guest14851 has quit [Ping timeout: 480 seconds]
mattst88_ has quit []
mattst88 has joined #freedesktop
JanC has quit [Ping timeout: 480 seconds]
JanC has joined #freedesktop
dakr has quit [Quit: ZNC 1.9.1 - https://znc.in]
dakr has joined #freedesktop
Xe has quit [Quit: WeeChat 4.6.2]
D-HUND is now known as debdog
Xe has joined #freedesktop
tr4gic_3rr0r has quit [Remote host closed the connection]
tr4gic_3rr0r has joined #freedesktop
JanC has quit [Ping timeout: 480 seconds]
haaninjo has joined #freedesktop
JanC has joined #freedesktop
Xe has quit [Quit: WeeChat 4.6.2]
Xe has joined #freedesktop
jsa2 has quit [Ping timeout: 480 seconds]
andy-turner has quit []
mvlad has quit [Remote host closed the connection]
jsa1 has joined #freedesktop
JanC is now known as Guest14862
JanC has joined #freedesktop
Guest14862 has quit [Ping timeout: 480 seconds]
guludo has quit [Quit: WeeChat 4.6.1]
haaninjo has quit [Quit: Ex-Chat]
jsa1 has quit [Ping timeout: 480 seconds]
D-HUND has joined #freedesktop
debdog has quit [Ping timeout: 480 seconds]
ybogdano has quit [Remote host closed the connection]