On 7/11/20 4:31 AM, Landry Breuil wrote:
> On Fri, Jul 10, 2020 at 08:59:08PM -0400, Aisha Tammy wrote:
>> On 7/10/20 7:59 PM, phess...@openbsd.org wrote:
>>> bulk build on arm64.ports.openbsd.org
>>> started on  Wed Jul 8 01:41:54 MDT 2020
>>> finished at Fri Jul 10 17:59:21 MDT 2020
>>> lasted 2D16h17m
>>> done with kern.version=OpenBSD 6.7-current (GENERIC.MP) #709: Tue Jul  7 
>>> 20:26:22 MDT 2020
>>>
>>> built packages:10837
>>> Jul 8:4109
>>> Jul 9:1700
>>> Jul 10:5027
>>>
>>>
>>> critical path missing pkgs:  
>>> http://build-failures.rhaalovely.net/aarch64/2020-07-08/summary.log
>>>
>>> build failures: 13
>>> http://build-failures.rhaalovely.net/aarch64/2020-07-08/databases/sqlite3-odbc.log
>>> http://build-failures.rhaalovely.net/aarch64/2020-07-08/editors/xwpe.log
>>> http://build-failures.rhaalovely.net/aarch64/2020-07-08/games/vkquake.log
>>> http://build-failures.rhaalovely.net/aarch64/2020-07-08/graphics/vulkan-validation-layers.log
>>> http://build-failures.rhaalovely.net/aarch64/2020-07-08/lang/compcert.log
>>> http://build-failures.rhaalovely.net/aarch64/2020-07-08/lang/pfe.log
>>> http://build-failures.rhaalovely.net/aarch64/2020-07-08/sysutils/libvirt.log
>>> http://build-failures.rhaalovely.net/aarch64/2020-07-08/sysutils/nomad.log
>>> http://build-failures.rhaalovely.net/aarch64/2020-07-08/sysutils/rclone.log
>>
>> I had a question about these messages. 
>> Really nice to have these btw, I really love them :) Thanks a bunch.
>>
>> sysutils/rclone - is not listed in recurrent failures or in new failures?
>>
>> What is this supposed to mean about the failures of rclone ?
>> Similarly for the things only listed in build failures but not in any of
>> the bottom three lists!!
> 
> the script hacked up years ago more or less does this with the build
> logs to find the failures:
> 
> paths=`grep locked ${LOCKDIR}/* | cut -d = -f2`
> for p in $paths ; do
>       echo $site/${ARCH}/${DATE}/$p.log ;
>       mkdir -p failures/`dirname $p`  ;
>       cp paths/$p.log failures/`dirname $p`; 
> done
> [ -f /usr/ports/logs/${ARCH}/summary.log ] && cp 
> /usr/ports/logs/${ARCH}/summary.log failures/
> find failures -type f > ls-failures
> 
> LAST=../old/${ARCH}/last/
> 
> if [ -f ${LAST}/ls-failures ] ; then
>       echo
>       echo "recurrent failures"
>       diff -u ${LAST}/ls-failures ls-failures | grep '^ '
Ah, I see, here the recurrent failures should probably be removed, as it 
only finds the common lines in the diff, which are not all the common lines.
-u seems to only have 3 lines of context.

Ideal solution would be to sort and find commons and differences (not sure if 
can
be done in shell, wouldn't bother with it). 

Removing the recurrent ones seems to be the next best solution.

Aisha

>       echo "new failures"
>       diff -u ${LAST}/ls-failures ls-failures | grep ^+
>       echo "resolved failures"
>       diff -u ${LAST}/ls-failures ls-failures | grep ^-
> fi
> 
> LAST is of course the previous bulk.
> 

Reply via email to