fish-shell/tests/checks/exec.fish

# RUN: fish=%fish %fish %s

exec cat <nosuchfile
#CHECKERR: warning: An error occurred while redirecting file 'nosuchfile'
#CHECKERR: warning: Path 'nosuchfile' does not exist
echo "failed: $status"
#CHECK: failed: 1
not exec cat <nosuchfile
#CHECKERR: warning: An error occurred while redirecting file 'nosuchfile'
#CHECKERR: warning: Path 'nosuchfile' does not exist
echo "neg failed: $status"
#CHECK: neg failed: 0

# See that variable overrides are applied to exec'd processes
# Match the entire line because github actions passes commit messages in the environment,
# so any message that includes "foo=bar" would also be matched.
$fish --no-config -c 'foo=bar exec env' | grep '^foo=bar$'
# CHECK: foo=bar

# This needs to be last, because it actually runs exec.
exec cat </dev/null
echo "not reached"
Make tests usable with path with spaces This is somewhat subtle: The #RUN line in a littlecheck file will be run by a posix shell, which means the substitutions will also be mangled by it. Now, we have shell-quoted them, but unfortunately what we need is to quote them for inside a pre-existing layer of quotes, e.g. # RUN: fish -C 'set -g fish %fish' here, %fish can't be replaced with `'path with spaces/fish'`, because that ends up as # RUN: fish -C 'set -g fish 'path with spaces/fish'' which is just broken. So instead, we pass it as a variable to that fish: # RUN: fish=%fish fish... In addition, we need to not mangle the arguments in our test_driver. For that, because we insist on posix shell, which has only one array, and we source a file, we need to stop having that file use arguments. Which is okay - test_env.sh could previously be used to start a test, and now it no longer can because that is test_driver.sh's job. For the interactive tests, it's slightly different: pexpect.spawn(foo) is sensitive to shell metacharacters like space. So we shell-quote it. But if you pass any args to pexpect.spawn, it no longer uses a shell, and so we cannot shell-quote it. There could be a better way to fix this? 2024-12-28 03:54:43 +08:00			`# RUN: fish=%fish %fish %s`
Apply variable overrides for exec Fixes #9995 2023-10-07 00:15:25 +08:00
Reindent functions to remove useless quotes This does not include checks/function.fish because that currently includes a "; end" in a message that indent would remove, breaking the test. 2020-03-10 02:36:12 +08:00			`exec cat <nosuchfile`
Port some small tests to littlecheck 2020-02-08 17:38:11 +08:00			`#CHECKERR: warning: An error occurred while redirecting file 'nosuchfile'`
Improve error for redirections to invalid paths This finds the first broken component, to help people figure out where they misspelt something. E.g. ``` echo foo >/usr/lob/systemd/system/machines.target.wants/var-lib-machines.mount ``` will now show: ``` warning: Path '/usr/lob' does not exist ``` which would help with seeing that it should be "/usr/lib". 2021-11-20 04:11:28 +08:00			`#CHECKERR: warning: Path 'nosuchfile' does not exist`
Port some small tests to littlecheck 2020-02-08 17:38:11 +08:00			`echo "failed: $status"`
			`#CHECK: failed: 1`
Reindent functions to remove useless quotes This does not include checks/function.fish because that currently includes a "; end" in a message that indent would remove, breaking the test. 2020-03-10 02:36:12 +08:00			`not exec cat <nosuchfile`
Port some small tests to littlecheck 2020-02-08 17:38:11 +08:00			`#CHECKERR: warning: An error occurred while redirecting file 'nosuchfile'`
Improve error for redirections to invalid paths This finds the first broken component, to help people figure out where they misspelt something. E.g. ``` echo foo >/usr/lob/systemd/system/machines.target.wants/var-lib-machines.mount ``` will now show: ``` warning: Path '/usr/lob' does not exist ``` which would help with seeing that it should be "/usr/lib". 2021-11-20 04:11:28 +08:00			`#CHECKERR: warning: Path 'nosuchfile' does not exist`
Port some small tests to littlecheck 2020-02-08 17:38:11 +08:00			`echo "neg failed: $status"`
			`#CHECK: neg failed: 0`
Detect windows line endings when executing a file Fixes #2783. 2020-09-25 22:44:02 +08:00
Apply variable overrides for exec Fixes #9995 2023-10-07 00:15:25 +08:00			`# See that variable overrides are applied to exec'd processes`
tests/checks/exec: Match entire env line 2025-01-20 01:47:28 +08:00			`# Match the entire line because github actions passes commit messages in the environment,`
			`# so any message that includes "foo=bar" would also be matched.`
			`$fish --no-config -c 'foo=bar exec env' \| grep '^foo=bar$'`
Apply variable overrides for exec Fixes #9995 2023-10-07 00:15:25 +08:00			`# CHECK: foo=bar`

Detect windows line endings when executing a file Fixes #2783. 2020-09-25 22:44:02 +08:00			`# This needs to be last, because it actually runs exec.`
Reindent functions to remove useless quotes This does not include checks/function.fish because that currently includes a "; end" in a message that indent would remove, breaking the test. 2020-03-10 02:36:12 +08:00			`exec cat </dev/null`
Port some small tests to littlecheck 2020-02-08 17:38:11 +08:00			`echo "not reached"`