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-27 19:54:43 +00:00
|
|
|
#RUN: fish=%fish filter_ctrls=%filter-control-sequences %fish %s
|
2021-07-21 20:33:39 +00:00
|
|
|
# Some tests of the "return" builtin.
|
|
|
|
|
|
|
|
$fish -c 'return 5'
|
|
|
|
echo $status
|
|
|
|
# CHECK: 5
|
|
|
|
|
|
|
|
$fish -c 'exit 5'
|
|
|
|
echo $status
|
|
|
|
# CHECK: 5
|
|
|
|
|
|
|
|
$fish -c 'echo foo; return 2; echo bar'
|
|
|
|
# CHECK: foo
|
|
|
|
# but not bar
|
|
|
|
echo $status
|
|
|
|
# CHECK: 2
|
|
|
|
|
2024-04-12 10:19:32 +00:00
|
|
|
begin
|
|
|
|
$fish -ic 'echo interactive-foo; return 69; echo interactive-bar'
|
|
|
|
# CHECK: interactive-foo
|
|
|
|
# but not bar
|
|
|
|
echo $status
|
|
|
|
# CHECK: 69
|
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-27 19:54:43 +00:00
|
|
|
end | $fish $filter_ctrls
|
2022-09-25 17:37:10 +00:00
|
|
|
|
|
|
|
# Verify negative return values don't cause UB and never map to 0
|
|
|
|
function empty_return
|
|
|
|
return $argv[1]
|
|
|
|
end
|
|
|
|
|
2022-10-23 20:42:53 +00:00
|
|
|
for i in (seq -- -550 -1)
|
2022-09-25 17:37:10 +00:00
|
|
|
empty_return $i
|
|
|
|
if test $status -eq 0
|
|
|
|
echo returning $i from a fish script maps to a $status of 0!
|
|
|
|
end
|
|
|
|
end
|
|
|
|
# CHECK:
|