Browse code

hack: add more debugging to understand exit codepath

Signed-off-by: Tibor Vass <tibor@docker.com>

Tibor Vass authored on 2020/05/27 23:29:00
Showing 2 changed files
... ...
@@ -286,6 +286,7 @@ pipeline {
286 286
                                 sh '''#!/bin/bash
287 287
                                 # bash is needed so 'jobs -p' works properly
288 288
                                 # it also accepts setting inline envvars for functions without explicitly exporting
289
+                                set -x
289 290
 
290 291
                                 run_tests() {
291 292
                                         [ -n "$TESTDEBUG" ] && rm= || rm=--rm;
... ...
@@ -335,7 +336,6 @@ pipeline {
335 335
                                 # integration-cli second set
336 336
                                 TEST_INTEGRATION_DEST=3 CONTAINER_NAME=${CONTAINER_NAME}-3 TEST_SKIP_INTEGRATION=1 TESTFLAGS="-test.run Test(DockerSwarmSuite|DockerDaemonSuite|DockerExternalVolumeSuite)/" run_tests &
337 337
 
338
-                                set +x
339 338
                                 c=0
340 339
                                 for job in $(jobs -p); do
341 340
                                         wait ${job} || c=$?
... ...
@@ -22,6 +22,8 @@ fi
22 22
 	cleanup_test_suite_binaries
23 23
 	error_on_leaked_containerd_shims
24 24
 
25
+	echo exiting test-integration
26
+	set -x
25 27
 	exit ${testexit}
26 28
 
27 29
 ) 2>&1 | tee -a "$DEST/test.log"