[LU-693] Sub-test failure in conf-sanity not shown in Maloo as test failure Created: 20/Sep/11 Updated: 28/May/17 Resolved: 28/May/17 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Maloo | Assignee: | WC Triage |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 5720 |
| Description |
|
This issue was created by maloo for Andreas Dilger <adilger@whamcloud.com> This issue relates to the following test suite run: https://maloo.whamcloud.com/test_sets/018c22de-e2f7-11e0-9909-52540025f9af. Sub-test 24a failed, but the test as a whole was marked as a pass. It may be a result of the test itself using "exit 10" instead of "return 10" and preventing the caller from printing the "FAILED" message? There are a couple of other tests If that is the case, we should audit the tests to avoid this and/or fix the test framework to handle it? conf-sanity.sh uses "exit" in subtests 24a, 24b, 33a, 36, but I couldn't find any other uses in the common test scripts. |