|From:||Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>|
|To:||Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>|
|Cc:||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|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
> > Unless there are any objections to give this idea a try I'm willing to
> > write and host a corresponding script.
> 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.
Agree. However we could simply add an "Enable autotests" checkbox to the
commitfest application. In fact we could even left the commitfest
application as is and provide corresponding checkboxes in the web
interface of the "autoreviewer" application. Naturally every
automatically generated code review will include a link that disables
autotests for this particular commitfest entry.
I hope this observation will change your mind :)
|Next Message||Amit Kapila||2017-09-11 13:25:19||Re: Parallel Append implementation|
|Previous Message||Etsuro Fujita||2017-09-11 13:01:24||Re: Add support for tuple routing to foreign partitions|