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,739

terminal, in range

Success rate

85.5%

1,487 of 1,739

Median build

2m 50s

successful and failed alike

Median test

5m 15s

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 15:00	success	3
17 Aug 16:00	success	8
17 Aug 16:00	tests failed	1
17 Aug 17:00	success	1
17 Aug 18:00	success	1
17 Aug 20:00	success	1
17 Aug 22:00	success	1
17 Aug 23:00	success	3
18 Aug 00:00	build failed	2
18 Aug 00:00	success	95
18 Aug 00:00	tests failed	11
18 Aug 01:00	build failed	8
18 Aug 01:00	success	101
18 Aug 01:00	tests failed	6
18 Aug 02:00	build failed	6
18 Aug 02:00	success	91
18 Aug 02:00	tests failed	9
18 Aug 03:00	build failed	11
18 Aug 03:00	success	102
18 Aug 03:00	tests failed	12
18 Aug 04:00	build failed	3
18 Aug 04:00	success	95
18 Aug 04:00	tests failed	15
18 Aug 05:00	build failed	3
18 Aug 05:00	success	106
18 Aug 05:00	tests failed	14
18 Aug 06:00	build failed	2
18 Aug 06:00	success	100
18 Aug 06:00	tests failed	9
18 Aug 07:00	build failed	9
18 Aug 07:00	success	77
18 Aug 07:00	tests failed	10
18 Aug 08:00	build failed	4
18 Aug 08:00	success	94
18 Aug 08:00	tests failed	12
18 Aug 09:00	build failed	1
18 Aug 09:00	success	92
18 Aug 09:00	tests failed	14
18 Aug 10:00	build failed	4
18 Aug 10:00	success	89
18 Aug 10:00	tests failed	21
18 Aug 11:00	build failed	8
18 Aug 11:00	success	87
18 Aug 11:00	tests failed	19
18 Aug 12:00	build failed	4
18 Aug 12:00	success	108
18 Aug 12:00	tests failed	6
18 Aug 13:00	build failed	2
18 Aug 13:00	success	87
18 Aug 13:00	tests failed	9
18 Aug 14:00	build failed	5
18 Aug 14:00	success	111
18 Aug 14:00	tests failed	8
18 Aug 15:00	build failed	2
18 Aug 15:00	success	34
18 Aug 15:00	tests failed	2

Success rate

hollow points sit below 5 terminal runs in the bucket

Show data

When	Success rate	Terminal runs
17 Aug 15:00	100.0%	3
17 Aug 16:00	88.9%	9
17 Aug 17:00	100.0%	1
17 Aug 18:00	100.0%	1
17 Aug 20:00	100.0%	1
17 Aug 22:00	100.0%	1
17 Aug 23:00	100.0%	3
18 Aug 00:00	88.0%	108
18 Aug 01:00	87.8%	115
18 Aug 02:00	85.8%	106
18 Aug 03:00	81.6%	125
18 Aug 04:00	84.1%	113
18 Aug 05:00	86.2%	123
18 Aug 06:00	90.1%	111
18 Aug 07:00	80.2%	96
18 Aug 08:00	85.5%	110
18 Aug 09:00	86.0%	107
18 Aug 10:00	78.1%	114
18 Aug 11:00	76.3%	114
18 Aug 12:00	91.5%	118
18 Aug 13:00	88.8%	98
18 Aug 14:00	89.5%	124
18 Aug 15:00	89.5%	38

Build and test duration by era

median seconds; successful runs only

Show data

