From 06a1cdb2cfd32ba8de8bec3ca54d604a26e141da Mon Sep 17 00:00:00 2001 From: Nigel Babu Date: Mon, 13 Aug 2018 07:04:58 +0530 Subject: Fix the return value for lcov The status was being taken for the mv command rather than the test run. When regression passes, we don't actually get any logs, so this would actually fail causing the entire run to be marked as failed Change-Id: Ia9fa731f7cc66c1c47481ebc47ffa2bc55d7c4ea --- build-gluster-org/scripts/lcov.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'build-gluster-org/scripts/lcov.sh') diff --git a/build-gluster-org/scripts/lcov.sh b/build-gluster-org/scripts/lcov.sh index 5f807b2..575559a 100644 --- a/build-gluster-org/scripts/lcov.sh +++ b/build-gluster-org/scripts/lcov.sh @@ -38,13 +38,13 @@ set +e echo "Running the regression test" sudo -E bash /opt/qa/regression.sh -c -t 300 -mv glusterfs-logs.tgz regression-glusterfs-logs.tgz REGRESSION_STATUS=$? +mv glusterfs-logs.tgz regression-glusterfs-logs.tgz echo "Running the smoke tests" sudo -E bash /opt/qa/smoke.sh -c -mv glusterfs-logs.tgz smoke-glusterfs-logs.tgz SMOKE_STATUS=$? +mv glusterfs-logs.tgz smoke-glusterfs-logs.tgz echo "Capturing the line coverage in the .info file" lcov -c -d . -o coverage/glusterfs-lcov.info -- cgit