01:32 <whot> huh, did the spam logs disappear from the admin interface?

10:53 <lynxeye> daniels: bentiss: is it possible to move a gitlab runner registration from a project scope to mesa group or even instance scope? Leonard set up a runner to access our lava lab, which we intend to use for some more Mesa (and possibly weston) CI coverage and has the runner registered in https://gitlab.freedesktop.org/hnez/pengutronix-mesa-lava-test/

11:21 <mupuf> lynxeye: let me see

11:23 <mupuf> lynxeye: how many DUTs do you have?

11:23 <mupuf> You need one gitlab runner per DUT

11:24 <mupuf> and no. It does not look like we can make a project runner an instance runner

11:25 <lynxeye> mupuf: currently it's only the single mba8mpxl board

11:25 <mupuf> ack

11:26 <mupuf> lynxeye: so... need a token?

19:39 <__tim> ooc, is there a configurable deadline in gitlab how long artifact uploads are allowed to take?

19:41 <__tim> seeing some issues with our mac runners where the upload sometimes is superslow (bouncing around between 30-100kB/sec) and then it results in ERROR: Uploading artifacts as "archive" to coordinator... error error=couldn't execute POST against

19:41 <__tim> https://gitlab.freedesktop.org/api/v4/jobs/71055806/artifacts?artifact_format=zip&artifact_type=archive&expire_in=5+days: Post "https://gitlab.freedesktop.org/api/v4/jobs/71055806/artifacts?artifact_format=zip&artifact_type=archive&expire_in=5+days": context deadline exceeded (Client.Timeout exceeded while awaiting headers) id=71055806

19:41 <__tim> token=glcbt-64

19:42 <__tim> not sure it's worth debugging the network issue at this point, but if there's a timeout that could be extended as a quickfix that'd be nice