On Tue, Dec 03, 2024 at 10:21:50AM +0100, Philippe Mathieu-Daudé wrote:
> Since commit 6f6e1698a68 ("vl: configure accelerators from -accel
> options") we prefer the '-accel bar' command line option.
>
> Replace '-machine foo,accel=bar' -> '-
Since commit 6f6e1698a68 ("vl: configure accelerators from -accel
options") we prefer the '-accel bar' command line option.
Replace '-machine foo,accel=bar' -> '-machine foo -accel bar' in
the device-crash-test script.
Signed-off-by: Philippe Mathie
by disabling
the up-to-date check via NINJA=":".
Fixes: 1d8cf47e5b ("tests: run 'device-crash-test' from tests/venv")
Signed-off-by: Thomas Huth
Message-Id: <20230414145845.456145-2-th...@redhat.com>
Signed-off-by: Alex Bennée
Message-Id: <20230424092249
From: Thomas Huth
We're currently facing the problem that the device-crash-test script
runs twice as long in the CI when a runner supports KVM - which sometimes
results in a timeout of the CI job. To get a more deterministic runtime
here, add an option to the script that allows to run it
by disabling
the up-to-date check via NINJA=":".
Fixes: 1d8cf47e5b ("tests: run 'device-crash-test' from tests/venv")
Signed-off-by: Thomas Huth
Message-Id: <20230414145845.456145-2-th...@redhat.com>
Signed-off-by: Alex Bennée
Message-Id: <20230424092249
From: Thomas Huth
We're currently facing the problem that the device-crash-test script
runs twice as long in the CI when a runner supports KVM - which sometimes
results in a timeout of the CI job. To get a more deterministic runtime
here, add an option to the script that allows to run it
From: Thomas Huth
We're currently facing the problem that the device-crash-test script
runs twice as long in the CI when a runner supports KVM - which sometimes
results in a timeout of the CI job. To get a more deterministic runtime
here, add an option to the script that allows to run it
by disabling
the up-to-date check via NINJA=":".
Fixes: 1d8cf47e5b ("tests: run 'device-crash-test' from tests/venv")
Signed-off-by: Thomas Huth
Message-Id: <20230414145845.456145-2-th...@redhat.com>
Signed-off-by: Alex Bennée
Message-Id: <20230424092249
by disabling
the up-to-date check via NINJA=":".
Fixes: 1d8cf47e5b ("tests: run 'device-crash-test' from tests/venv")
Signed-off-by: Thomas Huth
Message-Id: <20230414145845.456145-2-th...@redhat.com>
Signed-off-by: Alex Bennée
---
.gitlab-ci.d/buildtest.ym
From: Thomas Huth
We're currently facing the problem that the device-crash-test script
runs twice as long in the CI when a runner supports KVM - which sometimes
results in a timeout of the CI job. To get a more deterministic runtime
here, add an option to the script that allows to run it
On 17/4/23 15:43, Alex Bennée wrote:
From: Thomas Huth
We're currently facing the problem that the device-crash-test script
runs twice as long in the CI when a runner supports KVM - which sometimes
results in a timeout of the CI job. To get a more deterministic runtime
here, add an opti
by disabling
the up-to-date check via NINJA=":".
Fixes: 1d8cf47e5b ("tests: run 'device-crash-test' from tests/venv")
Signed-off-by: Thomas Huth
Message-Id: <20230414145845.456145-2-th...@redhat.com>
Signed-off-by: Alex Bennée
---
.gitlab-ci.d/buildtest.ym
From: Thomas Huth
We're currently facing the problem that the device-crash-test script
runs twice as long in the CI when a runner supports KVM - which sometimes
results in a timeout of the CI job. To get a more deterministic runtime
here, add an option to the script that allows to run it
Thomas Huth writes:
> Improve the runtime of the device-crash-test jobs by avoiding
> to run "configure" again and by forcing to test with TCG only
> (instead of testing twice, with TCG and KVM).
Queued to testing/next, thanks.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
up-to-date check via NINJA=":".
Fixes: 1d8cf47e5b ("tests: run 'device-crash-test' from tests/venv")
Signed-off-by: Thomas Huth
---
.gitlab-ci.d/buildtest.yml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/.gitlab-ci.d/buildtest.yml b/.gitl
Improve the runtime of the device-crash-test jobs by avoiding
to run "configure" again and by forcing to test with TCG only
(instead of testing twice, with TCG and KVM).
Thomas Huth (2):
gitlab-ci: Avoid to re-run "configure" in the device-crash-test jobs
scripts/devi
We're currently facing the problem that the device-crash-test script
runs twice as long in the CI when a runner supports KVM - which sometimes
results in a timeout of the CI job. To get a more deterministic runtime
here, add an option to the script that allows to run it with TCG only.
Report
From: John Snow
Remove the sys.path hacking from device-crash-test, and add in a little
user-friendly message for anyone who was used to running this script
directly from the source tree.
Modify the GitLab job recipes to create the tests/venv first, then run
device-crash-test from that venv
On Thu, May 26, 2022, 8:14 AM Paolo Bonzini wrote:
> On 5/26/22 02:09, John Snow wrote:
> > Remove the sys.path hacking from device-crash-test, and add in a little
> > user-friendly message for anyone who was used to running this script
> > directly from the source tre
On 5/26/22 02:09, John Snow wrote:
Remove the sys.path hacking from device-crash-test, and add in a little
user-friendly message for anyone who was used to running this script
directly from the source tree.
Modify the GitLab job recipes to create the tests/venv first, then run
device-crash-test
Remove the sys.path hacking from device-crash-test, and add in a little
user-friendly message for anyone who was used to running this script
directly from the source tree.
Modify the GitLab job recipes to create the tests/venv first, then run
device-crash-test from that venv.
Signed-off-by: John
scripts/device-crash-test | 1 +
1 file changed, 1 insertion(+)
diff --git a/scripts/device-crash-test b/scripts/device-crash-test
index 7fbd99158b..52bd3d8f71 100755
--- a/scripts/device-crash-test
+++ b/scripts/device-crash-test
@@ -93,6 +93,7 @@ ERROR_RULE_LIST = [
{'device':&
The device-crash-test script has been quite neglected in the past,
so that it bit-rot quite often. Let's add CI jobs that run this
script for at least some targets, so that this script does not
regress that easily anymore.
Message-Id: <20211126162724.1162049-1-th...@redhat.com>
On 29/11/2021 11.07, Daniel P. Berrangé wrote:
On Fri, Nov 26, 2021 at 05:27:24PM +0100, Thomas Huth wrote:
The device-crash-test script has been quite neglected in the past,
so that it bit-rot quite often. Let's add CI jobs that run this
script for at least some targets, so that this s
On Fri, Nov 26, 2021 at 05:27:24PM +0100, Thomas Huth wrote:
> The device-crash-test script has been quite neglected in the past,
> so that it bit-rot quite often. Let's add CI jobs that run this
> script for at least some targets, so that this script does not
> regress th
On 11/26/21 17:27, Thomas Huth wrote:
> The device-crash-test script has been quite neglected in the past,
> so that it bit-rot quite often. Let's add CI jobs that run this
> script for at least some targets, so that this script does not
> regress that easily anymore.
>
>
The device-crash-test script has been quite neglected in the past,
so that it bit-rot quite often. Let's add CI jobs that run this
script for at least some targets, so that this script does not
regress that easily anymore.
Signed-off-by: Thomas Huth
---
.gitlab-ci.d/buildtest.yml
Despite all the previous fixes, it's still possible for
device-crash-test to wedge itself in the case that QEMU terminates *so
quickly* that it doesn't even begin a connection attempt to our QMP
client. Python will just joyfully wait ad infinitum for a connection
that will now never ar
Despite all the previous fixes, it's still possible for
device-crash-test to wedge itself in the case that QEMU terminates *so
quickly* that it doesn't even begin a connection attempt to our QMP
client. Python will just joyfully wait ad infinitum for a connection
that will now never ar
On Thu, Nov 18, 2021 at 1:31 PM Philippe Mathieu-Daudé
wrote:
> On 11/18/21 18:55, John Snow wrote:
> > I finally squashed all of the bugs and got a clean run of
> > device-crash-test with a full build of QEMU, over 182,000 individual
> > test cases.
> >
> > Here
On 11/18/21 18:55, John Snow wrote:
> I finally squashed all of the bugs and got a clean run of
> device-crash-test with a full build of QEMU, over 182,000 individual
> test cases.
>
> Here's all of the legitimate failures I saw:
>
> CRITICAL: failed: binary=./qe
I finally squashed all of the bugs and got a clean run of device-crash-test
with a full build of QEMU, over 182,000 individual test cases.
Here's all of the legitimate failures I saw:
CRITICAL: failed: binary=./qemu-system-x86_64 accel=kvm machine=none
device=sgx-epc
CRITICAL: cmdline: .
: 2021143719.2162525-6-js...@redhat.com
Signed-off-by: John Snow
---
scripts/device-crash-test | 21 ++---
1 file changed, 18 insertions(+), 3 deletions(-)
diff --git a/scripts/device-crash-test b/scripts/device-crash-test
index 49bcd61b4f..3db0ffe5b8 100755
--- a/scripts/device-crash-test
+++ b
uth
Message-id: 2021143719.2162525-5-js...@redhat.com
Signed-off-by: John Snow
---
scripts/device-crash-test | 6 ++
1 file changed, 6 insertions(+)
diff --git a/scripts/device-crash-test b/scripts/device-crash-test
index d91e8616ef..49bcd61b4f 100755
--- a/scripts/device-crash-test
+++ b/scripts/de
ruptError and a few other important ones are
BaseExceptions, so this does the same thing with less code.
Signed-off-by: John Snow
Reported-by: Thomas Huth
Tested-by: Thomas Huth
Message-id: 2021143719.2162525-4-js...@redhat.com
Signed-off-by: John Snow
---
scripts/device-crash-test | 8 +
spit out the 'No bus found'
messages in their backtrace), but these other problems have now
fortunately been tackled by John Snow, so we certainly don't need
this duplicated entry here anymore.
Signed-off-by: Thomas Huth
---
scripts/device-crash-test | 1 -
1 file changed, 1 de
On 11/11/2021 15.37, John Snow wrote:
When I switched machine.py over to using AQMP, I caused a regression in
device-crash-test that caused many spurious errors to be printed during
the test, obscuring real test failure cases.
This series fixes the vast majority of false positives, though there
When I switched machine.py over to using AQMP, I caused a regression in
device-crash-test that caused many spurious errors to be printed during
the test, obscuring real test failure cases.
This series fixes the vast majority of false positives, though there is
one remaining bug in machine.py
These errors are expected, so they shouldn't clog up terminal output. In
the event that they're *not* expected, we'll be seeing an awful lot more
output concerning the nature of the failure.
Reported-by: Thomas Huth
Signed-off-by: John Snow
---
scripts/device-crash-test | 6
ruptError and a few other important ones are
BaseExceptions, so this does the same thing with less code.
Signed-off-by: John Snow
---
scripts/device-crash-test | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/scripts/device-crash-test b/scripts/device-crash-test
i
Generally, the traceback for a connection failure is uninteresting and
all we need to know is that the connection attempt failed.
Reduce the verbosity in these cases, except when debugging.
Signed-off-by: John Snow
---
scripts/device-crash-test | 21 ++---
1 file changed, 18
Recent QEMU versions now sometimes exit cleanly with an error message
that a bus is not available for a specified device. Don't flag those
as an error in the device-crash-test script.
Message-Id: <20210323164718.1393792-1-th...@redhat.com>
Acked-by: John Snow
Signed-off-by:
On 3/23/21 12:47 PM, Thomas Huth wrote:
Recent QEMU versions now sometimes exit cleanly with an error message
that a bus is not available for a specified device. Don't flag those
as an error in the device-crash-test script.
Signed-off-by: Thomas Huth
---
scripts/device-crash-test | 1
Recent QEMU versions now sometimes exit cleanly with an error message
that a bus is not available for a specified device. Don't flag those
as an error in the device-crash-test script.
Signed-off-by: Thomas Huth
---
scripts/device-crash-test | 1 +
1 file changed, 1 insertion(+)
diff --
t;
>> [*] https://github.com/conscious-lang/conscious-lang-docs/blob/main/faq.md
>>
>> Reviewed-by: Daniel P. Berrangé
>> Signed-off-by: Philippe Mathieu-Daudé
>> ---
>> scripts/device-crash-test | 30 +++---
>> 1 file changed, 15 in
main/faq.md
>
> Reviewed-by: Daniel P. Berrangé
> Signed-off-by: Philippe Mathieu-Daudé
> ---
> scripts/device-crash-test | 30 +++---
> 1 file changed, 15 insertions(+), 15 deletions(-)
>
> diff --git a/scripts/device-crash-test b/scripts/device
Replace "whitelist" in the device-crash-test script with
"rule list".
I'm using "rule list" instead of "allow list" or "pass list"
because the list is not used only for expected/allowed errors.
It also contain rules specifying which errors s
by: Philippe Mathieu-Daudé
---
scripts/device-crash-test | 30 +++---
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/scripts/device-crash-test b/scripts/device-crash-test
index 04118669ba7..6812de42f8c 100755
--- a/scripts/device-crash-test
+++ b/scrip
/conscious-lang/conscious-lang-docs/blob/main/faq.md
>
> Signed-off-by: Philippe Mathieu-Daudé
> ---
> scripts/device-crash-test | 30 +++---
> 1 file changed, 15 insertions(+), 15 deletions(-)
Reviewed-by: Daniel P. Berrangé
Regards,
Daniel
--
|: https
onscious-lang-docs/blob/main/faq.md
>
> Signed-off-by: Philippe Mathieu-Daudé
> ---
> scripts/device-crash-test | 30 +++---
> 1 file changed, 15 insertions(+), 15 deletions(-)
Eduardo already sent a clever patch:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg778534.html
On 02/02/2021 20.12, Eduardo Habkost wrote:
Replace "whitelist" in the device-crash-test script with
"rule list".
I'm using "rule list" instead of "allow list" or "pass list"
because the list is not used only for expected/allowed errors.
scripts/device-crash-test | 30 +++---
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/scripts/device-crash-test b/scripts/device-crash-test
index 04118669ba7..6812de42f8c 100755
--- a/scripts/device-crash-test
+++ b/scripts/device-crash-test
@@ -41
On 2/2/21 2:12 PM, Eduardo Habkost wrote:
Replace "whitelist" in the device-crash-test script with
"rule list".
I'm using "rule list" instead of "allow list" or "pass list"
because the list is not used only for expected/allowed errors.
It
Replace "whitelist" in the device-crash-test script with
"rule list".
I'm using "rule list" instead of "allow list" or "pass list"
because the list is not used only for expected/allowed errors.
It also contain rules specifying which errors s
From: Eduardo Habkost
After the transition to Meson, the build directory now have
subdirectories named "qemu-system-*.p", and device-crash-test
will try to execute them as if they were binaries. This results
in errors like:
PermissionError: [Errno 13] Permission denied: './qem
On 10/26/20 1:52 PM, Eduardo Habkost wrote:
After the transition to Meson, the build directory now have
subdirectories named "qemu-system-*.p", and device-crash-test
will try to execute them as if they were binaries. This results
in errors like:
PermissionError: [Errno 13] Permiss
On 26/10/2020 13.52, Eduardo Habkost wrote:
> After the transition to Meson, the build directory now have
> subdirectories named "qemu-system-*.p", and device-crash-test
> will try to execute them as if they were binaries. This results
> in errors like:
>
>
After the transition to Meson, the build directory now have
subdirectories named "qemu-system-*.p", and device-crash-test
will try to execute them as if they were binaries. This results
in errors like:
PermissionError: [Errno 13] Permission denied: './qemu-system-or1k.p'
Thanks for the review.
On 1/24/19 12:20 AM, Eduardo Habkost wrote:
This breaks Python 2 support:
$ python2 scripts/device-crash-test
File "scripts/device-crash-test", line 534
print("No QEMU binary found", file=sys.stderr)
^
hunks from patch]
[ehabkost: edited commit message]
Signed-off-by: Eduardo Habkost
---
scripts/device-crash-test | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/scripts/device-crash-test b/scripts/device-crash-test
index 483dafb2fc..2a13fa4f84 100755
--- a/scripts/device-
On Thu, Jan 17, 2019 at 12:03:58AM +0530, Nisarg Shah wrote:
> Apply 2to3 tool to scripts/device-crash-test.
> Restrict whitelist entry stats in debug mode to be sorted only by "count",
> since Python 3 does
> not implicitly support comparing dictionaries.
Thanks for the
Message-Id: <1541510826-21031-1-git-send-email-th...@redhat.com>
Signed-off-by: Eduardo Habkost
---
scripts/device-crash-test | 15 ---
1 file changed, 15 deletions(-)
diff --git a/scripts/device-crash-test b/scripts/device-crash-test
index e93a7c0c84..549162a547 100755
--- a/scri
Apply 2to3 tool to scripts/device-crash-test.
Restrict whitelist entry stats in debug mode to be sorted only by "count",
since Python 3 does
not implicitly support comparing dictionaries.
Signed-off-by: Nisarg Shah
---
scripts/device-crash-test | 7 ---
1 file changed, 4 insert
On Tue, Nov 06, 2018 at 02:27:06PM +0100, Thomas Huth wrote:
> Looks like we've fixed them all already in the past months, e.g. with:
>
> f7d6bfcdc0fe49040aac3ac131a319cb5427957e
> spapr_pci: fail gracefully with non-pseries machine types
>
> 2363d5ee231bf047479422d56d3b85b7d37a7c23
> hw/ppc/
ot able to reproduce these crashes with the script
anymore... but please double-check whether I'm right.
scripts/device-crash-test | 15 ---
1 file changed, 15 deletions(-)
diff --git a/scripts/device-crash-test b/scripts/device-crash-test
index e93a7c0..549162a 100755
--- a
From: Thomas Huth
Devices that are derived from TYPE_SYS_BUS_DEVICE are not user_creatable
anymore by default, and some others have been marked as non-user_creatable
manually, so we can remove these devices from the "ignore"-list in the
device-crash-test script.
Signed-off-by: T
ist in the
> device-crash-test script.
>
> Signed-off-by: Thomas Huth
Thanks, queued on python-next.
--
Eduardo
Devices that are derived from TYPE_SYS_BUS_DEVICE are not user_creatable
anymore by default, and some others have been marked as non-user_creatable
manually, so we can remove these devices from the "ignore"-list in the
device-crash-test script.
Signed-off-by: Thomas Huth
---
scri
From: Thomas Huth
The problem with the various serial devices has been fixed a while
ago in commit 47c4f85a0c27888e12af827471cfef87deb49821 ("hw/char/serial:
Allow disconnected chardevs") already, so we can remove these entries
from the "ignore" list in the device-crash-test
The device-crash-test script is already inside the 'scripts'
directory, there's no need to add the directory manually to
sys.path.
Signed-off-by: Eduardo Habkost
Message-Id: <20180618225131.13113-2-ehabk...@redhat.com>
Reviewed-by: Daniel P. Berrangé
Reviewed-by: Stefan Ha
> from the "ignore" list in the device-crash-test script now.
>
> Signed-off-by: Thomas Huth
Thanks, queued on python-next.
--
Eduardo
The problem with the various serial devices has been fixed a while
ago in commit 47c4f85a0c27888e12af827471cfef87deb49821 ("hw/char/serial:
Allow disconnected chardevs") already, so we can remove these entries
from the "ignore" list in the device-crash-test script now.
Signed
On Mon, Jun 18, 2018 at 07:51:29PM -0300, Eduardo Habkost wrote:
> The device-crash-test script is already inside the 'scripts'
> directory, there's no need to add the directory manually to
> sys.path.
>
> Signed-off-by: Eduardo Habkost
> ---
> scripts/devic
The device-crash-test script is already inside the 'scripts'
directory, there's no need to add the directory manually to
sys.path.
Signed-off-by: Eduardo Habkost
---
scripts/device-crash-test | 1 -
1 file changed, 1 deletion(-)
diff --git a/scripts/device-crash-test b/scrip
off-by: Eduardo Habkost
---
scripts/device-crash-test | 3 ---
1 file changed, 3 deletions(-)
diff --git a/scripts/device-crash-test b/scripts/device-crash-test
index 5d17dc68dd..b3ce72069f 100755
--- a/scripts/device-crash-test
+++ b/scripts/device-crash-test
@@ -218,9 +218,6 @@ ERROR_WHI
On Mon, Apr 16, 2018 at 07:41:29PM +0200, Thomas Huth wrote:
> The CAN device crashes have been fixed with the commit
> 089eac81e1d34d202471c0a023284f47f4c5f00e already.
>
> Signed-off-by: Thomas Huth
Queued, thanks.
--
Eduardo
The CAN device crashes have been fixed with the commit
089eac81e1d34d202471c0a023284f47f4c5f00e already.
Signed-off-by: Thomas Huth
---
scripts/device-crash-test | 3 ---
1 file changed, 3 deletions(-)
diff --git a/scripts/device-crash-test b/scripts/device-crash-test
index 5d17dc6..b3ce720
From: Thomas Huth
Fixed by commit b3da551 ("fdc: Exit if ISA controller does not support DMA",
2018-03-16).
Signed-off-by: Thomas Huth
Signed-off-by: Paolo Bonzini
---
scripts/device-crash-test | 1 -
1 file changed, 1 deletion(-)
diff --git a/scripts/device-crash-test b/scri
From: Thomas Huth
Fixed in a0c167a18470831e359f0538c3cf67907808f13e ("x86_iommu: check
if machine has PCI bus").
Signed-off-by: Thomas Huth
Message-Id: <1521193892-15552-5-git-send-email-th...@redhat.com>
Signed-off-by: Paolo Bonzini
---
scripts/device-crash-test | 1 -
1
Fixed in a0c167a18470831e359f0538c3cf67907808f13e ("x86_iommu: check
if machine has PCI bus").
Signed-off-by: Thomas Huth
---
scripts/device-crash-test | 1 -
1 file changed, 1 deletion(-)
diff --git a/scripts/device-crash-test b/scripts/device-crash-test
index 8ad3f44..b3ce720 10
Now the script works with Python 3, so we can use the 'python'
binary provided by the system.
Signed-off-by: Eduardo Habkost
Message-Id: <20180312185503.5746-4-ehabk...@redhat.com>
Reviewed-by: Daniel P. Berrangé
Signed-off-by: Eduardo Habkost
---
scripts/device-crash-tes
We are not running the script on "make check" yet, and additional
bugs were introduced recently in the tree.
Whitelist the new crashes while we investigate, to allow us to
run device-crash-test on "make check" as soon as possible to
prevent new bugs.
Cc: Pavel Pisa
Cc: John
On Mon, Mar 12, 2018 at 03:55:03PM -0300, Eduardo Habkost wrote:
> Now the script works with Python 3, so we can use the 'python'
> binary provided by the system.
>
> Signed-off-by: Eduardo Habkost
> ---
> scripts/device-crash-test | 2 +-
> 1 file chan
Now the script works with Python 3, so we can use the 'python'
binary provided by the system.
Signed-off-by: Eduardo Habkost
---
scripts/device-crash-test | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/device-crash-test b/scripts/device-crash-test
index
On Fri, Mar 09, 2018 at 05:28:27PM -0300, Eduardo Habkost wrote:
> Run a subset of tests using device-crash-test on "make check", to
> help us catch device crashes earlier.
>
> This also add a "check-device-crash-test-full" rule, that will
> check all machine/d
On Fri, Mar 09, 2018 at 12:48:42PM -0800, no-re...@patchew.org wrote:
[...]
> /tmp/qemu-test/src/scripts/device-crash-test -q -t machine=DEFAULT accel=tcg
> -- x86_64-softmmu/qemu-system-x86_64 aarch64-softmmu/qemu-system-aarch64
> /usr/bin/env: python2.7: No such file or directo
device-crash-test on "make check"
=== TEST SCRIPT BEGIN ===
#!/bin/bash
set -e
git submodule update --init dtc
# Let docker tests dump environment info
export SHOW_ENV=1
export J=8
time make docker-test-quick@centos6
=== TEST SCRIPT END ===
Updating 3c8cf5a9c21ff8782164d1def7f44b
Run a subset of tests using device-crash-test on "make check", to
help us catch device crashes earlier.
This also add a "check-device-crash-test-full" rule, that will
check all machine/device combinations.
Signed-off-by: Eduardo Habkost
---
tests/Makefile.include | 13 +
We're going to run device-crash-test on "make check", so it's
better to make the script less noisy on known errors.
Signed-off-by: Eduardo Habkost
---
scripts/device-crash-test | 44 ++--
1 file changed, 22 insertions(+), 22 deleti
This will be useful for running a smaller test set on
"make check", instead of testing every single machine-type/device
combination.
Signed-off-by: Eduardo Habkost
---
scripts/device-crash-test | 29 +++--
1 file changed, 27 insertions(+), 2 deletions(-)
di
This optimization to skip tests if the machine is not runnable is
unreliable and makes the script ignore actual QEMU crashes, so
we're safer simply removing it.
Signed-off-by: Eduardo Habkost
---
scripts/device-crash-test | 31 +--
1 file changed, 1 insertion(+
This will be useful for hiding known crashes on "make check".
Signed-off-by: Eduardo Habkost
---
scripts/device-crash-test | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/device-crash-test b/scripts/device-crash-test
index ed9a552fa1..36194e4347 100755
---
Add simple examples for common use cases.
Signed-off-by: Eduardo Habkost
---
scripts/device-crash-test | 19 +++
1 file changed, 19 insertions(+)
diff --git a/scripts/device-crash-test b/scripts/device-crash-test
index c6a7875357..364c779cdb 100755
--- a/scripts/device-crash
We are not running the script on "make check" yet, and additional
bugs were introduced recently in the tree.
Whitelist the new crashes while we investigate, to allow us to
run device-crash-test on "make check" as soon as possible to
prevent new bugs.
Cc: Pavel Pisa
Cc: John
So, we're back to that time when we need to add new known crashes
to device-crash-test, because we haven't been running it in a
while and new bugs were introduced.
To help prevent this from happening again, this series adds new
rules to validate devices against the default machine-typ
Use action='store_const', dest='loglevel' to represent the effect
of each option more clearly.
This will also make the last option in the command-line override
the previous ones (e.g.: "-d -q").
Signed-off-by: Eduardo Habkost
---
scripts/device-crash-test | 22
From: Thomas Huth
These are crashes / errors which have been fixed already in the past
months. We can remove these from the device-crash-test script now.
Signed-off-by: Thomas Huth
Message-Id: <1513613438-11017-1-git-send-email-th...@redhat.com>
Signed-off-by: Eduardo Habkost
---
s
From: Thomas Huth
These are crashes / errors which have been fixed already in the past
months. We can remove these from the device-crash-test script now.
Signed-off-by: Thomas Huth
Message-Id: <1513613438-11017-1-git-send-email-th...@redhat.com>
Signed-off-by: Eduardo Habkost
---
s
On Mon, Dec 18, 2017 at 05:10:38PM +0100, Thomas Huth wrote:
> These are crashes / errors which have been fixed already in the past
> months. We can remove these from the device-crash-test script now.
>
> Signed-off-by: Thomas Huth
Queued on machine-next. Sorry for the long delay.
--
Eduardo
These are crashes / errors which have been fixed already in the past
months. We can remove these from the device-crash-test script now.
Signed-off-by: Thomas Huth
---
scripts/device-crash-test | 8
1 file changed, 8 deletions(-)
diff --git a/scripts/device-crash-test b/scripts/device
1 - 100 of 121 matches
Mail list logo
