5 commits

Author	SHA1	Message	Date
Robert Hensing	8557d79650	tests/functional: Skip tests that don't work in NixOS environment yet	2024-06-20 14:54:11 +02:00
John Ericson	10f864c5ae	Ensure all functional scripts are (a) executable (b) have shebang ... This is good for shebang, and also good for future build system simplifications	2024-05-28 12:46:24 -04:00
John Ericson	2e12b58126	Shellcheck some test scripts ... Progress on #10795	2024-05-28 12:32:22 -04:00
wh0	2e5abc0fd0	tests: avoid a chroot store without sandbox support	2023-12-03 17:18:58 -08:00
John Ericson	68c81c7375	Put functional tests in tests/functional ... I think it is bad for these reasons when `tests/` contains a mix of functional and integration tests - Concepts is harder to understand, the documentation makes a good unit vs functional vs integration distinction, but when the integration tests are just two subdirs within `tests/` this is not clear. - Source filtering in the `flake.nix` is more complex. We need to filter out some of the dirs from `tests/`, rather than simply pick the dirs we want and take all of them. This is a good sign the structure of what we are trying to do is not matching the structure of the files. With this change we have a clean: ```shell-session $ git show 'HEAD:tests' tree HEAD:tests functional/ installer/ nixos/ ```	2023-10-06 09:05:56 -04:00

Renamed from tests/build-remote-trustless-should-fail-0.sh (Browse further)