[LU-12760] sanity test_161d incorrect use of stack_trap

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.13.0, Lustre 2.12.4
• Affects Version/s: Lustre 2.13.0
• Severity: 3
• Assignee: Andreas Dilger
• Reporter: Oleg Drokin

Description

stack_trap uses two arguments, the second being the signal to trap.

Yes test_161d has this:

        stack_trap "rm -f $tempfile"

the end result is this:

== sanity test 161d: create with concurrent .lustre/fid access ======================================= 07:42:56 (1568374976)
mdd.lustre-MDT0000.changelog_mask=+hsm
Registered 1 changelog users: 'cl13'
fail_loc=0x8000140c
fail_val=5
  PID TTY          TIME CMD
  490 pts/0    00:00:00 bash
/home/green/git/lustre-release/lustre/tests/test-framework.sh: line 6086: trap: : invalid signal specification
/home/green/git/lustre-release/lustre/tests/test-framework.sh: line 6093: trap: : invalid signal specification
/home/green/git/lustre-release/lustre/tests/test-framework.sh: line 6094: trap: : invalid signal specification
/home/green/git/lustre-release/lustre/tests/test-framework.sh: line 6095: trap: : invalid signal specification
/home/green/git/lustre-release/lustre/tests/test-framework.sh: eval: line 6099: unexpected EOF while looking for matching `''
/home/green/git/lustre-release/lustre/tests/test-framework.sh: eval: line 6100: syntax error: unexpected end of file

sohuld add EXIT to the the end of stack_trap call.