From: Haiwei Li <lihaiwei.kernel@gmail.com>
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: [kvm-unit-tests] ./run_tests.sh error?
Date: Wed, 25 Dec 2019 13:38:53 +0800 [thread overview]
Message-ID: <46d9112f-1520-0d81-e109-015b7962b1a7@gmail.com> (raw)
When i run ./run_tests.sh, i get output like this:
SKIP apic-split (qemu: could not open kernel file '_NO_FILE_4Uhere_': No
such file or directory)
SKIP ioapic-split (qemu: could not open kernel file '_NO_FILE_4Uhere_':
No such file or directory)
SKIP apic (qemu: could not open kernel file '_NO_FILE_4Uhere_': No such
file or directory)
......
Seems like the code below causing of "SKIP" above.
file: scripts/runtime.bash
# We assume that QEMU is going to work if it tried to load the kernel
premature_failure()
{
local log="$(eval $(get_cmdline _NO_FILE_4Uhere_) 2>&1)"
echo "$log" | grep "_NO_FILE_4Uhere_" |
grep -q -e "could not load kernel" -e "error loading" &&
return 1
RUNTIME_log_stderr <<< "$log"
echo "$log"
return 0
}
get_cmdline()
{
local kernel=$1
echo "TESTNAME=$testname TIMEOUT=$timeout ACCEL=$accel
$RUNTIME_arch_run $kernel -smp $smp $opts"
}
function run()
{
...
last_line=$(premature_failure > >(tail -1)) && {
print_result "SKIP" $testname "" "$last_line"
return 77
}
...
}
Is that proper? What can i do?
What i did:
1. git clone git://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
2. cd kvm-unit-tests/
3. git checkout -b next origin/next
4. ./configure
5. make
6. ./run_test.sh
Related config file:
# cat config.mak
SRCDIR=/data/kvm-unit-tests
PREFIX=/usr/local
HOST=x86_64
ARCH=x86_64
ARCH_NAME=x86_64
PROCESSOR=x86_64
CC=gcc
CXX=g++
LD=ld
OBJCOPY=objcopy
OBJDUMP=objdump
AR=ar
ADDR2LINE=addr2line
API=yes
TEST_DIR=x86
FIRMWARE=
ENDIAN=
PRETTY_PRINT_STACKS=yes
ENVIRON_DEFAULT=yes
ERRATATXT=errata.txt
U32_LONG_FMT=
next reply other threads:[~2019-12-25 5:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 5:38 Haiwei Li [this message]
2019-12-27 12:46 ` [kvm-unit-tests] ./run_tests.sh error? Andrew Jones
2019-12-28 4:03 ` Haiwei Li
2020-01-07 13:22 ` Thomas Huth
2020-01-07 13:29 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46d9112f-1520-0d81-e109-015b7962b1a7@gmail.com \
--to=lihaiwei.kernel@gmail.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox