Catching a double fault is doomed... Don't take action.
Simplify CT_DoExecLog: it does not support affectations prior to the command, anyway.
/trunk/scripts/functions | 5 1 4 0 +----
1 file changed, 1 insertion(+), 4 deletions(-)
1.1 --- a/scripts/functions Mon Jul 14 21:51:56 2008 +0000
1.2 +++ b/scripts/functions Mon Jul 14 21:56:58 2008 +0000
1.3 @@ -3,11 +3,8 @@
1.4 # Licensed under the GPL v2. See COPYING in the root of this package
1.5
1.6 # Prepare the fault handler
1.7 -CT_IN_FAULT_HANDLER=0
1.8 CT_OnError() {
1.9 ret=$?
1.10 - [ ${CT_IN_FAULT_HANDLER} -ne 0 ] && return 0
1.11 - CT_IN_FAULT_HANDLER=1
1.12 CT_DoLog ERROR "Build failed in step '${CT_STEP_MESSAGE[${CT_STEP_COUNT}]}'"
1.13 for((step=(CT_STEP_COUNT-1); step>1; step--)); do
1.14 CT_DoLog ERROR " called in step '${CT_STEP_MESSAGE[${step}]}'"
1.15 @@ -114,7 +111,7 @@
1.16 local level="$1"
1.17 shift
1.18 CT_DoLog DEBUG "==> Executing: '${@}'"
1.19 - eval "${@}" 2>&1 |CT_DoLog "${level}"
1.20 + "${@}" 2>&1 |CT_DoLog "${level}"
1.21 }
1.22
1.23 # Tail message to be logged whatever happens