Patch CI statistics

Pipeline reads CI wall-clock time. Corpus reads today's patchsets laid out over PostgreSQL's history.

range24h 7d 30d 90d all

granularityhour day week

Runs

1,887

terminal, in range

Success rate

85.6%

1,616 of 1,887

Median build

2m 49s

successful and failed alike

Median test

5m 12s

successful and failed alike

Median queue wait

0m 00s

queued to started

Infra errors

0.0%

0 runs

GitHub re-attempts

attempt > 1 on one run id

Runs by result

terminal runs only; timeouts fold into their failure band

Show data

When	Result	Runs
17 Aug 00:00	success	10
17 Aug 00:00	tests failed	1
18 Aug 00:00	build failed	78
18 Aug 00:00	success	1,606
18 Aug 00:00	tests failed	192

Success rate

hollow points sit below 5 terminal runs in the bucket

Show data

When	Success rate	Terminal runs
17 Aug 00:00	90.9%	11
18 Aug 00:00	85.6%	1,876

Build and test duration by era

median seconds; successful runs only

Show data

When	Era	Build median	Test median	Build p25-p75
18 Aug 00:00	bookworm	2m 51s	4m 02s	2m 38s - 2m 57s
18 Aug 00:00	bullseye	2m 11s	3m 13s	2m 04s - 2m 15s
18 Aug 00:00	buster	1m 58s	2m 59s	1m 55s - 2m 01s
17 Aug 00:00	trixie	2m 49s	5m 24s	2m 49s - 2m 54s
18 Aug 00:00	trixie	2m 51s	5m 18s	2m 45s - 2m 55s

ccache hit rate

median per bucket; the image's warm cache was baked against one reference commit, so a patch on a different base misses most of it

Show data

When	Hit rate	Runs
17 Aug 00:00	1.5%	10
18 Aug 00:00	1.5%	1,606

Build time against ccache hit rate

one point per successful run; table shows the first 50

Show data

Hit rate	Build
3.3%	1m 56s
3.3%	2m 01s
1.5%	2m 56s
3.3%	1m 35s
3.3%	1m 55s
3.3%	1m 55s
3.3%	2m 01s
3.3%	1m 58s
3.3%	2m 05s
3.3%	1m 58s
1.5%	2m 52s
1.7%	2m 02s
1.7%	2m 08s
3.3%	1m 56s
1.6%	2m 02s
1.6%	1m 58s
1.6%	2m 02s
1.5%	2m 13s
4.8%	2m 05s
3.3%	1m 31s
4.8%	2m 09s
4.7%	1m 36s
4.8%	2m 16s
4.8%	2m 04s
4.8%	2m 05s
4.8%	2m 10s
4.8%	2m 04s
4.8%	2m 07s
1.5%	2m 47s
1.5%	2m 50s
3.0%	2m 07s
3.0%	2m 10s
4.4%	1m 42s
2.9%	2m 12s
2.9%	2m 12s
4.4%	2m 14s
3.1%	2m 15s
1.5%	2m 56s
2.9%	1m 47s
2.9%	2m 16s
1.5%	2m 47s
4.8%	2m 07s
2.9%	2m 14s
2.9%	2m 14s
2.9%	1m 32s
2.9%	2m 15s
1.5%	2m 48s
2.9%	1m 47s
2.9%	1m 46s
2.9%	2m 23s

Queue latency

median seconds

Show data

When	Push to queued	Queued to started
17 Aug 00:00	0m 02s	0m 00s
18 Aug 00:00	0m 02s	0m 00s

Average concurrency

time-weighted average of runs in flight per bucket, against the 30-slot budget

Show data

When	Avg concurrency
17 Aug 00:00	13.9
18 Aug 00:00	15.9

Push lag

time from the patch being posted to CI queueing it

Show data

When	Lag	Runs
17 Aug 00:00	same day	6
17 Aug 00:00	days	5
18 Aug 00:00	same day	29
18 Aug 00:00	days	61
18 Aug 00:00	weeks	172
18 Aug 00:00	months	674
18 Aug 00:00	older	940

