BTW, the story is quite different when running this remotely from our jenkins server with command: ~/kernel-testing/remote ubuntu@ms10-35-mcdivittb0-kernel --kernel-test-list=ubuntu_stress_smoke_test
It will stuck at the file-ioctl test: 06:46:33 DEBUG| [stdout] fifo PASSED 06:46:33 DEBUG| [stdout] file-ioctl STARTING Reproduce rate: 4/4 Mar 13 06:46:28 ms10-35-mcdivittB0-kernel stress-ng: info: [30165] dispatching hogs: 4 fifo Mar 13 06:46:28 ms10-35-mcdivittB0-kernel stress-ng: info: [30165] cache allocate: using built-in defaults as unable to determine cache details Mar 13 06:46:33 ms10-35-mcdivittB0-kernel stress-ng: info: [30165] successful run completed in 5.00s Mar 13 06:46:33 ms10-35-mcdivittB0-kernel stress-ng: invoked with './stress-ng -v -t 5 --file-ioctl 4 --ignite-cpu --syslog --verbose --verify --oomable' by user 0 Mar 13 06:46:33 ms10-35-mcdivittB0-kernel stress-ng: system: 'ms10-35-mcdivittB0-kernel' Linux 4.13.0-37-generic #42-Ubuntu SMP Wed Mar 7 14:13:33 UTC 2018 aarch64 Mar 13 06:46:33 ms10-35-mcdivittB0-kernel stress-ng: memory (MB): total 64429.68, free 62156.75, shared 0.63, buffer 297.27, swap 9215.99, free swap 9215.99 Mar 13 06:46:33 ms10-35-mcdivittB0-kernel stress-ng: info: [30196] dispatching hogs: 4 file-ioctl Mar 13 06:46:33 ms10-35-mcdivittB0-kernel stress-ng: info: [30196] cache allocate: using built-in defaults as unable to determine cache details -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755358 Title: enosys test in ubuntu_stress_smoke test will terminates the user session on Artful ARM64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755358/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
