You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The flake checks can be the same as what's in the cloud-reaper workflow file. Other checks should run parts of nix-watch itself and look for specific things, e.g:
nix-watch -c
touch <some file>
should cause the current process to be killed, resulting in an error: interrupted by user if the process takes long enough. If the output of nix-watch is captured to a file, a grep of the file for that error could be one way of checking it's working. Another way to test that the -c, --clear flag works would be to check the status of the PID.
The text was updated successfully, but these errors were encountered:
The flake checks can be the same as what's in the
cloud-reaper
workflow file. Other checks should run parts ofnix-watch
itself and look for specific things, e.g:should cause the current process to be killed, resulting in an
error: interrupted by user
if the process takes long enough. If the output ofnix-watch
is captured to a file, a grep of the file for that error could be one way of checking it's working. Another way to test that the-c, --clear
flag works would be to check the status of the PID.The text was updated successfully, but these errors were encountered: