| From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Cc: | Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Automatic testing of patches in commit fest |
| Date: | 2017-09-12 22:08:38 |
| Message-ID: | CAEepm=0jKkzh+YEkmJbyZ571F3hwU-Lr0KKKqOvassG_Qvt=sQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 12, 2017 at 12:45 AM, Tomas Vondra
<tomas(dot)vondra(at)2ndquadrant(dot)com> wrote:
> That won't work until (2) is reliable enough. There are patches (for
> example my "multivariate MCV lists and histograms") which fails to apply
> only because the tool picks the wrong patch. Possibly because it does
> not recognize compressed patches, or something.
FWIW I told it how to handle your .patch.gz files and Alexander
Lakhin's .tar.bz2 files. Your patch still didn't apply anyway due to
bitrot, but I see you've just posted a new one so it should hopefully
turn green soon. (It can take a while because it rotates through the
submissions at a rate of one submission every 5 minutes after a new
commit to master is detected, since I don't want to get in trouble for
generating excessive load against the Commitfest, Github or (mainly)
Travis CI. That's probably too cautious and over time we can revise
it.)
--
Thomas Munro
http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Dilger | 2017-09-12 22:16:01 | Re: Renaming PG_GETARG functions (was Re: PG_GETARG_GISTENTRY?) |
| Previous Message | Thomas Munro | 2017-09-12 21:56:30 | Re: Automatic testing of patches in commit fest |