fish-shell/tests/checks/check-all-fish-files.fish

#RUN: %fish -C 'set -l fish %fish' %s
# Test ALL THE FISH FILES
# in share/, that is - the tests are exempt because they contain syntax errors, on purpose

for file in $__fish_data_dir/**.fish
    $fish -n $file
end
# No output is good output
Add check to test all fish files with -n This executes `fish --no-execute` a whole bunch of times in order to find syntax errors in our fish scripts. tests/ is exempt because it contains syntax errors on purpose. This is a great idea in principle, but it takes ~4s on my system. 2020-02-17 22:31:47 +08:00			`#RUN: %fish -C 'set -l fish %fish' %s`
			`# Test ALL THE FISH FILES`
			`# in share/, that is - the tests are exempt because they contain syntax errors, on purpose`

Revert "Speed up check-all-fish-files when executed locally" My find (GNU findutils 4.8.0) prints > find: unknown predicate `-mnewer' So we would have to test for support. Also this is super hacky - tests aren't supposed to keep files around, this is something you would do in the build system. This reverts commit ddd0e28b4ff2982238ad3a29cb01ce657b8a5762. 2021-03-06 16:27:43 +08:00			`for file in $__fish_data_dir/**.fish`
			`$fish -n $file`
Speed up check-all-fish-files when executed locally Only check fish files that have been modified since the last time they were checked. (This continues with the assumption that we are testing for broken /usr/share fish scripts and not breakage of the fish parser, which is covered by all the other tests.) This saves 8 seconds on an NVMe disk under WSL. Won't affect integrity of CI runs, which start with a blank slate each time. 2021-03-06 12:40:40 +08:00			`end`
Add check to test all fish files with -n This executes `fish --no-execute` a whole bunch of times in order to find syntax errors in our fish scripts. tests/ is exempt because it contains syntax errors on purpose. This is a great idea in principle, but it takes ~4s on my system. 2020-02-17 22:31:47 +08:00			`# No output is good output`