[13:30:21] 10GitLab, 10serviceops-collab: Repository by URL import from Gerrit to GitLab fails - https://phabricator.wikimedia.org/T333447 (10Jelto) [13:39:17] 10GitLab, 10serviceops-collab: Repository by URL import from Gerrit to GitLab fails - https://phabricator.wikimedia.org/T333447 (10Jelto) p:05Triage→03Medium a:03Jelto According to some upstream issues https://gitlab.com/gitlab-org/gitlab/-/issues/384547 https://gitlab.com/gitlab-org/gitlab/-/issues/3794... [15:09:36] 10GitLab, 10serviceops-collab: Repository by URL import from Gerrit to GitLab fails - https://phabricator.wikimedia.org/T333447 (10Legoktm) Duplicate of {T333048}? [15:41:52] 10GitLab, 10serviceops-collab: Repository by URL import from Gerrit to GitLab fails - https://phabricator.wikimedia.org/T333447 (10Dzahn) I have definitely imported a repo from Gerrit before, seems like this must have been introduced in a gitlab version upgrade. [16:32:35] 10GitLab (Administration, Settings & Policy), 10Privacy Engineering, 10Product-Analytics, 10Privacy, and 2 others: Request for Private repos to be enabled - https://phabricator.wikimedia.org/T305082 (10mpopov) >>! In T305082#8735744, @Legoktm wrote: >> @Legoktm This view skips over any work that isn't engi... [19:02:08] We enabled another instance wide Gitlab Runner that accepts untagged jobs. Let us (Release Engineering Team) know if you experience any issues. [19:43:00] what's a tagged vs untagged job mean? [19:46:28] You can associate tags (arbitrary strings) with jobs in .gitlab-ci.yml. These tags are used to choose a runner for the job. Runners can be figured with their own tags that indicate their available for jobs that mention that tag. Runners can optionally be configured to run jobs that haven't specified any tags at all. In short this means that we added another generally available runner that can be used by any repo. [19:47:05] s/available/availability/. [19:47:57] gotcha, ty [19:48:12] This new runner is in a different environment than the one we made available earlier, so it may behave differently. [19:49:15] e.g., I wonder if https://gitlab.wikimedia.org/arlolra/mwbot/-/jobs/87322 exceeded the memory limits of the container it ran int. [19:49:18] *in [21:49:29] Has anyone setup a gitlab CI job that uses tox + multiple python versions yet? I'm wondering mostly about a container that would have a bunch of python3.x versions already installed that someone might be maintaining. [21:56:27] https://gitlab.wikimedia.org/repos/releng/scap tests bullseye and buster. [21:56:38] https://gitlab.wikimedia.org/repos/releng/scap/-/blob/master/.gitlab-ci.yml [21:57:24] dancy: awesome. I'll take a look and see if I can grok how it is working. [21:58:02] That stuff is not using tox, but it could. For scap we use a separate job to test each distro, versus one job that tests them both [22:00:14] * bd808 wishes that kokkuri had a name he could remember and spell [22:00:44] haha.. it does take some getting used to.. "how many k's?" [22:02:13] I like the way this works with blubber variants :) [23:38:18] is half-way through the WP article.... "kokkuri-san refers to the being that is summoned: it is considered by the Japanese to be some sort of animal spirit that is a mix between a fox, dog, and raccoon. These three animals are meant to reflect the dual nature of the being, justifying its different personality traits: the fox being a trickster or teacher, and the raccoon being both a bearer of [23:38:24] mischief or good fortune" [23:39:03] foxdog