| 28 Jun 2025 |
 ElvishJerricco | But that timestamp has come and gone | 03:31:28 |
| ElvishJerricco | long gone | 03:31:30 |
| ElvishJerricco | should it still have that disabledUntil field if the time has passed? | 03:31:48 |
 hexa | I don't think so | 03:32:06 |
| hexa | or yes, it can | 03:32:22 |
| hexa | h.n.o has that as well | 03:32:27 |
| ElvishJerricco | My other builder has "disabledUntil" : 0, | 03:32:40 |
| hexa | yeah, if it never failed | 03:32:46 |
| hexa | I think consecutiveFailures gets reset when it continues working | 03:33:05 |
| hexa | but disabledUntil and lastFailure are sticky until queue-runner restart | 03:33:24 |
| hexa | possibly stale ssh session? | 03:33:51 |
| hexa | kill the local nix-daemon? | 03:34:04 |
| hexa | test the ssh connection? | 03:34:08 |
| ElvishJerricco | well ssh is working, it seems | 03:36:08 |
| ElvishJerricco | the way this hydra is set up is a little stupid | 03:36:17 |
| ElvishJerricco | it's running in a nixos container on the host that is the builder :P | 03:36:34 |
| ElvishJerricco | I don't remember why I set it up this way; I assume the daemon-socket bind mounted from the host in the container would have let hydra use the local machine as a builder | 03:38:23 |
| ElvishJerricco | huh, restarting the nix daemon on the host, there's three processes left in the systemd unit from the previous service instance | 03:40:06 |
