From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-www(at)lists(dot)postgresql(dot)org |
Subject: | Re: Should we have a "Testing" topic in the CF app? |
Date: | 2022-08-03 08:43:31 |
Message-ID: | CAD21AoC36N32CxBf+JMf+dK_fbjbHkEm+TGtkNSnpKZejQ3JZQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On Wed, Aug 3, 2022 at 4:40 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>
> > On 1 Aug 2022, at 13:58, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>
> > Unless there are objections raised I can go and create that topic.
>
>
> Done. I took the liberty of moving one of the TAP test patches over just to
> check that everything worked as intended.
Thanks!
Skimming the CF entries, the following patches can be moved to the new
Testing category:
* Unit tests for SLRU
* https://commitfest.postgresql.org/39/3608/
* Improve TAP tests of pg_upgrade for cross-version tests
* https://commitfest.postgresql.org/39/3649/
* CI and test improvements
* https://commitfest.postgresql.org/39/3709/
* add test: pg_rowlocks extension
* https://commitfest.postgresql.org/39/3724/
* Testing autovacuum wraparound
* https://commitfest.postgresql.org/39/3729/
* pgstattuple: add test for coverage
* https://commitfest.postgresql.org/39/3793/
* Introduce wait_for_subscription_sync for TAP tests
* https://commitfest.postgresql.org/39/3780/
Regards,
--
Masahiko Sawada
EDB: https://www.enterprisedb.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Gustafsson | 2022-08-03 13:28:37 | Re: Should we have a "Testing" topic in the CF app? |
Previous Message | Daniel Gustafsson | 2022-08-03 07:40:40 | Re: Should we have a "Testing" topic in the CF app? |