13:48 <slomo> any guesses what this is about https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/issues/444#note_2115739 ? valid comment marked as spam

13:49 <slomo> erm it was edited now :) original comment was "I am unable to post my comment here, as it keeps getting recognised as spam. I moved it to a pastebin

13:49 <slomo> https://pastebin.com/zdXAbrhk"

14:42 <gallo[m]> hey bentiss, could you help Dmitrii to run pipelines in his fork of gfx-ci/linux repository? He is stumbling upon the authentication errors for running pipelines, e.g. https://gitlab.freedesktop.org/digetx/linux/-/jobs/49968614

14:49 <bentiss> gallo[m]: please make him request guest access on https://gitlab.freedesktop.org/mesa/ci-ok

14:49 <bentiss> once validated he should be able to run pipelines

16:50 <gallo[m]> bentiss: he is already in CI-OK https://gitlab.freedesktop.org/users/digetx/groups, but not in mesa/CI-OK. Is this needed for allowing him to run pipelines for his gfx-ci/linux fork? By the way, it seems that I can't add members to the mesa/CI-OK group, at least I couldn't find any magic button in the link you sent me, and the list is empty for me.

18:12 <bentiss> gallo[m]: added you as a maintainer of ci-ok, so you can add more people

18:14 <bentiss> gallo[m]: regarding the "already in CI-OK" it's an issue in gitlab in which if you are in a project where the group has been included in CI-OK, you'll appear as a member of CI-OK but if you request "is that person a memeber of CI-OK", given that the person is not directly in a group included in CI-OK, it will return false

18:14 <bentiss> so it's a bummer, but we need to manually add people to a group included in CI-OK for that check to be vali

18:23 <gallo[m]> Thanks, bentiss, for the explanation

18:23 <gallo[m]> but I still can't add anyone. It seems that only members with an Owner role can add users to a group in GItlab https://docs.gitlab.com/ee/user/group/#add-users-to-a-group

19:21 <Guest2187> bentiss: where can I see the list of groups included in CI-OK? I recall there was a list somewere but I couldn't find at https://gitlab.freedesktop.org/groups/ci-ok

19:30 <Guest2187> ah, found it https://gitlab.freedesktop.org/groups/ci-ok/-/group_members

19:32 <Guest2187> bentiss: gallo : for drm-ci, wouldn't drm/ci-ok make more sense https://gitlab.freedesktop.org/groups/drm/ci-ok ? there is a "request access" button there, should I instruct people to go through it?

19:34 <Guest2187> I would like to add this instructions in the kernel docs

19:37 <gallo[m]> koike: pointing new users to the "request access" interaction seems to be a good idea. I am also confused by using mesa/CI-OK instead of gfx-ci/CI-OK, linux/CI-OK or drm/CI-OK.

20:00 <bentiss> yep, that seems like a good idea. Creating drm/ci-ok and adding gallo[m] as the owner

20:00 <bentiss> actually, drm/ci-ok already exists

20:03 <bentiss> gallo[m]: just added you as an owner. There is already a request access request pending :)

20:03 <bentiss> feel free to set up whatever rule you want to give these permissions

20:08 <gallo[m]> bentiss: Thank you! I've added Dmitrii. I'm now wondering how Koike can run a pipeline in her fork of gfx-ci/linux without being blocked, given her absence from drm/ci-ok group. Is being a part of mesa/ci-ok enough for it?

20:28 <Guest2187> gallo: if I understand correctly, being part of any group listed on https://gitlab.freedesktop.org/groups/ci-ok/-/group_members?tab=groups is enough

20:29 <Guest2187> and I'm part of gfx-ci

20:30 <bwidawsk> Do I need to do anything to get my container registry deletions scheduled?

20:30 <bwidawsk> I already marked all the invalid ones as delete

20:39 <Guest2187> gallo: I mean, if you got added to the group (and not just to a project in the group)

20:45 <gallo[m]> koike: thanks, the penny has dropped now