Push kind

first push, a re-push on a newer master, or a retry of the same head

Show data

When	Kind	Runs
17 Aug 00:00	first push	6
17 Aug 00:00	rebase re-push	5
18 Aug 00:00	first push	384
18 Aug 00:00	rebase re-push	1,492

Suites failed per failing run

one suite is usually a patch bug; dozens is usually one crash cascading

Show data

Suites failed	Runs
1	67
2	13
3	6
4	48
5	13
6	3
7	7
8	2
9	1
10	2
11	3
12	2
21	1
29	1
33	1
58	1
59	1
62	1
68	1
76	1
83	1
107	1
122	1
129	1
132	1
157	1

Top failing suites

total failures, and in brackets the number of distinct patchsets - many failures on few patchsets means one broken patch retried; roughly one per patchset means either a flaky suite or a suite that reruns others and inherits their failures

recovery/027_stream_regress

80 (80 branches)

pg_upgrade/002_pg_upgrade

77 (77 branches)

test_plan_advice/001_replan_regress

74 (74 branches)

regress/partition_join

11 (11 branches)

regress/subselect

10 (10 branches)

postgres_fdw/postgres_fdw

9 (9 branches)

regress/alter_table

9 (9 branches)

regress/collate.icu.utf8

9 (9 branches)

regress/copy2

9 (9 branches)

isolation/horizons

8 (8 branches)

regress/generated_virtual

8 (8 branches)

regress/partition_split

8 (8 branches)

regress/plpgsql

8 (8 branches)

regress/predicate

8 (8 branches)

regress/stats

8 (8 branches)

regress/with

8 (8 branches)

isolation/eval-plan-qual

7 (7 branches)

regress/domain

7 (7 branches)

regress/explain

7 (7 branches)

regress/foreign_key

7 (7 branches)

Infra health

Everything here should be zero. Non-zero is worth a look, not a panic.

Condition	Count
infra errors	0
in flight past 48h	0
branches with a failed push	2
payloads we could not parse	0
runs with no payload	0
built but pushed no image	17

Retried heads

same head_sha pushed again, new run id

Verdict changed

0 of 0 - meaningless until this denominator grows

discussionsall active only

Tracked patchsets

5,828

current, not superseded, all patchsets

Median base age

932 days

behind master, all patchsets

On recent master

33.4%

base 30 days or newer, all patchsets

Has a verdict

88.9%

terminal CI status, all patchsets

Has a runnable image

85.4%

counted by digest, all patchsets

recent

1,949

base age tier, all patchsets

stale

398

base age tier, all patchsets

ancient

3,391

base age tier, all patchsets

unknown

base age tier, all patchsets

Master re-check recency

when each patchset was last tried against master; overdue is past 26h with master moved since. Unlike the base age tiles above, this follows the discussions control.

current

behind

378

overdue

112

never

Base age distribution

all current patchsets against those in active discussions

Show data

Base age	All	Active discussions
<1d	1,639	319
1-7d	65	55
7-30d	245	99
30-90d	62	16
90d-1y	336	10
1-2y	363	2
2-5y	1,000	0
>5y	2,028	1
unknown	90	10

Outcome by base commit year

current patchsets, by the year of the master commit they apply to

Show data

Base year	Outcome	Patchsets
unknown	never applied	10
2021	success	1
2025	success	2
2025	tests failed	1
2026	success	424
2026	cancelled	1
2026	tests failed	31
2026	build failed	6
2026	infra error	1
2026	no verdict	5
2026	never applied	30

Success rate by base commit year

of patchsets carrying a verdict

Show data

Base year	Success rate	With a verdict
2021	100.0%	1
2025	66.7%	3
2026	91.6%	465

Apply failures by base commit year

patchsets that would not apply even to their own detected base - a patch-extraction / base-detection signal, not a staleness measure; the rate is in the table

Show data

Base year	Patchsets	Failed to apply	Failure rate
unknown	10	10	100.0%
2021	1	0	0.0%
2025	3	0	0.0%
2026	498	30	6.0%

