| From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | 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-11 00:16:14 |
| Message-ID: | CAEepm=1amc3n2G3n_PntLtx-FqHa1vigHjDE4NHSw34FfGzJYw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Sep 11, 2017 at 12:10 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> On Sun, Sep 10, 2017 at 4:40 PM, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
>> http://commitfest.cputube.org/
>
> This looks very interesting. But when I click on a "build: failing" icon,
> it takes me to a generic page, not one describing how that specific build
> is failing.
True. The problem is that travis-ci.org doesn't seem to provide a URL
that can take you directly to the latest build for a given branch,
instead I'd need to figure out how to talk to their API to ask for the
build ID of the latest build for that branch. For now you have to
note the Commitfest entry ID, and then when find the corresponding
branch (ie commitfest/14/1234) on the page it dumps you on. It would
be nice to fix that.
--
Thomas Munro
http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2017-09-11 00:22:12 | Re: The case for removing replacement selection sort |
| Previous Message | Thomas Munro | 2017-09-11 00:12:29 | Re: Automatic testing of patches in commit fest |