00:41 <Xe> how do I get a reason for why xwayland isn't starting?

07:09 <eric_engestrom> DemiMarie: not trying to be fighty, but gmail is well known for randomly dropping emails that don't come from google or microsoft, so if there's an email that's important for you to receive, you need to _not_ use gmail, as the rest of the world can't do anything about google's behaviour

07:10 <eric_engestrom> (and for what it's worth, I've also been receiving all emails just fine, on my non-google email provider)

14:57 <eric_engestrom> has anyone else noticed retry buttons disappeared on job pages?

14:58 <eric_engestrom> well, no everywhere actually, which is what makes it even weirder

14:58 <eric_engestrom> on mesa for instance, I still have the retry button, but on ci-tron it's gone

15:04 <slomo> yes, we had that in gstreamer

15:04 <slomo> __tim worked around that somehow

15:05 <eric_engestrom> I'm interested in the "somehow" :)

15:05 <daniels> at a guess, ci-tron doesn't use MR pipelines?

15:06 <mupuf> daniels: we try to. and some jobs have it and some don't

15:06 <mupuf> but I'll keep an eye

16:59 <__tim> eric_engestrom, mupuf, in our case what changed was (gitlab upgrade presumably) that MR pipelines for developers/maintainers are now run in the upstream project namespace (and no longer in the fork); then in the project repository settings we have a list of protected branches that people are allowed to merge/push on, and a wildcard * protected

16:59 <__tim> branch that had `No one` / `No one` permissions for being allowed to merge/push to. And that was what prevented the job control apparently

17:00 <mupuf> __tim: oooh, thanks!

17:00 <__tim> after changing that to developers/maintainers being allowed to merge to `*` it worked again

17:01 <__tim> which feels somewhat questionable seeing that the MR was against the `main` branch where devs already have that permission, but who am I to argue with the ways of the gitlab

17:04 <eric_engestrom> __tim: thanks!

17:05 <__tim> Did that sort it for you as well?

17:06 <eric_engestrom> and yeah like mupuf said, we tried to get MR pipelines but for some reason it's not happening; feel free to have a look at https://gitlab.freedesktop.org/gfx-ci/ci-tron/-/blob/main/.gitlab-ci.yml or the gitlab settings (that last part is only for daniels and other admins)

17:07 <mupuf> __tim: we'll test tomorrow

17:08 <eric_engestrom> __tim: I haven't checked, but since we already have the "MR pipelines are not in the correct namespace" problem, this might not fix it

17:13 <__tim> iirc somewhere in the gitlab docs I saw that there was a hidden project setting for that (where the MR pipelines should run) that can be set via the API

17:13 <__tim> but I might be making that up, don't have the link at hand right now

17:39 <eric_engestrom> I didn't have to do anything when I set up the mesa ci 🤷

17:39 <eric_engestrom> although maybe it wasn't running the pipeline in the right namespace at the time, and that was fixed later? I honestly don't remember

17:42 <__tim> which one is the "right" namespace? :)

20:06 <alatiera> I saw a new setting about "who" has access to project variables now as well

20:06 <alatiera> but didn't find much more yday

22:29 <eric_engestrom> __tim: fair question; in my case, the target namespace is the one I consider the right one, at least when the submitter is Developer or above in the target repo