qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] tests/docker: Refresh APT cache before installi


From: Thomas Huth
Subject: Re: [Qemu-devel] [PATCH] tests/docker: Refresh APT cache before installing new packages on Debian
Date: Wed, 24 Jul 2019 13:25:06 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2

On 24/07/2019 12.46, Philippe Mathieu-Daudé wrote:
> Cc'ing the qtest maintainers and Xiao since I have no clue about this test.
> 
> On 7/23/19 7:20 PM, address@hidden wrote:
>> Patchew URL: https://patchew.org/QEMU/address@hidden/
>> ---
>> PASS 4 pxe-test /x86_64/pxe/ipv4/q35/virtio-net-pci
>> MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))}  
>> QTEST_QEMU_BINARY=x86_64-softmmu/qemu-system-x86_64 QTEST_QEMU_IMG=qemu-img 
>> tests/rtc-test -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl 
>> --test-name="rtc-test" 
>> **
>> ERROR:/tmp/qemu-test/src/tests/rtc-test.c:173:check_time: assertion failed 
>> (ABS(t - s) <= wiggle): (3 <= 2)
>> ERROR - Bail out! ERROR:/tmp/qemu-test/src/tests/rtc-test.c:173:check_time: 
>> assertion failed (ABS(t - s) <= wiggle): (3 <= 2)

Was the test running on a machine with heavy load? In that case, the
test thread just might have been suspended for too long...
We might need to set the "wiggle" parameter there to a higher value
(like 5 seconds maybe)?
Or maybe we should fence the check_time() related tests with "if
(g_test_slow())" to make sure that they are not run on CI systems anymore...

 Thomas



reply via email to

[Prev in Thread] Current Thread [Next in Thread]