| 15 Oct 2025 |
 helle (just a stray cat girl) | it is a bunch of things that have a sort of circular dependency, that has a few ways of breaking it depending on priorities we want to set | 10:21:28 |
| helle (just a stray cat girl) | anyway, back to more priority items if I sit down for code for now | 10:25:59 |
| helle (just a stray cat girl) | lmao, yeah, we missed that merge window again, sigh | 11:15:55 |
| helle (just a stray cat girl) | (downside of doing several tasks at once, guess I need to make it ding a loud alarm when the cake is ready, erm, a merge can be done) | 11:16:56 |
 Rutile (Commentator2.0) feel free to ping | ... still says active for me? | 11:22:43 |
| helle (just a stray cat girl) | https://gerrit.lix.systems/c/lix/+/4342 so for me it shows as needs rebasing, which means another CI run | 11:24:01 |
| helle (just a stray cat girl) | (which we've had to do 2 extra after the initial "just before merge" one, meaning the CI got hit 2x without an absolute need) | 11:24:34 |
| helle (just a stray cat girl) | (tell me if I am just holding it wrong) | 11:25:58 |
| Rutile (Commentator2.0) feel free to ping | 
Download image.png | 11:28:50 |
| helle (just a stray cat girl) | yeah, it has however as actions I can only to Rebase, Abandon or Edit, so that agains means a rebase | 11:31:49 |
| Rutile (Commentator2.0) feel free to ping | oh, not all tests have run yet | 11:40:41 |
| Rutile (Commentator2.0) feel free to ping | its waiting on darwin | 11:40:45 |
| Rutile (Commentator2.0) feel free to ping | just not showing as they aren't running yet | 11:40:51 |
| helle (just a stray cat girl) | from my end they showed as having all run what | 11:41:08 |
| helle (just a stray cat girl) | oh hell | 11:41:20 |
| helle (just a stray cat girl) | I just noticed | 11:41:23 |
| Rutile (Commentator2.0) feel free to ping | check the "checks" tab | 11:41:26 |
| helle (just a stray cat girl) | okay, that isn't the clearest lol | 11:41:32 |
 aloisw | I wonder why there is a rebase button when there is nothing to rebase… | 11:42:17 |
| aloisw | (Not an issue on your end, I see it for my own changes too.) | 11:42:30 |
| helle (just a stray cat girl) | I wonder if we can make the "queued jobs" show up more obviously in Gerrit like running ones are | 11:46:17 |
| helle (just a stray cat girl) | because that would make it way more obvious | 11:46:28 |
| helle (just a stray cat girl) | (we know we can check buildkite, but it is not the immediate thought I have if it only shows me | 11:47:11 |
| helle (just a stray cat girl) | 
Download clipboard.png | 11:47:13 |
| helle (just a stray cat girl) | (it also probably should not be "Not run" but "Queued" but idk if we can easily do this without losing it for actual cases where we end up having a CI "Not run" situation) | 11:49:27 |
| helle (just a stray cat girl) | the irony of forgetting to check Buildkite and forgetting how the queue is represented on a doc patch to mention for Buildkite in the hacking document is not lost on us | 12:00:24 |
 just1602 | This morning I saw that https://github.com/flokli/gerrit-queue has been archived, and I was wondering what the infra team was planning to use as a merge queue? | 14:26:17 |
 raitobezarius | I had planned to take inspiration from flokli's code and integrate it into gerrit-autosubmit (which is simply an autosubmitter) | 15:42:31 |
| raitobezarius | The thing that shows the jobs is a JavaScript plugin (very hackable), you could probably pull the JS console and hack to see if there's missing data we could be processing to show this | 16:34:26 |
| helle (just a stray cat girl) | oh, I can have look | 16:36:37 |