Build and test time over PostgreSQL history

median seconds of successful runs, by the base commit's year

Show data

Base year	Build median	Test median
2021	2m 17s	3m 02s
2025	2m 32s	5m 43s
2026	2m 53s	5m 21s

Test suites over PostgreSQL history

median executed suites of successful runs, by the base commit's year

Show data

Base year	Suites median
2021	623
2025	905
2026	1019

Per PostgreSQL major

A major whose era image is still a disabled stub is marked - those patchsets sit in won't-retry until the image exists.

PG	Era	Patchsets	Runs	Success	Build median	Test median	Suites	Images
15	bullseye	1	1	100.0%	2m 17s	3m 02s	623	1
19	trixie	16	15	80.0%	2m 47s	4m 45s	997	14
20	trixie	484	4,432	91.0%	2m 52s	5m 21s	1019	440

Files the corpus conflicts on

from apply-stage failures; in brackets the number of distinct patchsets

src/backend/utils/adt/float.c

3 (3 branches)

src/include/utils/float.h

3 (3 branches)

doc/src/sgml/release-18.sgml

2 (2 branches)

doc/src/sgml/release-19.sgml

2 (2 branches)

src/backend/commands/publicationcmds.c

2 (2 branches)

contrib/pg_buffercache/pg_buffercache_pages.c

1 (1 branches)

doc/src/sgml/perform.sgml

1 (1 branches)

doc/src/sgml/protocol.sgml

1 (1 branches)

doc/src/sgml/ref/explain.sgml

1 (1 branches)

src/backend/access/common/reloptions.c

1 (1 branches)

src/backend/access/common/toast_internals.c

1 (1 branches)

src/backend/access/heap/heapam.c

1 (1 branches)

src/backend/access/table/toast_helper.c

1 (1 branches)

src/backend/optimizer/path/allpaths.c

1 (1 branches)

src/backend/optimizer/path/joinpath.c

1 (1 branches)

src/backend/optimizer/plan/subselect.c

1 (1 branches)

src/backend/optimizer/prep/prepjointree.c

1 (1 branches)

src/backend/optimizer/util/pathnode.c

1 (1 branches)

src/backend/postmaster/checkpointer.c

1 (1 branches)

src/backend/replication/logical/relation.c

1 (1 branches)

Verdict coverage in active discussions

patchsets in threads with a message in the last 30 days

Show data

Era	With a verdict	No verdict
bullseye	1	0
trixie	468	32
unknown	0	11

Patch size against outcome

files touched per patchset, from the recorded submission paths

Show data

Files touched	Outcome	Patchsets
unknown	success	427
unknown	cancelled	1
unknown	tests failed	32
unknown	build failed	6
unknown	infra error	1
unknown	no verdict	5
unknown	never applied	40

Patchset versions per topic

every version, superseded included; split by whether the topic was committed

Show data

Versions	Topic	Topics
1	not committed	4,981
1	committed	534
2	not committed	157
2	committed	36
3	not committed	46
3	committed	8
4	not committed	14
4	committed	5
5	committed	2
5	not committed	8
6	committed	1
6	not committed	5
7	not committed	4
8	not committed	2
10	committed	1
11	not committed	1

Why the orchestrator won't retry

The dashboard shows the top three of this same breakdown.

Reason	Patchsets
base too old	3,249
committed	118
patchset touches .github/	11

Navigation

Patch CI statistics

Runs by result

Success rate

Build and test duration by era

ccache hit rate

Build time against ccache hit rate

Queue latency

Average concurrency

Push lag

Push kind

Suites failed per failing run

Top failing suites

Infra health

Master re-check recency

Base age distribution

Outcome by base commit year

Success rate by base commit year

Apply failures by base commit year

Build and test time over PostgreSQL history

Test suites over PostgreSQL history

Per PostgreSQL major

Files the corpus conflicts on

Verdict coverage in active discussions

Patch size against outcome

Patchset versions per topic

Why the orchestrator won't retry