| 12 Jul 2021 |
nix-community-alerts | [firing] reboot: nix-community-build01 just rebooted.
[resolved] uptime: nix-community-build01 has been up for more than 30 days.
| 09:33:31 |
nix-community-alerts | [resolved] reboot: nix-community-build01 just rebooted.
[resolved] uptime: nix-community-build01 has been up for more than 30 days.
| 09:38:31 |
| Alex Zero joined the room. | 14:13:08 |
lewo | taking the deployment lock for build03 | 21:09:42 |
lewo | released. | 21:17:29 |
| 13 Jul 2021 |
Mic92 | grahamc (he/him): I would like to help setting up cachix on our x86 linux ofborg builder and later maybe on macOS as well. This would require a cachix watch-store service, that uploads new packages as they are added using inotify - no changes in ofborg so. Domen Kožar already stated that he would be happy to sponsort that. | 12:11:48 |
Mic92 | * grahamc (he/him): I would like to help setting up cachix on our x86 linux ofborg builders and later maybe on macOS as well. This would require a cachix watch-store service, that uploads new packages as they are added using inotify - no changes in ofborg so. Domen Kožar already stated that he would be happy to sponsort that. | 12:12:01 |
Mic92 | We already have a similar set up running on our nix-community infrastructure. | 12:13:31 |
Mic92 | * grahamc (he/him): I would like to help setting up cachix on our x86 linux ofborg builders and later maybe on macOS as well. This would require a cachix watch-store service, that uploads new packages as they are added using inotify - no changes in ofborg so. Domen Kožar already stated that he would be happy to sponsor that. | 12:13:56 |
| Sandro joined the room. | 12:53:54 |
@grahamc:nixos.org | that sounds good, those machines aren't accessibly by anyone except trusted admins and ofborg, and people are likely to be building the PRs anyway so I think the threat model allows it | 13:04:20 |
@grahamc:nixos.org | the aarch64 box is a tricky one, probably not sufficient | 13:04:48 |
@grahamc:nixos.org | * the aarch64 box wouldn't work though | 13:08:14 |
Mic92 | Domen Kožar: should we use the same cache as used by https://github.com/NixOS ? | 13:25:42 |
Domen Kožar | Best to create a new cache I think | 13:47:30 |
Domen Kožar | Mic92 ^^ | 17:42:14 |
| 15 Jul 2021 |
| dbaynard joined the room. | 21:43:11 |
| 16 Jul 2021 |
nix-community-alerts | [firing] systemd_service_failed: nix-community-build03 failed to (re)start service cachix-watch-store.service.
| 03:25:21 |
nix-community-alerts | [resolved] systemd_service_failed: nix-community-build03 failed to (re)start service cachix-watch-store.service.
| 03:30:21 |
| vika (she/her) 🏳️⚧️ joined the room. | 19:43:40 |
| nixinator joined the room. | 23:13:51 |
| 17 Jul 2021 |
nix-community-alerts | [firing] systemd_service_failed: nix-community-build03 failed to (re)start service cachix-watch-store.service.
| 03:25:21 |
nix-community-alerts | [resolved] systemd_service_failed: nix-community-build03 failed to (re)start service cachix-watch-store.service.
| 03:30:21 |
Mic92 | In reply to @nix-community-alerts:matrix.org [firing] systemd_service_failed: nix-community-build03 failed to (re)start service cachix-watch-store.service. Maybe stopping now times out? | 04:55:11 |
Mic92 | Domen Kožar: This is my workaround now: https://github.com/nix-community/infra/blob/c65de96b680924e9bdb462c1e51c2088bcc6015a/roles/nix-community-cache.nix#L19 if you have any better idea... I think systemd services can also extend their stopping timeout when they implement notify and send EXTEND_TIMEOUT_USEC=... | 05:14:06 |
Mic92 | When I was looking in the logs there were still like 6000 items in the queue when it was killed | 05:14:51 |
Mic92 | The other alternative would to persist the queue and resume on start | 05:15:13 |
Domen Kožar | 6000 items! | 06:10:57 |
Domen Kožar | Happy to implement the notify signals | 06:11:24 |
Mic92 | Yes. We build a lot of emacs packages. | 08:02:26 |