Message-ID: <d7d2996e-0ca2-4887-b022-75bf124de40a@dunslane.net>
Date: Thu, 25 Jul 2024 08:12:38 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: fairywren timeout failures on the pg_amcheck/005_opclass_damage
 test
To: Alexander Lakhin <exclusion@gmail.com>,
 pgsql-hackers <pgsql-hackers@postgresql.org>
References: <b2037a8d-fe6b-d299-da17-ff5f3214e648@gmail.com>
From: Andrew Dunstan <andrew@dunslane.net>
Content-Language: en-US
Autocrypt: addr=andrew@dunslane.net; keydata=
 xsBNBE7KWFkBCAClridxur2AIc7eW2AR7izbfp3EnNefie2HbLF0izW5Ik5UjX2HBXBx4syI
 gY6b0ugohXrr274+baoAlvSbq6cAoQuEVrk5IZFzt20b1Xkx65FwGSEj526yiKLocqkJceSq
 Xr9xcA5SGY+FZv441chh5SU92v4q6z+6LPpoHOh97ptAVXZYNTtU0LevyvD5lja0TzbvJm6C
 eFXitJfnm1pLEr0DGJCR/iUOl/N62Kh4855zZC7NHIjQHPOvV5Stz/l5ilDhvGVk+xkXFPys
 SjZoUr1rXhYLpiyi5sR0X9FHXT0KnGuz1F5ERO7ZTLSSQ6fJwPj6gOk9K+vvoKvoeql5ABEB
 AAHNJEFuZHJldyBEdW5zdGFuIDxhbmRyZXdAZHVuc2xhbmUubmV0PsLAmwQTAQgARQIbAwIX
 gAIZAQULCQgHAgMiAgEGFQoJCAsCBBYCAwECHgcWIQTkPlhGHfx8v0RpFaWZ+n/LWfw7gQUC
 ZFlxxwUJGVGAbgAKCRCZ+n/LWfw7gXikB/9ZdcUy6CTBFIIuL/bVsc1eLEW/gJBjJBF6HxNY
 xgEkAgXAp4Lg4A5U+QB9GouFr7+GYxF0BU4hzoGhNPUWltxnHdMWP8nC/38LAqgMi8L/bbsm
 HW5YPBdWYaAZAPJQVfOAgjTbRUb26KSprpyrrJKW0ZmrZfjhNPcQ72jpWzoPLQqx2X6B0fru
 1jq+cBh8lb6r1mJTim1T3JIn+F/v5VpdQS+EL8xqsHkfzKjIPsW3CIXpkypSk6saA55Rkkbl
 26AW8ftPVB0Q6Lnn6FLt9CP0MGNixBQ55yq8r1K+nCBvCCjvQjM8RDm0UUum0WNl+ifQgTLO
 E8TWEnwVtkBf+3QWzsBNBE7KWFkBCADRnOM0FCzsYW6jtncg+dWIagjUZpvaClmqn/sJluLa
 Q3v1VXMQJzYs3eC1gh386W+XBwLRpDj3jzH81lX+p73Re3d3oJW7X+ffsxuzu5ZVdMUkqBYo
 nkAbKxr6gyJ12F/+JkUVzLcoTN+d/7YsQvUVi7NaKH8mJgjz112O4fUe3p9wfAaFa0RXHc5S
 GPzRTYRRlv/XZBIho4J2tkZOnteZJZ+GbxQVlINt6fd8P6al3MWOvpP/ExJPguEfjOsO6Njy
 xjo3WfpD4lHMOR/Oc3/8mScEF84rF2jXbsFgelWnbPWAvXY+pD0dXOFRkagGmC/viwBDqq5b
 5tk76kKmUbZxABEBAAHCwHwEGAEIACYCGwwWIQTkPlhGHfx8v0RpFaWZ+n/LWfw7gQUCZFlx
 5wUJGVGAjgAKCRCZ+n/LWfw7gf+iB/4g8CPY5jihf5r/8EsoIGe2H+dpVmpPF8YGBzTIvCz/
 fQoOq8AX/pE76QEuFnFZWfjw+wgBXgCVmkox2Eflkk6z4ND3pcwGZ6CfCxTQCDk/dij+2DQ4
 6bmDCy/sBgcbz9mTpoLC11HLoPae6YN9nBNQRZDcEFEu54OaVOqlIdbA6m+POIBCXZdHOFc0
 WoDTgxHRzC1jgQNidyd6tKqcsVJs0dzF0oKTmFFmUAqTdJO12LBuNA1rlqrR3EtpYk8B/wtS
 5dIMD7Q8hwQpL+4C6GNpb6ZKnPkLi47pDOLhz2qBrqN+rqUEsT3YnExYpzj5yOBi+FlmV1Hw
 49QYe1sn2ZPs
In-Reply-To: <b2037a8d-fe6b-d299-da17-ff5f3214e648@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/d7d2996e-0ca2-4887-b022-75bf124de40a%40dunslane.net>
Precedence: bulk


On 2024-07-25 Th 8:00 AM, Alexander Lakhin wrote:
> Hello hackers,
>
> Please take a look at today's failure [1], that raises several questions
> at once:
> 117/244 postgresql:pg_upgrade / pg_upgrade/002_pg_upgrade 
> TIMEOUT        3001.48s   exit status 1
> 180/244 postgresql:pg_amcheck / pg_amcheck/005_opclass_damage 
> TIMEOUT        3001.43s   exit status 1
>
> Ok:                 227
> Expected Fail:      0
> Fail:               0
> Unexpected Pass:    0
> Skipped:            15
> Timeout:            2
>
> But looking at the previous test run [2], marked 'OK', I can see almost
> the same:
> 115/244 postgresql:pg_upgrade / pg_upgrade/002_pg_upgrade 
> TIMEOUT        3001.54s   exit status 1
> 176/244 postgresql:pg_amcheck / pg_amcheck/005_opclass_damage 
> TIMEOUT        3001.26s   exit status 1
>
> Ok:                 227
> Expected Fail:      0
> Fail:               0
> Unexpected Pass:    0
> Skipped:            15
> Timeout:            2
>
> So it's not clear to me, why is the latter test run considered failed
> unlike the former?


Yesterday I changed the way we detect failure in the buildfarm client, 
and pushed that to fairywren (and a few more of my animals). Previously 
it did not consider a timeout to be a failure, but now it does. I'm 
going to release that soon.


cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com