62578ace21
For the log entry that has multiple lines, "makedumpfile --dump-dmesg" would indent the remaining lines while vmcore-dmesg doesn't. For example, vmcore-dmesg.txt and vmcore-dmesg.txt.2 are the outputs of vmcore-dmesg and "makedumpfile --dump-dmesg" respectively, ``` diff -u vmcore-dmesg.txt vmcore-dmesg.txt.2 --- vmcore-dmesg.txt 2021-03-28 22:13:09.986000000 -0400 +++ vmcore-dmesg.txt.2 2021-03-28 22:13:39.920106131 -0400 @@ -397,9 +397,9 @@ [ 1.710742] vc vcsa: hash matches [ 1.711938] RAS: Correctable Errors collector initialized. [ 1.713736] Unstable clock detected, switching default tracing clock to "global" -If you want to keep using the local clock, then add: - "trace_clock=local" -on the kernel command line + If you want to keep using the local clock, then add: + "trace_clock=local" + on the kernel command line [ 1.750539] ata1.01: NODEV after polling detection [ 1.750973] ata1.00: ATA-7: QEMU HARDDISK, 2.5+, max UDMA/100 [ 1.752885] ata1.00: 8388608 sectors, multi 16: LBA48 ``` Quite often, all three tests could fail because of the above difference. So let's ignore all the spaces. This patch could fix bz1952299 [1]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1952299 Signed-off-by: Coiby Xu <coxu@redhat.com> Acked-by: Kairui Song <kasong@redhat.com> |
||
---|---|---|
.. | ||
build-scripts | ||
kexec-kdump-test | ||
testcases | ||
build-image.sh | ||
copy-from-image.sh | ||
image-init-lib.sh | ||
run-qemu | ||
run-test.sh | ||
spawn-image-shell.sh | ||
test-lib.sh |