When	Era	Build median	Test median	Build p25-p75
18 Aug 15:00	bookworm	2m 54s	3m 35s	2m 50s - 3m 07s
17 Aug 15:00	trixie	2m 49s	5m 31s	2m 49s - 2m 53s
17 Aug 16:00	trixie	2m 50s	5m 19s	2m 49s - 2m 54s
17 Aug 17:00	trixie	3m 01s	5m 44s	3m 01s - 3m 01s
17 Aug 18:00	trixie	2m 49s	5m 06s	2m 49s - 2m 49s
17 Aug 20:00	trixie	2m 12s	3m 46s	2m 12s - 2m 12s
17 Aug 22:00	trixie	2m 49s	5m 29s	2m 49s - 2m 49s
17 Aug 23:00	trixie	2m 52s	5m 24s	2m 50s - 2m 55s
18 Aug 00:00	trixie	2m 47s	5m 14s	2m 37s - 2m 53s
18 Aug 01:00	trixie	2m 49s	5m 16s	2m 32s - 2m 56s
18 Aug 02:00	trixie	2m 50s	5m 19s	2m 45s - 2m 55s
18 Aug 03:00	trixie	2m 52s	5m 19s	2m 46s - 2m 55s
18 Aug 04:00	trixie	2m 52s	5m 16s	2m 34s - 2m 55s
18 Aug 05:00	trixie	2m 52s	5m 19s	2m 43s - 2m 55s
18 Aug 06:00	trixie	2m 53s	5m 19s	2m 47s - 2m 56s
18 Aug 07:00	trixie	2m 52s	5m 18s	2m 46s - 2m 55s
18 Aug 08:00	trixie	2m 52s	5m 17s	2m 26s - 2m 55s
18 Aug 09:00	trixie	2m 51s	5m 20s	2m 47s - 2m 56s
18 Aug 10:00	trixie	2m 52s	5m 21s	2m 47s - 2m 55s
18 Aug 11:00	trixie	2m 52s	5m 18s	2m 48s - 2m 55s
18 Aug 12:00	trixie	2m 52s	5m 23s	2m 47s - 2m 56s
18 Aug 13:00	trixie	2m 48s	5m 21s	2m 39s - 2m 55s
18 Aug 14:00	trixie	2m 48s	4m 44s	2m 39s - 2m 53s
18 Aug 15:00	trixie	2m 48s	5m 10s	2m 41s - 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 15:00	1.5%	3
17 Aug 16:00	1.5%	8
17 Aug 17:00	1.5%	1
17 Aug 18:00	1.5%	1
17 Aug 20:00	1.5%	1
17 Aug 22:00	1.5%	1
17 Aug 23:00	1.5%	3
18 Aug 00:00	1.5%	95
18 Aug 01:00	1.5%	101
18 Aug 02:00	1.5%	91
18 Aug 03:00	1.5%	102
18 Aug 04:00	1.5%	95
18 Aug 05:00	1.5%	106
18 Aug 06:00	1.5%	100
18 Aug 07:00	1.5%	77
18 Aug 08:00	1.5%	94
18 Aug 09:00	1.5%	92
18 Aug 10:00	1.5%	89
18 Aug 11:00	1.5%	87
18 Aug 12:00	1.5%	108
18 Aug 13:00	1.5%	87
18 Aug 14:00	1.5%	111
18 Aug 15:00	1.6%	34

Build time against ccache hit rate

one point per successful run; table shows the first 50

Show data

Hit rate	Build
1.5%	2m 47s
1.5%	2m 48s
4.7%	2m 51s
4.7%	2m 50s
1.5%	2m 55s
4.7%	2m 54s
4.7%	2m 51s
4.7%	3m 04s
1.5%	2m 41s
4.7%	2m 52s
4.7%	2m 52s
1.5%	2m 48s
4.7%	1m 53s
10.5%	2m 48s
1.5%	2m 56s
1.5%	1m 58s
34.7%	0m 43s
1.7%	3m 08s
17.2%	2m 22s
1.5%	2m 55s
1.6%	2m 20s
1.6%	2m 55s
1.6%	3m 11s
1.6%	3m 09s
1.6%	3m 10s
1.6%	3m 07s
1.6%	2m 59s
1.5%	2m 25s
1.5%	2m 53s
1.6%	3m 07s
1.6%	2m 54s
1.6%	3m 09s
1.5%	3m 02s
1.2%	2m 39s
1.2%	2m 40s
1.5%	2m 48s
1.2%	2m 37s
1.5%	2m 21s
1.2%	2m 48s
1.5%	2m 54s
1.3%	2m 49s
1.3%	2m 49s
1.3%	2m 50s
1.3%	1m 45s
1.3%	1m 49s
1.5%	2m 55s
1.3%	2m 37s
1.3%	2m 38s
1.5%	2m 56s
1.5%	2m 46s

