run-file () { local spec_name=$1; shift; local spec_file=spec/$spec_name.test.sh; local suite; suite=$(test/sh_spec.py --print-spec-suite $spec_file); local spec_subdir; case $suite in osh) spec_subdir='osh-cpp' ;; ysh) spec_subdir='ysh-cpp' ;; *) die "Invalid suite $suite" ;; esac; local base_dir=_tmp/spec/$spec_subdir; mkdir -v -p $base_dir; sh-spec $spec_file --timeout 10 --oils-bin-dir $PWD/bin --oils-cpp-bin-dir $REPO_ROOT/_bin/cxx-asan --tsv-output $base_dir/${spec_name}.tsv "$@" } builtin-trap-bash: spec test case results

Results for builtin-trap-bash.test.sh

status	osh	osh-cpp
pass	16	16
ok	3	3
N-I	2	2
FAIL	2	2
total	23	23

case	osh	osh-cpp	description
0	pass	pass	trap -l
1	pass	pass	trap -p
2	pass	pass	trap -p in child is BUGGY in bash
3	pass	pass	trap DEBUG ignores $?
4	pass	pass	but trap DEBUG respects errexit
5	ok	ok	trap DEBUG with 'return'
	details	details
6	pass	pass	trap DEBUG with 'exit'
7	pass	pass	trap DEBUG with non-compound commands
8	pass	pass	trap DEBUG and control flow
9	pass	pass	trap DEBUG and command sub / subshell
10	pass	pass	trap DEBUG not run in forked interpreter for first pipeline part
11	ok	ok	One 'echo' in first pipeline part - why does bash behave differently from case above?
	details	details
12	ok	ok	trap DEBUG and pipeline (lastpipe difference)
	details	details
13	pass	pass	trap DEBUG function call
14	pass	pass	trap DEBUG case
15	N-I	N-I	trap DEBUG for each
	details	details
16	N-I	N-I	trap DEBUG for expr
	details	details
17	pass	pass	trap DEBUG if while
18	FAIL	FAIL	trap RETURN
	details	details
19	FAIL	FAIL	Compare trap DEBUG vs. trap ERR
	details	details
20	pass	pass	Combine DEBUG trap and USR1 trap
21	pass	pass	Combine ERR trap and USR1 trap
22	pass	pass	Combine DEBUG trap and ERR trap

32 passed, 6 OK, 4 not implemented, 0 BUG, 2 failed, 0 timeouts, 0 cases skipped
2 failed under osh

Details on runs that didn't PASS

osh	5 trap DEBUG with 'return' stdout: [7] stderr:
osh-cpp	5 trap DEBUG with 'return' stdout: [7] stderr:
osh	11 One 'echo' in first pipeline part - why does bash behave differently from case above? stdout: LINENO=7 pipeline LINENO=8 ok stderr:
osh-cpp	11 One 'echo' in first pipeline part - why does bash behave differently from case above? stdout: LINENO=7 pipeline LINENO=8 ok stderr:
osh	12 trap DEBUG and pipeline (lastpipe difference) stdout: [6] a [6] b [8] 2 [10] 1 [14] 1 stderr:
osh-cpp	12 trap DEBUG and pipeline (lastpipe difference) stdout: [6] a [6] b [8] 2 [10] 1 [14] 1 stderr:
osh	15 trap DEBUG for each stdout: [7] x=1 [7] x=2 [10] ok stderr:
osh-cpp	15 trap DEBUG for each stdout: [7] x=1 [7] x=2 [10] ok stderr:
osh	16 trap DEBUG for expr stdout: [7] i=3 [7] i=4 [10] ok stderr:
osh-cpp	16 trap DEBUG for expr stdout: [7] i=3 [7] i=4 [10] ok stderr:
osh	18 trap RETURN [osh stdout] Expected '--\nf\n--\n--\ng\n--\nreturn-helper.sh\nprofile [x y]\n' Got '--\nf\n--\n--\ng\n--\nreturn-helper.sh\n' stdout: -- f -- -- g -- return-helper.sh stderr: osh warning: The 'RETURN' hook isn't implemented
osh-cpp	18 trap RETURN [osh-cpp stdout] Expected '--\nf\n--\n--\ng\n--\nreturn-helper.sh\nprofile [x y]\n' Got '--\nf\n--\n--\ng\n--\nreturn-helper.sh\n' stdout: -- f -- -- g -- return-helper.sh stderr: osh warning: The 'RETURN' hook isn't implemented
osh	19 Compare trap DEBUG vs. trap ERR [osh stdout] Expected 'dbg 3\ndbg 3\ndbg 3\ndbg 5\ndbg 5\ndbg 5\ndbg 7\ndbg 9\nerr 14\nerr 16\nok\n' Got 'dbg 3\ndbg 5\ndbg 5\ndbg 5\ndbg 7\ndbg 9\nerr 14\nerr 16\nok\n' stdout: dbg 3 dbg 5 dbg 5 dbg 5 dbg 7 dbg 9 err 14 err 16 ok stderr:
osh-cpp	19 Compare trap DEBUG vs. trap ERR [osh-cpp stdout] Expected 'dbg 3\ndbg 3\ndbg 3\ndbg 5\ndbg 5\ndbg 5\ndbg 7\ndbg 9\nerr 14\nerr 16\nok\n' Got 'dbg 3\ndbg 5\ndbg 5\ndbg 5\ndbg 7\ndbg 9\nerr 14\nerr 16\nok\n' stdout: dbg 3 dbg 5 dbg 5 dbg 5 dbg 7 dbg 9 err 14 err 16 ok stderr: