avocado-framework-tests / avocado-misc-tests

Community maintained Avocado tests repository
Other
22 stars 123 forks source link

After running pjdfstest.py in Rhel8.4 with Avocado (version: 92.0), it shows “FAIL: failed: Command 'prove -rv tests' failed”. #2173

Open Gene-Lo opened 2 years ago

Gene-Lo commented 2 years ago

After running pjdfstest.py in Rhel8.4 with Avocado (version: 92.0), it shows “FAIL: failed: Command 'prove -rv tests' failed”.

《SOL-Log》 SOL-Log

《Debug-Log》 L0470 DEBUG| [stdout] Test Summary Report L0470 DEBUG| [stdout] ------------------- L0470 DEBUG| [stdout] tests/chown/00.t (Wstat: 0 Tests: 1323 Failed: 0) L0470 DEBUG| [stdout] TODO passed: 693, 697, 708-709, 714-715, 729, 733 L0470 DEBUG| [stdout] tests/symlink/03.t (Wstat: 0 Tests: 6 Failed: 2) L0470 DEBUG| [stdout] Failed tests: 1-2 L0470 DEBUG| [stdout] tests/utimensat/09.t (Wstat: 0 Tests: 7 Failed: 2) L0470 DEBUG| [stdout] Failed tests: 4-5 L0470 DEBUG| [stdout] Files=236, Tests=8818, 176 wallclock secs ( 1.41 usr 0.14 sys + 40.15 cusr 5.84 csys = 47.54 CPU) L0470 DEBUG| [stdout] Result: FAIL

《Manual Test Log》 ※ The result of Manual-Test-Log is as same as the result of Avocado-Test-Log.

Test Summary Report

tests/chown/00.t (Wstat: 0 Tests: 1323 Failed: 0) TODO passed: 693, 697, 708-709, 714-715, 729, 733 tests/symlink/03.t (Wstat: 0 Tests: 6 Failed: 2) Failed tests: 1-2 tests/utimensat/09.t (Wstat: 0 Tests: 7 Failed: 2) Failed tests: 4-5 Files=236, Tests=8818, 176 wallclock secs ( 1.50 usr 0.24 sys + 39.78 cusr 5.95 csys = 47.47 CPU) Result: FAIL

Manual-Test-Log.txt

《Avocado Test Log》 20211111-SUT1.2-Distro-pjdfstest.zip

《Configuration》 [Kernel] 4.18.0-305.25.1.el8_4.ppc64le

[FW Config] BMC: op940.22.mih-1-0-g41157d8d2e Pnor: OP9_v2.4.1-4.31-prod

[HW Config] CPU DD2.3 20 core 2 Micron Technology (72ASS8G72PSZ-2S6G1) 64GiB x32 SAMSUNG PM985 (MZ1LB960HAJQ-00007) 960GB M.2 x1 PSU ACBEL 2000w 2 Slot1: Mellanox 2-PORT EDR 100Gb IB CONNECTX-5 GEN4 PCIe x16 CAPI CAPABLE LP ADAPTER Slot2: Marvell 2-PORT E'NET (2X10 10Gb), PCIe Gen 2 X8/SHORT LP CAPABLE (SHINER 10GBase-T) Slot3: Mellanox 2-PORT 10Gb NIC&ROCE ConnectX-4Lx SR/Cu PCIe 3.0 LP CAPABLE ADAPTER Slot4: Marvell QUAD E'NET (2X1 + 2X10 10Gb), PCIe Gen 2 X8/SHORT LP CAPABLE (SHINER SFP+ SR COPPER) Slot5: Broadcom (LSI) MegaRAID 9361-8i SAS3 Controller w/ 8 internal ports Slot6: Mellanox 2-PORT 100Gb ROCE EN CONNECTX-5 GEN4 PCIe x16 LP CAPABLE ADAPTER Slot7: Nvidia T4 Accelerator 16GB PCIe3 x16 LP Slot8: Mellanox 2-PORT 25/10Gb NIC&ROCE SR/Cu PCIe 3.0 (25/10Gb EVERGLADES EN) Slot9: Broadcom 5719 QP 1G (1G/100M/10M) Network Interface Card PCIe x4 LP Slot10: Broadcom 9305-16i SAS/SATA HBA PCIe Gen3 x8 LP 0VN497 - Seagate Skybolt - HDD 2400GB SAS 3 00VN629 - Micron 5100 PRO - SSD 3840GB SATA 4 00VN329 - Samsung PM1643 - SSD 3840GB SAS *9

disgoel commented 1 year ago

@PraveenPenguin here we see two different failures with symlink and utimensat tests.

for symlink test failure closed as will not fix since its failing from long time and expected behaviour as per below comment.

It seems it is in expected behaviour of XFS filesystem. I could reproduce in older and latest upstream kernel, also based on some of the XFS kernel comments, this looks expected. Thus we should ignore this failure on XFS and close this BZ.

for utimensat test failure, based on below analysis from Dev we need to see if we can enhance our script with this.

PraveenPenguin commented 1 year ago

@disgoel thanks , so closing this issue