Bash stacktrace is too conservative about what stack frames it shows

[stevekuznetsov]

In an effort to not show the internal working of the stacktrace in the stacktrace, we are a little too conservative in how we display the stack frames. This leads to unintelligible stack readouts when a failure happens in a trap.

[INFO] Dumping container logs to /tmp/openshift/conformance/logs/containers                                                                                                                                
[ERROR] PID 26302: hack/lib/cleanup.sh:74: `[[ -n "${OS_DEBUG:-}" ]]` exited with status 1.                                                                                                                
[INFO]          Stack Trace:                                                                                                                                                                               
[INFO]            1: hack/lib/cleanup.sh:74: `[[ -n "${OS_DEBUG:-}" ]]`                                                                                                                                    
[INFO]            2: test/extended/setup.sh:48: os::cleanup::dump_container_logs                                                                                                                           
[INFO]            3: test/extended/conformance.sh:1: cleanup                                                                                                                                              
[INFO]   Exiting with code 1.

See also: #11777 (comment)

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[stevekuznetsov]

Not important

/close