[LU-14848] Lustre test suite's non-zero rc is not propagated to auster Created: 13/Jul/21 Updated: 14/Jul/21 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.14.0, Lustre 2.12.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Xiaolin Zang | Assignee: | WC Triage |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | tests | ||
| Environment: |
The issue likely exists in some of the other versions, too. |
||
| Epic/Theme: | test |
| Severity: | 3 |
| Project: | Test Infrastructure |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
Without the following patch, the rc from a test suite is not propagated to auster. As a result, auster always declares success, making it necessary to check results.yml to determine the outcome of the tests.
--- a/lustre/tests/auster
+++ b/lustre/tests/auster
@@ -210,6 +210,8 @@ run_suite() {
[[ ! -f $TF_SKIP ]] || rm -f $TF_SKIP
reset_lustre
+
+ return $rc
}
run_suite_logged() {
@@ -227,10 +229,13 @@ run_suite_logged() {
local log_name=${suite_name}.suite_log.$(hostname -s).log
if $verbose; then
run_suite $suite_name $suite_script 2>&1 |tee $LOGDIR/$log_name
+ local rc=${PIPESTATUS[0]}
else
run_suite $suite_name $suite_script > $LOGDIR/$log_name 2>&1
+ local rc=$?
fi
+ return $rc
}
|