[LU-16399] Auster's results.yml should record setup/cleanup subtests Created: 14/Dec/22 Updated: 01/Jul/23 Resolved: 20/Jun/23 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.16.0 |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Charlie Olmstead | Assignee: | Alex Deiter |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Issue Links: |
|
||||
| Rank (Obsolete): | 9223372036854775807 | ||||
| Description |
|
Before and after the subtests of a suite run, auster runs a setup/cleanup 'subtest' however it is not recorded in the results.yml file which makes it confusing to users when they fail. For example: https://testing.whamcloud.com/test_sets/6c25ddb2-8f54-4bfc-b517-7d8fa10a26e0 In that session, all of ost-pools sub-tests passed but the suite is marked FAIL. After looking at the ost-pools suite log we can see that the cleanup phase failed. == ost-pools test complete, duration 3469 sec ============ 06:14:41 (1670998481) rm: cannot remove '/mnt/lustre/d70b.replay-single/onyx-80vm13.onyx.whamcloud.com': Directory not empty rm: cannot remove '/mnt/lustre/d70b.replay-single/onyx-80vm12.onyx.whamcloud.com': Directory not empty ost-pools : @@@@@@ FAIL: remove sub-test dirs failed Trace dump: = /usr/lib64/lustre/tests/test-framework.sh:6526:error() = /usr/lib64/lustre/tests/test-framework.sh:6010:check_and_cleanup_lustre() = /usr/lib64/lustre/tests/ost-pools.sh:1891:main() Dumping lctl log to /autotest/autotest-2/2022-12-14/lustre-reviews_review-dne-part-6_91178_8_65e71c9b-ceca-42ee-bf2e-b293cbbbbbb5//ost-pools..*.1670998485.log CMD: onyx-113vm8,onyx-113vm9,onyx-61vm1,onyx-80vm12.onyx.whamcloud.com,onyx-80vm13 /usr/sbin/lctl dk > /autotest/autotest-2/2022-12-14/lustre-reviews_review-dne-part-6_91178_8_65e71c9b-ceca-42ee-bf2e-b293cbbbbbb5//ost-pools..debug_log.\$(hostname -s).1670998485.log; dmesg > /autotest/autotest-2/2022-12-14/lustre-reviews_review-dne-part-6_91178_8_65e71c9b-ceca-42ee-bf2e-b293cbbbbbb5//ost-pools..dmesg.\$(hostname -s).1670998485.log
Here's another example that's more confusing because the suite log shows no indication of a failure. https://testing.whamcloud.com/test_sets/69e4c1c0-365c-4451-ba53-3305b892b0d9 |
| Comments |
| Comment by Charlie Olmstead [ 06/Jan/23 ] |
|
Another example: https://testing.whamcloud.com/test_sets/a532ea75-1451-452e-854c-57169d5d56a6 |
| Comment by Gerrit Updater [ 09/Jan/23 ] |
|
"Alex Deiter <alex.deiter@gmail.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/49582 |
| Comment by Gerrit Updater [ 20/Jun/23 ] |
|
"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/49582/ |
| Comment by Peter Jones [ 20/Jun/23 ] |
|
Landed for 2.16 |