PostgreSQL Patch Tester

Current commitfest | Next commitfest | FAQ | Statistics | Highlights

Highlight type: all assertion compiler core linker panic regress sanitizer tap test

Time range: current 7-day 30-day 90-day

This robot generates gigabytes of CI logs every week. Here is an attempt to search for "highlights", so it's easier to find actionable information quickly. New ideas for what patterns to search for are very welcome. "Current" shows only the most recent results from each submission. The wider time ranges also show information about historical versions, which may be useful for flapping tests, and also for hunting for bugs in master.

55/4718 Set log_lock_waits=on by default
Windows - Server 2019, VS 2019 - Meson & ninja
tap
[07:07:26.279](0.000s) not ok 18 - checking with a non-existent user stderr /(?^:role "no_such_user" does not exist)/
tap
[07:11:10.782](0.001s) not ok 5 - reserved_connections limit: matches
54/5848 Add Table of Contents to psql Reference Page
Windows - Server 2019, VS 2019 - Meson & ninja
tap
[05:54:48.119](0.001s) not ok 4 - connecting to an invalid database: matches
55/5831 pgindent: improve formatting of multiline comments
Windows - Server 2019, VS 2019 - Meson & ninja
tap
[02:33:57.371](0.000s) not ok 2 - connecting to a non-existent database: matches
55/5487 Exists pull-up application with JoinExpr
Windows - Server 2019, VS 2019 - Meson & ninja
tap
[01:27:49.205](124.189s) not ok 5 - regression tests pass
[01:28:24.210](12.090s) not ok 16 - run of pg_upgrade for new instance
[01:28:24.211](0.000s) not ok 17 - pg_upgrade_output.d/ removed after pg_upgrade success
[01:28:26.888](0.128s) not ok 20 - old and new dumps match after pg_upgrade
tap
[01:30:37.017](134.624s) not ok 2 - regression tests pass
[01:30:37.017](0.000s) not ok 3 - primary alive after regression test run
macOS - Sonoma - Meson
tap
[01:25:54.684](97.952s) not ok 5 - regression tests pass
[01:26:31.260](11.729s) not ok 16 - run of pg_upgrade for new instance
[01:26:31.264](0.002s) not ok 17 - pg_upgrade_output.d/ removed after pg_upgrade success
[01:26:32.917](0.138s) not ok 20 - old and new dumps match after pg_upgrade
tap
[01:27:49.934](135.692s) not ok 2 - regression tests pass
[01:27:49.938](0.000s) not ok 3 - primary alive after regression test run
Linux - Debian Bookworm - Meson
tap
[01:28:05.212](70.303s) not ok 5 - regression tests pass
[01:28:26.669](9.277s) not ok 16 - run of pg_upgrade for new instance
[01:28:26.669](0.000s) not ok 17 - pg_upgrade_output.d/ removed after pg_upgrade success
[01:28:28.091](0.197s) not ok 20 - old and new dumps match after pg_upgrade
tap
[01:29:20.539](71.533s) not ok 2 - regression tests pass
[01:29:20.540](0.000s) not ok 3 - primary alive after regression test run
FreeBSD - Meson
tap
[01:27:40.641](205.816s) not ok 5 - regression tests pass
[01:28:20.282](20.161s) not ok 16 - run of pg_upgrade for new instance
[01:28:20.283](0.000s) not ok 17 - pg_upgrade_output.d/ removed after pg_upgrade success
[01:28:21.938](0.033s) not ok 20 - old and new dumps match after pg_upgrade
tap
[01:28:49.849](227.914s) not ok 2 - regression tests pass
[01:28:49.850](0.000s) not ok 3 - primary alive after regression test run
Linux - Debian Bookworm - Autoconf
tap
[01:32:05.466](131.549s) not ok 5 - regression tests pass
[01:32:31.592](9.838s) not ok 16 - run of pg_upgrade for new instance
[01:32:31.592](0.000s) not ok 17 - pg_upgrade_output.d/ removed after pg_upgrade success
[01:32:32.522](0.044s) not ok 20 - old and new dumps match after pg_upgrade
tap
[01:33:01.095](88.631s) not ok 2 - regression tests pass
[01:33:01.096](0.000s) not ok 3 - primary alive after regression test run
55/5663 Selectively invalidate caches in pgoutput when pg_namespace is modified
Windows - Server 2019, VS 2019 - Meson & ninja
tap
[15:32:53.359](0.001s) not ok 2 - regular connections limit: matches
55/5927 Fix incorrect comment in pg_get_shmem_allocations_numa()
Windows - Server 2019, VS 2019 - Meson & ninja
tap
[13:23:01.007](0.000s) not ok 3 - checking a non-existent database stderr /(?^:FATAL:  database "qqq" does not exist)/
55/5681 Prevent internal error at concurrent CREATE OR REPLACE / ALTER FUNCTION
Linux - Debian Bookworm - Autoconf
tap
[13:00:40.908](131.874s) not ok 5 - regression tests pass
[13:00:57.529](6.275s) not ok 16 - run of pg_upgrade for new instance
[13:00:57.529](0.000s) not ok 17 - pg_upgrade_output.d/ removed after pg_upgrade success
[13:00:58.339](0.037s) not ok 20 - old and new dumps match after pg_upgrade
55/5588 Improvement of var_eq_non_const()
FreeBSD - Meson
tap
[12:47:35.191](220.917s) not ok 5 - regression tests pass
tap
[12:48:43.267](242.342s) not ok 2 - regression tests pass
Linux - Debian Bookworm - Meson
tap
[12:48:28.039](76.102s) not ok 5 - regression tests pass
tap
[12:49:53.753](83.739s) not ok 2 - regression tests pass
macOS - Sonoma - Meson
tap
[12:43:13.395](39.398s) not ok 5 - regression tests pass
tap
[12:44:16.744](58.040s) not ok 2 - regression tests pass
Windows - Server 2019, VS 2019 - Meson & ninja
tap
[12:46:49.663](125.274s) not ok 5 - regression tests pass
tap
[12:49:31.756](132.750s) not ok 2 - regression tests pass
Linux - Debian Bookworm - Autoconf
tap
[12:52:16.501](145.567s) not ok 5 - regression tests pass
tap
[12:53:08.767](101.013s) not ok 2 - regression tests pass
55/5553 starjoin join order planning
Linux - Debian Bookworm - Meson
tap
[12:21:51.366](80.506s) not ok 5 - regression tests pass
tap
[12:23:16.730](85.855s) not ok 2 - regression tests pass
tap
[12:26:17.559](2.284s) not ok 1 - no parameters missing from postgresql.conf.sample
macOS - Sonoma - Meson
tap
[12:19:35.829](77.943s) not ok 5 - regression tests pass
tap
[12:21:16.437](99.182s) not ok 2 - regression tests pass
tap
[12:23:39.638](0.986s) not ok 1 - no parameters missing from postgresql.conf.sample
Windows - Server 2019, VS 2019 - Meson & ninja
tap
[12:20:59.156](129.243s) not ok 5 - regression tests pass
tap
[12:23:43.564](133.647s) not ok 2 - regression tests pass
tap
[12:31:15.796](1.822s) not ok 1 - no parameters missing from postgresql.conf.sample
Linux - Debian Bookworm - Autoconf
tap
[12:24:56.158](117.088s) not ok 5 - regression tests pass
tap
[12:22:15.677](0.640s) not ok 1 - no parameters missing from postgresql.conf.sample
tap
[12:26:15.739](80.120s) not ok 2 - regression tests pass
FreeBSD - Meson
tap
[12:20:36.618](211.524s) not ok 5 - regression tests pass
tap
[12:21:55.346](243.729s) not ok 2 - regression tests pass
tap
[12:22:57.840](1.558s) not ok 1 - no parameters missing from postgresql.conf.sample
55/5901 Proposal to allow DELETE/UPDATE on partitioned tables with unsupported foreign partitions
Windows - Server 2019, VS 2019 - Meson & ninja
tap
[12:18:45.035](132.394s) not ok 5 - regression tests pass
tap
[12:21:30.518](138.406s) not ok 2 - regression tests pass
macOS - Sonoma - Meson
tap
[12:15:59.851](66.836s) not ok 5 - regression tests pass
tap
[12:17:37.459](91.516s) not ok 2 - regression tests pass
Linux - Debian Bookworm - Meson
tap
[12:19:25.294](79.036s) not ok 5 - regression tests pass
tap
[12:20:48.041](82.873s) not ok 2 - regression tests pass
FreeBSD - Meson
tap
[12:18:33.985](203.065s) not ok 5 - regression tests pass
tap
[12:19:32.977](217.050s) not ok 2 - regression tests pass
Linux - Debian Bookworm - Autoconf
tap
[12:23:14.925](131.560s) not ok 5 - regression tests pass
tap
[12:24:03.159](98.551s) not ok 2 - regression tests pass
55/5892 parallel safety of correlated subquery (was: parallel_safe)
Linux - Debian Bookworm - Meson
tap
[12:05:49.615](12.843s) not ok 5 - regression tests pass
[12:05:58.417](3.168s) not ok 14 - run of pg_upgrade --check for new instance
[12:05:58.418](0.000s) not ok 15 - pg_upgrade_output.d/ removed after pg_upgrade --check success
[12:05:58.630](0.212s) not ok 16 - run of pg_upgrade for new instance
[12:05:58.631](0.000s) not ok 17 - pg_upgrade_output.d/ removed after pg_upgrade success
[12:05:58.793](0.036s) not ok 18 - check that locales in new cluster match original cluster
[12:05:59.549](0.023s) not ok 20 - old and new dumps match after pg_upgrade
tap
[12:05:44.019](0.000s) not ok 2 - run of pg_upgrade where the new cluster has insufficient "max_replication_slots" stdou...
[12:05:49.688](0.000s) not ok 6 - run of pg_upgrade of old cluster with slots having unconsumed WAL records stdout /(?^:...
tap
[12:05:47.131](0.000s) not ok 2 - run of pg_upgrade where the new cluster has insufficient max_active_replication_origin...
tap
[12:05:44.376](4.176s) not ok 13 - run of pg_upgrade
[12:05:44.391](0.000s) not ok 16 - the default char signedness is updated during pg_upgrade: matches
tap
[12:05:52.149](15.926s) not ok 1 - pg_upgrade with transfer mode --clone: stdout matches
[12:05:59.107](4.858s) not ok 3 - pg_upgrade with transfer mode --copy: stdout matches
[12:06:05.029](3.946s) not ok 5 - pg_upgrade with transfer mode --copy-file-range: stdout matches
[12:06:10.988](4.221s) not ok 7 - pg_upgrade with transfer mode --link: stdout matches
[12:06:18.361](5.389s) not ok 9 - pg_upgrade with transfer mode --swap: stdout matches
tap
[12:06:27.063](9.988s) not ok 2 - regression tests pass
[12:06:27.063](0.000s) not ok 3 - primary alive after regression test run
55/5964 Do not exit on postmaster death event inside CRIT sections.
macOS - Sonoma - Meson
tap
[11:23:10.408](0.000s) not ok 268 - pgbench script error: sql syntax error stderr /(?^:ERROR:  syntax error)/
[11:23:10.410](0.000s) not ok 269 - pgbench script error: sql syntax error stderr /(?^:prepared statement .* does not ex...
55/5940 Improve LWLock tranche name visibility across backends
Windows - Server 2019, VS 2019 - Meson & ninja
tap
[10:22:52.050](2.138s) Bail out!  pg_ctl start failed
tap
[10:22:53.138](7.581s) Bail out!  pg_ctl start failed