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
ybogdano has quit [Ping timeout: 480 seconds]
Haaninjo has quit [Quit: Ex-Chat]
jrayhawk has quit [Remote host closed the connection]
jrayhawk has joined #freedesktop
vkareh has joined #freedesktop
genpaku has quit [Remote host closed the connection]
miracolix has quit [Remote host closed the connection]
alanc has quit [Remote host closed the connection]
alanc has joined #freedesktop
vbenes has quit [Remote host closed the connection]
alatiera has quit [Ping timeout: 480 seconds]
vbenes has joined #freedesktop
<MrCooper>
bentiss daniels: 'podman image pull registry.freedesktop.org/psykose1/demos/debian/x86_build:2023-02-17-clang' fails here as well; I suspect it's because 'skopeo copy' hit a 404 in https://gitlab.freedesktop.org/psykose1/demos/-/jobs/38560020
<bentiss>
MrCooper: the cluster is a little bit flacky since yesterday. I guess it's time for a reboot of the nodes
<svuorela>
bentiss: I got a fix merged to poppler yesterday to hopefully respect the parallel setting.
<bentiss>
svuorela: yes I saw it, thanks!
<bentiss>
svuorela: just to be clear, the flackiness of the cluster is not poppler related, poppler had an impact on the runners for the pipelines, we are talking about the gitlab instance
<svuorela>
yeah.
<daniels>
MrCooper: yeah, the repo isn’t public
<svuorela>
(And I also tihnk I got the poppler people to accept me as a "guest" in the project, so I should be able to do CI until the bad people becomes sufficiently clever, right?)
<daniels>
MrCooper: yeah, because you’re authenticated - the project is not set to public so anonymous pulls will fail
<MrCooper>
then I couldn't see that page, could I?
<daniels>
are you logged in?
<MrCooper>
yes
<daniels>
podman image pull would work if it was logged in, too
<daniels>
that project has a visibility setting which specifically only allows it to be seen by logged-in users
<daniels>
if it was set to public like everything else, the error would disappear
<bentiss>
MrCooper: in other words: gitlab has 3 project visibility levels "public", "internal", "private", anything that is not "public" will fail
<bentiss>
for "private", you need to be granted access to the repository, but for "internal" you need to be authenticated (it's "internal" to the gitlab instance)
<bentiss>
rebooting the cluster, so expect some 500 errors
<MrCooper>
I did create an access token for podman though
<MrCooper>
not sure how I can check if that's still active though
<bentiss>
MrCooper: the problem is that the runner converts regsitry.fd.o into harbor.fd.o/cache, and is *not* authenticated, so if you run any job on our runners, and the project is internal, the runners are not able to pull
<MrCooper>
I see, thanks
pjakobsson has quit [Remote host closed the connection]
thaller has quit [Ping timeout: 480 seconds]
<italove>
hi, I'm getting the "Looks like you don't have enough privileges" message when trying to run jobs on my mesa fork, even though I have "CI-OK" on https://gitlab.freedesktop.org/users/italove/groups
<bentiss>
italove: so, looks like you have been added to the project (which makes the UI shows the ci-ok), but not the group itself, which makes runner-gating things you are not allowed to run workloads
<bentiss>
italove: if you open a MR against mesa, the pipeline will be authorized to run FWIW. But I'm going to create a mesa-ci-ok group and add you there, so you get access to the CI in your personal namespace
<italove>
yeah, running on MRs works, but I'd like to be able to run on non-MR branches
<bentiss>
italove: ok, solved. The problem was that the mesa/ci-ok group was internal, and the runner-gating token couldn't get the visibility on it. I marked the group as public and it's good now
<bentiss>
alright. One last server to reboot
<italove>
looks good now, thanks!
<bentiss>
no worries
slomo has joined #freedesktop
<bentiss>
svuorela: just in case, I set up the poppler/ci-ok group. If anyone in the poppler project needs CI access, they can be added here instead of giving the entire group membership
<bentiss>
svuorela: I would appreciate if you could forward that information to poppler maintainers ;)
scrumplex_ has quit [Quit: Quassel - Signing Off]
scrumplex has joined #freedesktop
<bentiss>
FWIW, all the nodes in the gitlab cluster have been rebooted now
<svuorela>
bentiss: forwarded.
<bentiss>
svuorela: thanks!
scrumplex_ has joined #freedesktop
scrumplex has quit [Ping timeout: 480 seconds]
vkareh has joined #freedesktop
AbleBacon_ has quit [Read error: Connection reset by peer]
pjakobsson has joined #freedesktop
alatiera has joined #freedesktop
<tintou>
Can someone add the virgl group to the CI-OK group?
phasta has joined #freedesktop
<mupuf>
tintou: done
thaller has joined #freedesktop
vkareh has quit [Quit: WeeChat 3.6]
vbenes has quit [Ping timeout: 480 seconds]
vbenes has joined #freedesktop
vkareh has joined #freedesktop
<tintou>
If I'm part of the CI-OK group, should I be allowed to use the shared runners when under a fork? Or is there something I can do to be able to do so?
<bentiss>
tintou: you should be in the same position you were previously, before we started enforcing the CI gating
___nick___ has joined #freedesktop
ximion has joined #freedesktop
<dcbaker>
daniels: cool, just wanted to make sure o hadn’t missed something important :)
karolherbst has quit [Quit: Konversation terminated!]
karolherbst has joined #freedesktop
<daniels>
dcbaker: you can file 'networking is sometimes unreliable' under disappointing-but-unsurprising
MrCooper has quit [Remote host closed the connection]
MrCooper has joined #freedesktop
jarthur has joined #freedesktop
vkareh has quit [Quit: WeeChat 3.6]
woodwose has joined #freedesktop
strk has joined #freedesktop
<strk>
I did read the topic BUT... pretty please, there must be a channel to ask for help about specs right ? I'm trying to find a DE-agnostic way to set PATH for a session
vyivel has quit [Ping timeout: 480 seconds]
vyivel has joined #freedesktop
<ishitatsuyuki>
is the Mesa tagging bot dead?
Guest8468 is now known as ybogdano
ybogdano is now known as Guest8656
ybogdano has joined #freedesktop
<jenatali>
ishitatsuyuki: Don't think so, why?
AbleBacon has joined #freedesktop
snuckls_ has joined #freedesktop
miracolix has quit [Read error: Connection reset by peer]
snuckls_ has quit [Ping timeout: 480 seconds]
ybogdano has quit [Ping timeout: 480 seconds]
ifreund has quit [Write error: connection closed]
ifreund has joined #freedesktop
ybogdano has joined #freedesktop
Kayden has quit [Quit: -> office]
phasta has quit [Quit: Leaving]
___nick___ has quit []
___nick___ has joined #freedesktop
___nick___ has quit []
___nick___ has joined #freedesktop
miracolix has joined #freedesktop
FileJanitor has joined #freedesktop
<FileJanitor>
Does AppStream do anything at all useful for traditional Apt setups?