Queue latency

median seconds

Show data

When	Push to queued	Queued to started
17 Aug 15:00	0m 01s	0m 00s
17 Aug 16:00	0m 02s	0m 00s
17 Aug 17:00	0m 02s	0m 00s
17 Aug 18:00	0m 02s	0m 00s
17 Aug 20:00	0m 02s	0m 00s
17 Aug 22:00	0m 02s	0m 00s
17 Aug 23:00	0m 01s	0m 00s
18 Aug 00:00	0m 01s	0m 00s
18 Aug 01:00	0m 02s	0m 00s
18 Aug 02:00	0m 01s	0m 00s
18 Aug 03:00	0m 01s	0m 00s
18 Aug 04:00	0m 01s	0m 00s
18 Aug 05:00	0m 01s	0m 00s
18 Aug 06:00	0m 01s	0m 00s
18 Aug 07:00	0m 02s	0m 00s
18 Aug 08:00	0m 02s	0m 00s
18 Aug 09:00	0m 01s	0m 00s
18 Aug 10:00	0m 01s	0m 00s
18 Aug 11:00	0m 01s	0m 00s
18 Aug 12:00	0m 02s	0m 00s
18 Aug 13:00	0m 02s	0m 00s
18 Aug 14:00	0m 02s	0m 00s
18 Aug 15: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 15:00	1.3
17 Aug 16:00	1.3
17 Aug 17:00	0.2
17 Aug 18:00	0.2
17 Aug 19:00	0.0
17 Aug 20:00	0.1
17 Aug 21:00	0.0
17 Aug 22:00	0.2
17 Aug 23:00	0.9
18 Aug 00:00	24.3
18 Aug 01:00	23.5
18 Aug 02:00	23.6
18 Aug 03:00	25.6
18 Aug 04:00	25.2
18 Aug 05:00	24.3
18 Aug 06:00	21.8
18 Aug 07:00	18.8
18 Aug 08:00	20.7
18 Aug 09:00	22.0
18 Aug 10:00	22.5
18 Aug 11:00	23.9
18 Aug 12:00	22.0
18 Aug 13:00	24.3
18 Aug 14:00	24.0
18 Aug 15:00	7.8

Push lag

time from the patch being posted to CI queueing it

Show data

