diff options
| author | Qu Wenruo <wqu@suse.com> | 2019-11-29 12:57:43 +0800 |
|---|---|---|
| committer | Eryu Guan <guaneryu@gmail.com> | 2019-12-01 23:13:03 +0800 |
| commit | 5e6b248c6668b4c1c1a0d512ba907920bfaa6eea (patch) | |
| tree | a378a5b277414f24d0b72e0fb19fe2ca7d894b4c /README | |
| parent | bdb2c8cc5f44575fee7ad4e08d173bd03676c393 (diff) | |
fstests: Allow user to keep $seqres.dmesg for all tests
Currently fstests will remove $seqres.dmesg if nothing wrong
happened. It saves some space, but sometimes it may not provide
good enough history for developers to check.
For example, some unexpected dmesg from fs, but not serious enough
to be caught by current filter.
So instead of deleting the ordinary $seqres.dmesg, provide a new
config: KEEP_DMESG, to allow user to keep the dmesg by setting it to
"yes".
The default value for it is "no", which keeps the existing behavior
by deleting ordinary dmesg.
[Eryu: change it to a "yes"/"no" switch.]
Signed-off-by: Qu Wenruo <wqu@suse.com>
Reviewed-by: Eryu Guan <guaneryu@gmail.com>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
Diffstat (limited to 'README')
| -rw-r--r-- | README | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -101,6 +101,7 @@ Preparing system for tests: using nvme drives. - set USE_KMEMLEAK=yes to scan for memory leaks in the kernel after every test, if the kernel supports kmemleak. + - set KEEP_DMESG=yes to keep dmesg log after test - or add a case to the switch in common/config assigning these variables based on the hostname of your test |