A hydra failure might be cached; I had to make a dummy change (renamed a dummy variable) to make hydra forget the failure in a previously cached build.

@winitzki Unfortunately that didn't work.
Hydra is out of disk space; See https://hydra.dhall-lang.org/build/115335/nixlog/1 and https://hydra.dhall-lang.org/build/115308/nixlog/1 .

I don't have access to that machine; @Gabriella439 can you have a look?

Hm, I think Hydra is dead:

500 Internal Server Error
DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI connect('dbname=hydra;user=hydra;','',...) failed: connection to server on socket "/run/postgresql/.s.PGSQL.5432" failed: No such file or directory
Is the server running locally and accepting connections on that socket? at /nix/store/naxc4jx308gkv96x7g7a8p6phq2hhk4z-hydra-perl-deps/lib/perl5/site_perl/5.34.1/DBIx/Class/Storage/DBI.pm line 1639. at /nix/store/w1cc6bxw43hf7dcya3ar95zckr0g9m8v-hydra-2022-05-03/libexec/hydra/lib/Hydra/Helper/CatalystUtils.pm line 423

Gently pinging @Gabriella439 .

"Hydra can't really be killed. You cut one head off, two more will grow."

"Hydra can't really be killed. You cut one head off, two more will grow."

@winitzki 😄 It seems you are right; It's working again. It appears only the web interface is reachable again, but there are no jobs enqueued for my latest commit.