Re: Automatic testing of patches in commit fest

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>
Cc: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Subject: Re: Automatic testing of patches in commit fest
Date: 2017-09-12 13:58:37
Message-ID: 28852.1505224717@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Aleksander Alekseev 2017-09-12 14:14:55 Patches that don't apply or don't compile: 2017-09-12
Previous Message Alvaro Herrera 2017-09-12 13:58:31 Re: Re: [COMMITTERS] pgsql: Use MINVALUE/MAXVALUE instead of UNBOUNDED for range partition b