Run on live-booted Kernel 4.14 test day image. Same thing is happening also on my installed F27 system.
Attachments (somehow lost before):
<img alt="test-output" src="/kernel-tests/issue/raw/files/7b0864c5b388ffaee4b1039f3fc213eb993d09a7e8ff76f1cb5783bad694d883-test-output" />
<img alt="dmesg" src="/kernel-tests/issue/raw/files/11715e9d2330a0a0e734975596dd624be0a7aa167a9be4f3451a9772eff992c4-dmesg" />
<img alt="journalctrl" src="/kernel-tests/issue/raw/files/3c53d4130028102662d705be30a0f1cbc5600762738982558678472bfee542f2-journalctrl" />
<img alt="kernel-test-1512118109.log.txt" src="/kernel-tests/issue/raw/files/a89eab7a3dd5ee15511969ba24f1580fb2e3f1f01deba581a3ffade0f86aab96-kernel-test-1512118109.log.txt" /> <img alt="kernel-test-1512118262.log.txt" src="/kernel-tests/issue/raw/files/cb40b884718d640d768dda7850b14bde83763f2e78cff1dbb57534ebc2dbca4b-kernel-test-1512118262.log.txt" />
Those are intentional, if the segfaults do not occur, then we have a problem and the test fails.
Thanks for explanation, I thought it was the reason why some test were skipped. I wander if it's that obvious or nobody cared to ask about it.
Metadata Update from @ozeszty: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.