| 18 Mar 2026 |
raitobezarius | FYI, it's easier to reach out for development discussions over zulip.lix.systems ; if you plan to contribute more actively, I recommend joining it :) | 13:09:34 |
zoë (she/her) | i've already made an account for it (because for some reason i couldn't join the matrix spaces before), but i'm not too good in more formal environments (at least to me zulip feels more formal) ;-; and i think the amount of things i can contribute given my skillset is not gonna be very high, especially given the time constraints i'll be in soon enough x) | 13:11:46 |
zoë (she/her) | anyway, i hesitated doing that this time, but i'll do it next time then :) | 13:12:16 |
zoë (she/her) | * anyway, i hesitated doing that this time, but i'll do it next time then, thanks for the clarification :) | 13:12:22 |
raitobezarius | i'd say zulip is meant to make conversations more structured to help us to help you or help yourselves follow what you care about on a development level | 13:15:46 |
raitobezarius | (sure, it's less tolerant of offtopics tangents but that's a feature :P) | 13:16:01 |
raitobezarius | but no problem, this was just an invitation | 13:17:07 |
zoë (she/her) | i saw on the wiki you were talking about maybe retiring the matrix anyway given the infrastructure problems with it (though i'd be sad to see it go given my reasons above), so i guess i might have to get used to zulip at some point :p | 13:17:40 |
piegames | As per the recent meeting on this, Matrix will stay with a slightly reduced channel list | 13:39:22 |
zoë (she/her) | (i wasn't sure what zulip channel would be best for this ;-;) is there anyway to re-launch the CI for a CL? i'm pretty sure the devShell and clang-tidy failures are just flaky ci, especially given the error messages and the fact that other pipelines (incl. on the same platform) were completely fine. the contributing wiki for the ci says "just login to restart the build" but i don't have the access level for it. | 22:31:12 |
zoë (she/her) | * (i wasn't sure what zulip channel would be best for this ;-;) is there anyway to re-launch the CI for a CL? i'm pretty sure the devShell and |clang-tidy](https://buildkite.com/afnix/lix/builds/966/summary?sid=019d01d2-d404-41ec-a6c1-df3836789413&tab=output) failures are just flaky ci, especially given the error messages and the fact that other pipelines (incl. on the same platform) were completely fine. the contributing wiki for the ci says "just login to restart the build" but i don't have the access level for it. | 22:32:07 |
zoë (she/her) | * (i wasn't sure what zulip channel would be best for this ;-;) is there anyway to re-launch the CI for a CL? i'm pretty sure the devShell and clang-tidy failures are just flaky ci, especially given the error messages and the fact that other pipelines (incl. on the same platform) were completely fine. the contributing wiki for the ci says "just login to restart the build" but i don't have the access level for it. | 22:32:29 |
| zoë (she/her) set a profile picture. | 22:36:46 |
Sergei Zimmerman (xokdvium) | In reply to @blokyk:matrix.org (i wasn't sure what zulip channel would be best for this ;-;) is there anyway to re-launch the CI for a CL? i'm pretty sure the devShell and clang-tidy failures are just flaky ci, especially given the error messages and the fact that other pipelines (incl. on the same platform) were completely fine. the contributing wiki for the ci says "just login to restart the build" but i don't have the access level for it. Can’t you force-push an amended commit without any diff? That should do the trick I think | 22:38:50 |
zoë (she/her) | nah, that's what i did and it noticed that no code actually changed so it didn't re-run it | 22:39:55 |
piegames | In reply to @blokyk:matrix.org (i wasn't sure what zulip channel would be best for this ;-;) is there anyway to re-launch the CI for a CL? i'm pretty sure the devShell and clang-tidy failures are just flaky ci, especially given the error messages and the fact that other pipelines (incl. on the same platform) were completely fine. the contributing wiki for the ci says "just login to restart the build" but i don't have the access level for it. You can get permissions if you ask, though I forgot where to ask 🙃 | 23:09:39 |
raitobezarius | In reply to @xokdvium:matrix.org Can’t you force-push an amended commit without any diff? That should do the trick I think Code changes are required for that | 23:11:32 |
raitobezarius | The CI is smart (still dumb) :p | 23:11:42 |
Sergei Zimmerman (xokdvium) | In reply to @raitobezarius:matrix.org Code changes are required for that Change one character and change back works? | 23:12:04 |
Sergei Zimmerman (xokdvium) | Or does the source hash get memoised? (Just curious) | 23:12:43 |
raitobezarius | Gerrit understands the kinds of delta a patchset | 23:14:19 |
raitobezarius | A NO_CODE_CHANGE won't trigger CI | 23:14:35 |
raitobezarius | Changing a character will trigger CI, yes | 23:14:47 |
piegames | In reply to @piegames:flausch.social You can get permissions if you ask, though I forgot where to ask 🙃 I restate my position here that retriggering CI builds should not be a gated permission and instead be accessible to all logged-in users | 23:17:53 |
zoë (she/her) | if you can't remember i can just change the release notes slightly, that should be enough x) | 23:18:19 |
zoë (she/her) | * if you can't remember i can just change the release notes slightly, that should be enough x)
edit: aaand it's pushed & restarted, thx folks | 23:20:15 |
raitobezarius | In reply to @piegames:flausch.social I restate my position here that retriggering CI builds should not be a gated permission and instead be accessible to all logged-in users I did not buy the Buildkite company yet alas | 23:20:31 |
raitobezarius | (and I am not sure that a bot would make things more discoverable but maybe, not sure) | 23:21:50 |
delroth | CI failure UI on the gerrit side could include instructions on how to retrigger via bot | 23:22:39 |
delroth | (and I presume besadii could listen for gerrit CL comments, for example?) | 23:23:03 |