I have not seen this occur on the -aws nitro backed arm64 instances.
Giving that mcdivitt is EOL, killing off this bug.
07/09 11:08:48 DEBUG| utils:0153| [stdout] chunk-overcommit (2M: 64):
PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] alloc-instantiate-race shared
(2M: 64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] alloc-instantiate-race private
(2M: 64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] truncate_reserve_wraparound (2M:
64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] truncate_sigbus_versus_oom (2M:
64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] get_huge_pages (2M: 64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] shmoverride_linked (2M: 64):
PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] HUGETLB_SHM=yes
shmoverride_linked (2M: 64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] shmoverride_linked_static (2M:
64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] HUGETLB_SHM=yes
shmoverride_linked_static (2M: 64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] LD_PRELOAD=libhugetlbfs.so
shmoverride_unlinked (2M: 64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] LD_PRELOAD=libhugetlbfs.so
HUGETLB_SHM=yes shmoverride_unlinked (2M: 64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] quota.sh (2M: 64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] counters.sh (2M: 64): PASS
07/09 11:08:49 DEBUG| utils:0153| [stdout] mmap-gettest 10 20 (2M: 64):
PASS
07/09 11:08:49 DEBUG| utils:0153| [stdout] mmap-cow 19 20 (2M: 64): PASS
07/09 11:08:49 DEBUG| utils:0153| [stdout] set shmmax limit to 41943040
07/09 11:08:50 DEBUG| utils:0153| [stdout] shm-fork 10 10 (2M: 64): PASS
07/09 11:08:50 DEBUG| utils:0153| [stdout] set shmmax limit to 41943040
07/09 11:08:52 DEBUG| utils:0153| [stdout] shm-fork 10 20 (2M: 64): PASS
07/09 11:08:52 DEBUG| utils:0153| [stdout] set shmmax limit to 41943040
07/09 11:08:52 DEBUG| utils:0153| [stdout] shm-getraw 20 /dev/full (2M:
64): PASS
07/09 11:09:18 DEBUG| utils:0153| [stdout] fallocate_stress.sh (2M: 64):
PASS
07/09 11:09:18 DEBUG| utils:0153| [stdout] ********** TEST SUMMARY
07/09 11:09:18 DEBUG| utils:0153| [stdout] * 2M
07/09 11:09:18 DEBUG| utils:0153| [stdout] * 32-bit
64-bit
07/09 11:09:18 DEBUG| utils:0153| [stdout] * Total testcases: 0
113
07/09 11:09:18 DEBUG| utils:0153| [stdout] * Skipped: 0
0
07/09 11:09:18 DEBUG| utils:0153| [stdout] * PASS: 0
111
07/09 11:09:18 DEBUG| utils:0153| [stdout] * FAIL: 0
0
07/09 11:09:18 DEBUG| utils:0153| [stdout] * Killed by signal: 0
1
07/09 11:09:18 DEBUG| utils:0153| [stdout] * Bad configuration: 0
1
07/09 11:09:18 DEBUG| utils:0153| [stdout] * Expected FAIL: 0
0
07/09 11:09:18 DEBUG| utils:0153| [stdout] * Unexpected PASS: 0
0
07/09 11:09:18 DEBUG| utils:0153| [stdout] * Test not present: 0
0
07/09 11:09:18 DEBUG| utils:0153| [stdout] * Strange test result: 0
0
07/09 11:09:18 DEBUG| utils:0153| [stdout] **********
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: ubuntu-kernel-tests
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739560
Title:
Trusty arm64 system will hang on libhugetlbfs shmoverride_linked test
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1739560/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs