Re: Improving tracking/processing of buildfarm test failures

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improving tracking/processing of buildfarm test failures
Date: 2024-05-25 12:00:00
Message-ID: bf2fec6f-14e2-c7ad-17b0-b2aaae17d007@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello Amit and Noah,

24.05.2024 14:15, Amit Kapila wrote:
> I feel it is a good idea to do something about this. It makes sense to
> start with something simple and see how it works. I think this can
> also help us whether we need to chase a particular BF failure
> immediately after committing.

24.05.2024 23:00, Noah Misch wrote:

>
>> (I could start with the second approach, if you don't mind, and we'll see
>> how it works.)
> Certainly you doing (2) can only help, though it may help less than (1).

Thank you for paying attention to this!

I've created such page to accumulate information on test failures:
https://wiki.postgresql.org/wiki/Known_Buildfarm_Test_Failures

I've deliberately added a trivial issue with partition_split, which is
doomed to be fixed soon, to test the information workflow, and I'm going
to add a few other items in the coming days.

Please share your comments and suggestions, if any.

Best regards,
Alexander

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2024-05-25 12:53:11 Re: Add SPLIT PARTITION/MERGE PARTITIONS commands
Previous Message Jelte Fennema-Nio 2024-05-25 11:01:44 Re: Volatile write caches on macOS and Windows, redux