a8dbd281f7
Now, by execute `make test-run` in tests/, kexec-tools sanity tests will be performed using VMs. There are currently 3 test cases, for local kdump, nfs kdump and ssh kdump. For each test VM, the selftest framework will create a snapshot layer, do setup as required by the test case, this ensure each test runs in a clean VM. This framework will install a custom systemd service that starts when system have finished booting, and the service will do basic routine (fetch and set boot counter, etc..), then call the test case which is installed in /kexec-kdump-test/test.sh in VM. Each VM will have two serial consoles, one for ordinary console usage, one for the test communication and log. The test script will watch the second test console to know the test status. The test cases are located in tests/scripts/testcases, documents about the test cases structure will be provided in following commits. Signed-off-by: Kairui Song <kasong@redhat.com> Acked-by: Dave Young <dyoung@redhat.com>
33 lines
525 B
Bash
Executable File
33 lines
525 B
Bash
Executable File
on_build() {
|
|
:
|
|
}
|
|
|
|
on_test() {
|
|
local boot_count=$(get_test_boot_count)
|
|
|
|
if [ $boot_count -eq 1 ]; then
|
|
cat << EOF > /etc/kdump.conf
|
|
path /var/crash
|
|
core_collector makedumpfile -l --message-level 1 -d 31
|
|
EOF
|
|
kdumpctl start || test_failed "Failed to start kdump"
|
|
|
|
sync
|
|
|
|
echo 1 > /proc/sys/kernel/sysrq
|
|
echo c > /proc/sysrq-trigger
|
|
|
|
elif [ $boot_count -eq 2 ]; then
|
|
|
|
if has_valid_vmcore_dir /var/crash; then
|
|
test_passed
|
|
else
|
|
test_failed
|
|
fi
|
|
|
|
shutdown -h 0
|
|
else
|
|
test_failed "Unexpected reboot"
|
|
fi
|
|
}
|