| 10 Jul 2021 |
| Mic92 (Old)changed room power levels. | 14:06:15 |
nix-community-alerts | [firing] systemd_service_failed: nix-community-build03 failed to (re)start service hydra-post-init.service.
| 14:49:31 |
| Mic92 (Old) left the room. | 15:00:12 |
ryantm | Deploying to build02 | 18:24:41 |
ryantm | Done. | 18:45:55 |
nix-community-alerts | [firing] systemd_service_failed: nix-community-build03 failed to (re)start service hydra-post-init.service.
| 18:54:31 |
nix-community-alerts | [firing] systemd_service_failed: nix-community-build03 failed to (re)start service hydra-post-init.service.
| 22:59:31 |
| 11 Jul 2021 |
nix-community-alerts | [firing] systemd_service_failed: nix-community-build03 failed to (re)start service hydra-post-init.service.
| 03:04:31 |
nix-community-alerts | [resolved] systemd_service_failed: nix-community-build03 failed to (re)start service hydra-post-init.service.
| 05:29:31 |
nix-community-alerts | [firing] uptime: nix-community-build01 has been up for more than 30 days.
| 20:55:31 |
| 12 Jul 2021 |
nix-community-alerts | [firing] uptime: nix-community-build01 has been up for more than 30 days.
| 01:00:31 |
nix-community-alerts | [firing] uptime: nix-community-build01 has been up for more than 30 days.
| 05:05:31 |
nix-community-alerts | [firing] uptime: nix-community-build01 has been up for more than 30 days.
| 09:10:31 |
nix-community-alerts | [resolved] uptime: nix-community-build01 has been up for more than 30 days.
| 09:30:31 |
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 |