Re: [HACKERS] Automatic testing of patches in commit fest - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Automatic testing of patches in commit fest
Date
Msg-id 28852.1505224717@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Automatic testing of patches in commit fest  (Aleksander Alekseev <a.alekseev@postgrespro.ru>)
Responses Re: [HACKERS] Automatic testing of patches in commit fest  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
Aleksander Alekseev <a.alekseev@postgrespro.ru> writes:
> I've ended up with this script [1]. It just generates a list of patches
> that are in "Needs Review" status but don't apply or don't compile. Here
> is the current list:

> === Apply Failed: 29 ===
> https://commitfest.postgresql.org/14/1235/ (Support arrays over domain types)

Can you clarify what went wrong for you on that one?  I went to rebase it,
but I end up with the identical patch except for a few line-numbering
variations.
        regards, tom lane


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] Re: [COMMITTERS] pgsql: Use MINVALUE/MAXVALUE insteadof UNBOUNDED for range partition b
Next
From: Aleksander Alekseev
Date:
Subject: [HACKERS] Patches that don't apply or don't compile: 2017-09-12