| 3 Oct 2025 |
 toonn | Does anyone artifacts directly to the nix-community cache? | 10:04:48 |
|  @realsnick:matrix.org removed their profile picture. | 10:07:21 |
| @realsnick:matrix.org removed their display name logger. | 10:07:28 |
| @realsnick:matrix.org left the room. | 10:07:45 |
|  @bootstrapper:matrix.org removed their profile picture. | 10:08:11 |
| @bootstrapper:matrix.org removed their display name Ido Samuelson. | 10:08:31 |
| @bootstrapper:matrix.org left the room. | 10:09:00 |
 Bot_wxt1221 | 
Download Screenshot_20251003_181223.jpg | 10:12:35 |
| toonn | *push | 10:13:59 |
 Gaétan Lepage | Technically, all the derivations built by the nix-community buildbot instance (the CI used by several projects of the organization) are pushed to the nix-community cache. | 11:32:01 |
 Yureka (she/her) | I think the CACHIX_TOKEN is also passed directly into all CI runs on the projects (not on PRs though)? | 11:39:44 |
| Yureka (she/her) | 
Download foo.png | 11:40:58 |
| Yureka (she/her) |
This secret overrides an organization secret
| 11:41:08 |
|  hash joined the room. | 15:36:34 |
 hexa | I hope y'all progress on the self-hosted cache plan | 22:33:53 |
| hexa | and then ideally one cache per project | 22:34:06 |
|  moleksiak joined the room. | 23:16:58 |
| 4 Oct 2025 |
 zowoq | I guess this also means separate builders for each project with a further separation for untrusted builds (PRs from forks)? | 00:42:53 |
|  aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) changed their profile picture. | 08:41:03 |
| aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) changed their profile picture. | 08:41:27 |
|  dramforever joined the room. | 12:28:10 |
| dramforever | hi, i'm trying to help unblock the current staging-next -> master, and i need somewhere to test darwin stuff. would appreciate if someone would make this happen: https://github.com/nix-community/infra/pull/1992 | 12:53:52 |
| 5 Oct 2025 |
| hexa | Right, that makes it complicated fast | 14:34:54 |
| 6 Oct 2025 |
 Matt Sturgeon | How do we force buildbot to rebuild a merge queue group?
We had an intermittent failure on the PR's build which was solved by clicking rebuild.
IIUC, the same thing happened when we enqueued the PR; the merge group's build failed.
Now each time we queue the PR we get the cached failure, and we can't trigger a rebuild because GitHub deletes the merge group ref when it dequeues it.
(This PR: https://github.com/nix-community/nixvim/pull/3724) | 08:46:56 |
| Matt Sturgeon | Thanks @zowoq:matrix.org | 09:10:50 |
 Mic92 | @mattsturg:matrix.org: if you go to the eval build step, there is a restart button after github login | 09:28:45 |
| Mic92 | Latest buildbot-nix will also cache use the old evaluation, so it should only start failed evaluations | 09:29:49 |
| Mic92 | I should probably improve the message on cached failures regarding that. I have them actually disable in my installations, because they can only be restarted by repo owners and not contributera | 09:31:37 |
| Mic92 | * I should probably improve the message on cached failures regarding that. I have them actually disable in my installations, because they can only be restarted by repo owners and not contributers | 09:31:51 |
 SomeoneSerge (back on matrix) | Related: now trying to asses how much of hydra+builders+cache can be split up into microvms | 09:58:43 |
