Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
Impala 2.7.0
Description
This bug is about the fact the data loading job can have a test fail, not produce any data load snapshot artifacts, and still be green. This bug is not about the failing test itself (separate bug).
http://sandbox.jenkins.cloudera.com/job/impala-asf-master-core-data-load/29/
There's not all that much to talk about. A kudu-related backend test failed here:
22:55:09 99% tests passed, 1 tests failed out of 78 22:55:09 22:55:09 The following tests FAILED: 22:55:09 13 - kudu-scan-node-test (OTHER_FAULT) 22:55:09 Errors while running CTest 22:55:09 make: *** [test] Error 8
Much further down, we see logic that the build failed, but then didn't?
01:52:10 + [[ 1 -ne 0 ]] 01:52:10 + echo Build Failed. 01:52:10 Build Failed. 01:52:10 + touch /data/jenkins/workspace/impala-asf-master-core-data-load/build-failed.txt 01:52:10 + exit 0 01:52:10 + ret=0 01:52:10 + JOB_UUID=impala-asf-master-core-data-load-29 01:52:10 + CLUSTER_LOG_TARBALL=cluster_logs-impala-asf-master-core-data-load-29.tar.gz 01:52:10 + IMPALA_HOME=/data/jenkins/workspace/impala-asf-master-core-data-load/repos/Impala 01:52:10 + set +e 01:52:10 + rm -rf /data/jenkins/workspace/impala-asf-master-core-data-load/repos/Impala/cluster_logs_static 01:52:10 + mkdir -p /data/jenkins/workspace/impala-asf-master-core-data-load/repos/Impala/cluster_logs_static 01:52:10 + cp -r -L /data/jenkins/workspace/impala-asf-master-core-data-load/repos/Impala/cluster_logs /data/jenkins/workspace/impala-asf-master-core-data-load/repos/Impala/cluster_logs_static 01:52:10 cp: cannot stat `/data/jenkins/workspace/impala-asf-master-core-data-load/repos/Impala/cluster_logs': No such file or directory 01:52:10 + tar -czf /data/jenkins/workspace/impala-asf-master-core-data-load/cluster_logs-impala-asf-master-core-data-load-29.tar.gz /data/jenkins/workspace/impala-asf-master-core-data-load/repos/Impala/cluster_logs_static 01:52:10 tar: Removing leading `/' from member names 01:52:10 + set -e 01:52:10 + echo finished 01:52:10 finished 01:52:10 + exit 0 01:52:10 [File exists] check if file exists [build-failed.txt] 01:52:10 Run condition [File exists] enabling perform for step [BuilderChain] 01:52:10 Triggering projects: send-email-from-jenkins 01:52:10 Archiving artifacts 01:52:15 WARN: No artifacts found that match the file pattern "hive_impala_*.txt,testdata/test-warehouse-SNAPSHOT/*,**/logs-*.tar.gz". Configuration error? 01:52:18 WARN: ‘hive_impala_*.txt’ doesn’t match anything 01:52:18 Recording test results 01:52:21 01:52:21 Deleting project workspace... 01:52:21 done 01:52:21 01:52:21 Finished: SUCCESS
Things to fix:
1. The failed kudu test should have resulted in a red build
2. The inability to generate artifacts should have resulted in a red build, regardless of failure of the kudu test