| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, "Gregory Stark (as CFM)" <stark(dot)cfm(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Commitfest 2023-03 starting tomorrow! |
| Date: | 2023-03-20 20:34:26 |
| Message-ID: | CA+hUKGJsE-1pC8VGi5YOU-b5jsMnEe5YLdwau2LucdL4R142vA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 21, 2023 at 9:22 AM Greg Stark <stark(at)mit(dot)edu> wrote:
> Yeah, even aside from flappers there's the problem that it's about as
> common for real commits to break some test as it is for patches to
> start failing tests. So often it's a real failure but it's nothing to
> do with the patch, it has to do with the commit that went into git.
That is true. The best solution to that problem, I think, is to teach
cfbot that it should test on top of the most recent master commit that
succeeded in CI here
https://github.com/postgres/postgres/commits/master . It's on my
list...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2023-03-20 20:35:38 | Re: Experiments with Postgres and SSL |
| Previous Message | Greg Stark | 2023-03-20 20:31:03 | Re: Experiments with Postgres and SSL |