Now that we've got a system which properly evaluates and builds again, let's format it so all our CI passes
+1
-3
packetmix/packages/bluesky-pds/default.nix
+26
packetmix/systems/umber/auto-shutdown.nix
+1
-1
.tangled/workflows/packetmix-build.yml
History
5 rounds
0 comments
3 commits
expand
collapse
The power to umber turns off at midnight. Therefore, we should shut it
down beforehand to make sure it shuts down cleanly
This IP was changed in the release and treefmt workflows, but we missed
it in the build workflow
expand 0 comments
3 commits
expand
collapse
Now that we've got a system which properly evaluates and builds again,
let's format it so all our CI passes
The power to umber turns off at midnight. Therefore, we should shut it
down beforehand to make sure it shuts down cleanly
This IP was changed in the release and treefmt workflows, but we missed
it in the build workflow
1/5 failed, 4/5 success
expand
collapse
expand 0 comments
3 commits
expand
collapse
Now that we've got a system which properly evaluates and builds again,
let's format it so all our CI passes
The power to umber turns off at midnight. Therefore, we should shut it
down beforehand to make sure it shuts down cleanly
This IP was changed in the release and treefmt workflows, but we missed
it in the build workflow
1/5 failed, 1/5 timeout, 3/5 success
expand
collapse
expand 0 comments
3 commits
expand
collapse
Now that we've got a system which properly evaluates and builds again,
let's format it so all our CI passes
The power to umber turns off at midnight. Therefore, we should shut it
down beforehand to make sure it shuts down cleanly
This IP was changed in the release and treefmt workflows, but we missed
it in the build workflow
1/5 failed, 2/5 timeout, 2/5 success
expand
collapse
expand 0 comments
1 commit
expand
collapse
Now that we've got a system which properly evaluates and builds again,
let's format it so all our CI passes