| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Subject: | Re: longfin and tamandua aren't too happy but I'm not sure why |
| Date: | 2022-09-29 03:45:31 |
| Message-ID: | 20220929034531.4k4zvxsxdsl7g7ti@awork3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2022-09-28 21:22:26 +0200, Alvaro Herrera wrote:
> I have an additional, unrelated complaint about CI, which is that we
> don't have anything for past branches. I have a partial hack(*), but
> I wish we had something we could readily use.
>
> (*) I just backpatched the commit that added the .cirrus.yml file, plus
> some later fixes to it, and I keep that as a separate branch which I
> merge with whatever other changes I want to test. I then push that to
> github, and ignore the windows results when looking at cirrus-ci.com.
I'd not be against backpatching the ci stuff if there were sufficient demand
for it. It'd probably be a decent bit of initial work, but after that it
shouldn't be too bad.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2022-09-29 04:46:54 | Re: Eliminating SPI from RI triggers - take 2 |
| Previous Message | Kyotaro Horiguchi | 2022-09-29 03:35:04 | Re: Make ON_ERROR_STOP stop on shell script failure |