Thread: patch extracting

patch extracting

From
"Erik Rijkers"
Date:
I find myself once again trying to find and extract links to the latest patch, from https://commitfest.postgresql.org/
(or
anywhere on postgresql.org; the mail archive being another possibility).  The goal, of course, is to automatically
download
& compile the lot.

I suppose I can figure it out but before I go any further: wouldn't it be possible to build some support for that goal
in
the commitfest application (or saomewhere else)?  Could it be done by pulling the latest link for each patch for each
fest
to some central place/list/ page?  It could be more stable then my local hacking.

(Almost equally satisfying would be to receive a program from anyone who has already done the work of extracting links
from
those pages or the mail archive)


thanks,

Erik Rijkers








Re: patch extracting

From
Magnus Hagander
Date:
<p dir="ltr"><br /> On Feb 1, 2015 10:50 AM, "Erik Rijkers" <<a href="mailto:er@xs4all.nl">er@xs4all.nl</a>>
wrote:<br/> ><br /> > I find myself once again trying to find and extract links to the latest patch, from <a
href="https://commitfest.postgresql.org/">https://commitfest.postgresql.org/</a>(or<br /> > anywhere on <a
href="http://postgresql.org">postgresql.org</a>;the mail archive being another possibility).  The goal, of course, is
toautomatically download<br /> > & compile the lot.<br /> ><br /> > I suppose I can figure it out but
beforeI go any further: wouldn't it be possible to build some support for that goal in<br /> > the commitfest
application(or saomewhere else)?  Could it be done by pulling the latest link for each patch for each fest<br /> >
tosome central place/list/ page?  It could be more stable then my local hacking.<br /> ><br /> > (Almost equally
satisfyingwould be to receive a program from anyone who has already done the work of extracting links from<br /> >
thosepages or the mail archive)<br /><p dir="ltr">This is on my todo list for the app, yes. It was considered as one of
theuse cases in the new architecture. Not done yet, but definitely on the list. It's be happy to work with you on it -
oncethe more u urgent features and regressions have been taken care of. <p dir="ltr">/Magnus  

Re: patch extracting

From
Peter Eisentraut
Date:
On 2/1/15 3:10 AM, Erik Rijkers wrote:
> I find myself once again trying to find and extract links to the latest patch, from
https://commitfest.postgresql.org/(or
 
> anywhere on postgresql.org; the mail archive being another possibility).  The goal, of course, is to automatically
download
> & compile the lot.
> 
> I suppose I can figure it out but before I go any further: wouldn't it be possible to build some support for that
goalin
 
> the commitfest application (or saomewhere else)?  Could it be done by pulling the latest link for each patch for each
fest
> to some central place/list/ page?  It could be more stable then my local hacking.
> 
> (Almost equally satisfying would be to receive a program from anyone who has already done the work of extracting
linksfrom
 
> those pages or the mail archive)

https://github.com/petere/commitfest-tools/blob/master/commitfest_branches#L134

Note, however, that this kind of thing needs constant manual
baby-sitting, because people send all kinds of attachments in all kinds
of ways.

Example 1: Someone sends patch and benchmark output as two attachments
with indistinguishable content types.

Example 2: Mail with two patches that are alternative implementations
(so they don't apply together), as opposed to mail with two patches that
apply in series.

The only way to fix these kinds of fundamental issues is using git pull
requests.

Nonetheless, the above code works most of the time.  I have used it for
automatically building and compiling commit fest submissions
(http://petereisentraut.blogspot.com/2013/08/automating-patch-review.html),
but got tired of having to manually feed the build failures to the
mailing list.  I need a way to automatically post build results back
into the commit fest app.