diff options
| author | Dr. David Alan Gilbert <dgilbert@redhat.com> | 2020-10-08 17:03:30 +0100 |
|---|---|---|
| committer | Thomas Huth <thuth@redhat.com> | 2020-10-13 08:08:55 +0200 |
| commit | a4339de2de4def4beb33e22e6f506bcc8b9d9326 (patch) | |
| tree | f95c2c0f6029463c6d6c4be5dc8ac4cdf28109d7 /softmmu | |
| parent | d8dd10950199ee4a505dc4872171dcb1b4ca6710 (diff) | |
| download | qemu-a4339de2de4def4beb33e22e6f506bcc8b9d9326.zip qemu-a4339de2de4def4beb33e22e6f506bcc8b9d9326.tar.gz qemu-a4339de2de4def4beb33e22e6f506bcc8b9d9326.tar.bz2 | |
tests/migration: Allow longer timeouts
In travis, with gcov and gprof we're seeing timeouts; hopefully fix
this by increasing the test timeouts a bit, but for xbzrle ensure it
really does get a couple of cycles through to test the cache.
I think the problem in travis is we have about 2 host CPU threads,
in the test we have at least 3:
a) The vCPU thread (100% flat out)
b) The source migration thread
c) The destination migration thread
if (b) & (c) are slow for any reason - gcov+gperf or a slow host -
then they're sharing one host CPU thread so limit the migration
bandwidth.
Tested on my laptop with:
taskset -c 0,1 ./tests/qtest/migration-test -p /x86_64/migration
Reported-by: Alex Bennée <alex.bennee@linaro.org>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Message-Id: <20201008160330.130431-1-dgilbert@redhat.com>
[thuth: Move the #define to the right location]
Signed-off-by: Thomas Huth <thuth@redhat.com>
Diffstat (limited to 'softmmu')
0 files changed, 0 insertions, 0 deletions