When	Lag	Runs
17 Aug 15:00	days	3
17 Aug 16:00	same day	1
17 Aug 16:00	days	7
17 Aug 16:00	weeks	1
17 Aug 17:00	same day	1
17 Aug 18:00	same day	1
17 Aug 20:00	same day	1
17 Aug 22:00	same day	1
17 Aug 23:00	same day	2
17 Aug 23:00	days	1
18 Aug 00:00	same day	1
18 Aug 00:00	days	17
18 Aug 00:00	weeks	5
18 Aug 00:00	months	77
18 Aug 00:00	older	8
18 Aug 01:00	same day	2
18 Aug 01:00	days	2
18 Aug 01:00	weeks	3
18 Aug 01:00	months	108
18 Aug 02:00	days	1
18 Aug 02:00	weeks	3
18 Aug 02:00	months	82
18 Aug 02:00	older	20
18 Aug 03:00	days	3
18 Aug 03:00	weeks	3
18 Aug 03:00	older	119
18 Aug 04:00	same day	1
18 Aug 04:00	days	3
18 Aug 04:00	weeks	5
18 Aug 04:00	older	104
18 Aug 05:00	same day	2
18 Aug 05:00	weeks	54
18 Aug 05:00	months	29
18 Aug 05:00	older	38
18 Aug 06:00	days	7
18 Aug 06:00	weeks	5
18 Aug 06:00	months	99
18 Aug 07:00	same day	1
18 Aug 07:00	days	4
18 Aug 07:00	weeks	3
18 Aug 07:00	months	31
18 Aug 07:00	older	57
18 Aug 08:00	same day	3
18 Aug 08:00	days	9
18 Aug 08:00	weeks	38
18 Aug 08:00	months	29
18 Aug 08:00	older	31
18 Aug 09:00	same day	2
18 Aug 09:00	days	1
18 Aug 09:00	weeks	4
18 Aug 09:00	months	32
18 Aug 09:00	older	68
18 Aug 10:00	same day	5
18 Aug 10:00	days	1
18 Aug 10:00	weeks	6
18 Aug 10:00	older	102
18 Aug 11:00	same day	1
18 Aug 11:00	days	2
18 Aug 11:00	weeks	8
18 Aug 11:00	older	103
18 Aug 12:00	same day	1
18 Aug 12:00	days	4
18 Aug 12:00	weeks	14
18 Aug 12:00	months	57
18 Aug 12:00	older	42
18 Aug 13:00	same day	5
18 Aug 13:00	days	7
18 Aug 13:00	weeks	21
18 Aug 13:00	months	65
18 Aug 14:00	same day	3
18 Aug 14:00	months	65
18 Aug 14:00	older	56
18 Aug 15:00	older	38

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 15:00	rebase re-push	3
17 Aug 16:00	first push	1
17 Aug 16:00	rebase re-push	8
17 Aug 17:00	first push	1
17 Aug 18:00	first push	1
17 Aug 20:00	first push	1
17 Aug 22:00	first push	1
17 Aug 23:00	first push	2
17 Aug 23:00	rebase re-push	1
18 Aug 00:00	first push	1
18 Aug 00:00	rebase re-push	107
18 Aug 01:00	first push	2
18 Aug 01:00	rebase re-push	113
18 Aug 02:00	rebase re-push	106
18 Aug 03:00	rebase re-push	125
18 Aug 04:00	first push	1
18 Aug 04:00	rebase re-push	112
18 Aug 05:00	first push	2
18 Aug 05:00	rebase re-push	121
18 Aug 06:00	rebase re-push	111
18 Aug 07:00	first push	1
18 Aug 07:00	rebase re-push	95
18 Aug 08:00	first push	3
18 Aug 08:00	rebase re-push	107
18 Aug 09:00	first push	2
18 Aug 09:00	rebase re-push	105
18 Aug 10:00	first push	5
18 Aug 10:00	rebase re-push	109
18 Aug 11:00	first push	1
18 Aug 11:00	rebase re-push	113
18 Aug 12:00	first push	1
18 Aug 12:00	rebase re-push	117
18 Aug 13:00	first push	47
18 Aug 13:00	rebase re-push	51
18 Aug 14:00	first push	124
18 Aug 15:00	first push	38

Suites failed per failing run

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

Show data

Suites failed	Runs
1	61
2	9
3	4
4	48
5	13
6	2
7	7
8	2
10	2
11	3
12	2
21	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

75 (75 branches)

test_plan_advice/001_replan_regress

74 (74 branches)

regress/partition_join

10 (10 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	18

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,628

current, not superseded, all patchsets

Median base age

860 days

behind master, all patchsets

On recent master

34.2%

base 30 days or newer, all patchsets

Has a verdict

89.3%

terminal CI status, all patchsets

Has a runnable image

85.7%

counted by digest, all patchsets

recent

1,926

base age tier, all patchsets

stale

398

base age tier, all patchsets

ancient

3,226

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

381

overdue

109

never

Base age distribution

all current patchsets against those in active discussions

Show data

Base age	All	Active discussions
<1d	1,616	318
1-7d	65	55
7-30d	245	99
30-90d	62	16
90d-1y	336	10
1-2y	363	2
2-5y	937	0
>5y	1,926	1
unknown	78	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	422
2026	cancelled	1
2026	tests failed	31
2026	build failed	6
2026	infra error	1
2026	no verdict	6
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%	463

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	497	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	483	4,430	91.0%	2m 52s	5m 21s	1019	438

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	466	33
unknown	0	11

Patch size against outcome

files touched per patchset, from the recorded submission paths

Show data

Files touched	Outcome	Patchsets
unknown	success	425
unknown	cancelled	1
unknown	tests failed	32
unknown	build failed	6
unknown	infra error	1
unknown	no verdict	6
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,980
1	committed	335
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,118
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