[Top][All Lists]

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

Re: [PATCH v8 16/27] cirrus: Building freebsd in a single short

From: Thomas Huth
Subject: Re: [PATCH v8 16/27] cirrus: Building freebsd in a single short
Date: Mon, 14 Sep 2020 12:43:29 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0

On 14/09/2020 10.50, Philippe Mathieu-Daudé wrote:
> On 9/14/20 9:27 AM, Thomas Huth wrote:
>> On 13/09/2020 00.44, Yonggang Luo wrote:
>>> This reverts commit 45f7b7b9f38f5c4d1529a37c93dedfc26a231bba
>>> ("cirrus.yml: Split FreeBSD job into two parts").
>>> freebsd 1 hour limit not hit anymore
>>> I think we going to a wrong direction, I think there is some tests a stall 
>>> the test runner,
>>> please look at
>>> https://cirrus-ci.com/task/5110577531977728
>>> When its running properly, the consumed time are little, but when tests 
>>> running too long,
>>> look at the cpu usage, the cpu usage are nearly zero. doesn't consuming 
>>> time.
>>> And look at
>>> https://cirrus-ci.com/task/6119341601062912
>>> If the tests running properly, the time consuming are little
>>> We should not hide the error by split them
>>> Signed-off-by: Yonggang Luo <luoyonggang@gmail.com>
>>> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
>>> Reviewed-by: Ed Maste <emaste@FreeBSD.org>
>>> ---
>>>  .cirrus.yml | 35 ++++++++---------------------------
>>>  1 file changed, 8 insertions(+), 27 deletions(-)
>> I tried this a couple of times now, and currently the problem seems to
>> be gone, indeed. I'd still prefer to understand first why we have seen
>> the slowdown a couple of weeks ago, but if people agree that we should
>> revert the patch now, that's ok for me now, too.
> Not sure if related (probably not as failure and not timeout),
> I hit this during the night:
>   TEST    iotest-qcow2: 030 [fail]

No, that's a different (known) issue. See my patch on the list:

 [PATCH v2] iotests: Skip test_stream_parallel in test 030 when doing
"make check"


reply via email to

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