diff options
| author | Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> | 2020-08-11 08:54:04 +0900 |
|---|---|---|
| committer | Dmitry Vyukov <dvyukov@google.com> | 2020-08-12 18:19:04 +0200 |
| commit | bc15f7dbbc1c6e2042a7115b3fdacc0ada8c35e7 (patch) | |
| tree | cbfe881391bf34d8cbbe7b6b08840ff6d83b29e0 /sys/linux/dev_watch_queue_ppc64le.const | |
| parent | 1bf9153625ea4fb8788b2181a94e891b84cb283b (diff) | |
executor/linux: dump mount information when failed to open kcov file
There are many "lost connection to test machine (5)" reports where the
testing terminated due to ENOENT upon open("/sys/kernel/debug/kcov").
Since some testcase might be unintendedly modifying mount information,
let's start from checking whether/how mount is broken.
This commit might be reverted after the cause is identified and fixed.
Diffstat (limited to 'sys/linux/dev_watch_queue_ppc64le.const')
0 files changed, 0 insertions, 0 deletions