[LU-14067] sanity test_400a: gcc segmentation fault on arm

• Status: Resolved
• Project: Lustre
• Fix Version/s: Lustre 2.16.0
• Type: Bug
• Priority: Minor
• Reporter: Maloo
• Assignee: Xinliang Liu
• Resolution: Fixed
• Labels: arm
• Severity: 3

Description

This issue was created by maloo for John Hammond <[e-mail]>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/956131b0-07f6-4348-9f34-74059e64b7c5

test_400a failed with the following error:

client api broken

== sanity test 400a: Lustre client api program can compile and link ================================== 19:29:24 (1603394964)
during IPA pass: visibility
/usr/lib64/lustre/tests/clientapi/simple_test.c:39:1: internal compiler error: Segmentation fault
 }
 ^

Same for 400b.

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity test_400a - client api broken

Comments

[Gerrit Updater]

John L. Hammond ([e-mail]) uploaded a new patch: https://review.whamcloud.com/40365
Subject: LU-14067 test: skip sanity 400ab on aarch64
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 62cefecebc129758763b4a697f302581c58bf0db

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/40365/
Subject: LU-14067 test: skip compile tests on aarch64
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 61f996b07f040376049522c9e8ee4469274607ce

[James Nunez (Inactive)]

Note that patch 40365 adds sanity test_400a and test_400b to the ALWAYS_EXCEPT list. It also adds sanity-lnet test_300 to the ALWAYS_EXCEPT list.

[Andreas Dilger]

We shouldn't have tests in ALWAYS_EXCEPT for closed tickets, since this is how we track test failures that are ignored for convenience but not actually resolved.

If this is expected to be a temporary issue, then the ticket should remain open until the problem is fixed.

If this is a permanent situation (i.e. the subtest doesn't make sense for this configuration) then this should be changed to a check and skip in the subtest itself, and the always_except label on this ticket can be removed before it is resolved.

[Andreas Dilger]

The sanity-lnet ALWAYS_EXCEPT for test_300 also has a misleading comment "skip the grant tests for ARM until they are fixed", but the that subtest has nothing to do with grants.

[James A Simmons]

Looking at the failures it looks like the development tools are install incorrectly for your images.

[Xinliang Liu]

I can't see this issue on the CI or my local environment for months on master branch.

[Andreas Dilger]

xinliang the always_except label means that the test is not being run (always skip because it is added to ALWAYS_EXCEPT), so no error would be seen. If it is passing when run manually, a patch can be pushed to remove the test from ALWAYS_EXCEPT in sanity.sh and it should hopefully pass:

       # bug number:    LU-14067 LU-14067
        ALWAYS_EXCEPT+=" 400a     400b"

If the patch passes, then it can be reviewed and landed and the tests will be run automatically again.

[James A Simmons]

This works locally for me as well. The development environment is broke on the whamcloud VMs.  Maybe it works now for whamcloud? 

[Xinliang Liu]

OK, Andreas will send a patch to remove the test from ALWAYS_EXCEPT  after LU-11596 patch landed or it will cause merge conflict.

[Gerrit Updater]

"James Simmons <[e-mail]>" uploaded a new patch: https://review.whamcloud.com/46409
Subject: LU-14067 tests: re-enable gcc compile test for PPC + ARM
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 2c93f9887d26efdd1056d47cb6f83a7e8a39bffe

[Gerrit Updater]

"Oleg Drokin <[e-mail]>" merged in patch https://review.whamcloud.com/46409/
Subject: LU-14067 tests: re-enable gcc compile test for PPC + ARM
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 5f3d2ff63b3eb67e55fa83123b236c820c347749

[Peter Jones]

Landed for 2.16