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

10,781

terminal, in range

Success rate

84.6%

9,126 of 10,781

Median build

2m 52s

successful and failed alike

Median test

5m 18s

successful and failed alike

Median queue wait

0m 00s

queued to started

Infra errors

0.1%

7 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
10 Aug 00:00	build failed	327
10 Aug 00:00	cancelled	6
10 Aug 00:00	infra error	7
10 Aug 00:00	success	6,466
10 Aug 00:00	tests failed	843
17 Aug 00:00	build failed	134
17 Aug 00:00	success	2,660
17 Aug 00:00	tests failed	338

Success rate

hollow points sit below 5 terminal runs in the bucket

Show data

When	Success rate	Terminal runs
10 Aug 00:00	84.5%	7,649
17 Aug 00:00	84.9%	3,132

Build and test duration by era

median seconds; successful runs only

Show data

When	Era	Build median	Test median	Build p25-p75
10 Aug 00:00	trixie	2m 53s	5m 21s	2m 47s - 2m 55s
17 Aug 00:00	trixie	2m 52s	5m 19s	2m 46s - 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
10 Aug 00:00	2.5%	6,466
17 Aug 00:00	1.5%	2,660

Build time against ccache hit rate

one point per successful run; table shows the first 50

Show data

Hit rate	Build
1.5%	2m 57s
1.5%	2m 58s
1.2%	2m 52s
1.3%	2m 08s
1.5%	2m 57s
1.5%	2m 58s
1.5%	2m 55s
1.5%	2m 55s
1.5%	2m 45s
1.2%	2m 48s
1.5%	2m 50s
1.5%	2m 52s
1.2%	2m 52s
1.2%	2m 51s
1.5%	1m 58s
1.5%	2m 47s
1.5%	2m 45s
1.5%	2m 58s
1.5%	2m 57s
2.2%	2m 49s
1.5%	2m 48s
1.5%	2m 50s
1.5%	2m 49s
1.5%	2m 11s
1.5%	2m 53s
1.5%	2m 50s
1.5%	2m 49s
2.2%	1m 53s
2.2%	3m 01s
2.2%	2m 44s
1.5%	2m 52s
1.5%	2m 55s
2.2%	1m 56s
2.2%	2m 46s
1.5%	3m 00s
1.5%	2m 56s
9.2%	2m 38s
1.5%	2m 58s
9.4%	1m 46s
2.2%	2m 30s
1.5%	2m 55s
9.3%	2m 38s
9.2%	1m 47s
1.5%	2m 11s
23.5%	0m 54s
1.5%	2m 55s
1.2%	2m 29s
1.5%	2m 53s
1.5%	3m 01s
1.5%	2m 50s

Queue latency

median seconds

Show data

When	Push to queued	Queued to started
10 Aug 00:00	-5767m 28s	0m 00s
17 Aug 00:00	0m 01s	0m 00s

Average concurrency

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

Show data

When	Avg concurrency
10 Aug 00:00	13.2
17 Aug 00:00	3.9

Push lag

time from the patch being posted to CI queueing it

Show data

When	Lag	Runs
10 Aug 00:00	same day	124
10 Aug 00:00	days	379
10 Aug 00:00	weeks	782
10 Aug 00:00	months	2,898
10 Aug 00:00	older	3,466
17 Aug 00:00	same day	59
17 Aug 00:00	days	132
17 Aug 00:00	weeks	334
17 Aug 00:00	months	1,221
17 Aug 00:00	older	1,386

Push kind

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

Show data

When	Kind	Runs
10 Aug 00:00	first push	126
10 Aug 00:00	rebase re-push	7,519
10 Aug 00:00	retry	4
17 Aug 00:00	first push	122
17 Aug 00:00	rebase re-push	3,010

Suites failed per failing run

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

Show data

Suites failed	Runs
1	394
2	55
3	27
4	348
5	74
6	18
7	46
8	17
9	6
10	7
11	12
12	11
13	4
21	7
31	1
33	7
55	1
56	1
58	6
59	7
62	7
76	7
83	7
102	3
107	4
111	1
122	6
123	1
129	6
131	3
132	1
133	1
140	1
155	3
156	1
157	2
158	2
200	3

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

561 (90 branches)

test_plan_advice/001_replan_regress

520 (80 branches)

pg_upgrade/002_pg_upgrade

510 (81 branches)

regress/collate.icu.utf8

69 (15 branches)

regress/subselect

67 (13 branches)

regress/partition_join

61 (14 branches)

postgres_fdw/postgres_fdw

60 (9 branches)

regress/alter_table

59 (11 branches)

regress/copy2

59 (11 branches)

regress/join

58 (12 branches)

regress/partition_split

58 (10 branches)

isolation/horizons

57 (9 branches)

regress/generated_virtual

54 (10 branches)

regress/stats

53 (11 branches)

regress/plpgsql

51 (9 branches)

regress/predicate

51 (9 branches)

regress/with

51 (9 branches)

isolation/eval-plan-qual

50 (8 branches)

regress/aggregates

49 (10 branches)

regress/opr_sanity

46 (8 branches)

Infra health

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

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

Retried heads

same head_sha pushed again, new run id

Verdict changed

100.0%

4 of 4 - meaningless until this denominator grows

discussionsall active only

Tracked patchsets

5,463

current, not superseded, all patchsets

Median base age

897 days

behind master, all patchsets

On recent master

34.5%

base 30 days or newer, all patchsets

Has a verdict

89.4%

terminal CI status, all patchsets

Has a runnable image

86.1%

counted by digest, all patchsets

recent

1,885

base age tier, all patchsets

stale

394

base age tier, all patchsets

ancient

3,123

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

1,670

overdue

292

never

3,449

Base age distribution

all current patchsets against those in active discussions

Show data

Base age	All	Active discussions
<1d	1,575	318
1-7d	65	55
7-30d	245	99
30-90d	62	16
90d-1y	332	10
1-2y	320	2
2-5y	878	0
>5y	1,925	1
unknown	61	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	61
2012	build failed	1
2014	never applied	1
2015	build failed	3
2015	never applied	3
2016	success	22
2016	tests failed	2
2016	never applied	2
2017	success	463
2017	tests failed	58
2017	build failed	14
2017	never applied	63
2018	success	281
2018	tests failed	38
2018	build failed	7
2018	never applied	60
2019	success	244
2019	tests failed	23
2019	build failed	10
2019	never applied	74
2020	success	232
2020	tests failed	34
2020	build failed	4
2020	never applied	52
2021	success	241
2021	tests failed	35
2021	build failed	9
2021	never applied	35
2022	success	242
2022	cancelled	1
2022	tests failed	36
2022	build failed	11
2022	never applied	36
2023	success	220
2023	tests failed	26
2023	build failed	9
2023	never applied	32
2024	success	205
2024	tests failed	36
2024	build failed	8
2024	infra error	1
2024	never applied	23
2025	success	260
2025	tests failed	43
2025	build failed	13
2025	infra error	1
2025	no verdict	7
2025	never applied	36
2026	success	1,659
2026	cancelled	1
2026	tests failed	206
2026	build failed	76
2026	infra error	2
2026	no verdict	36
2026	never applied	165

Success rate by base commit year

of patchsets carrying a verdict

Show data

Base year	Success rate	With a verdict
2012	0.0%	1
2015	0.0%	3
2016	91.7%	24
2017	86.5%	535
2018	86.2%	326
2019	88.1%	277
2020	85.9%	270
2021	84.6%	285
2022	83.4%	290
2023	86.3%	255
2024	82.0%	250
2025	82.0%	317
2026	86.1%	2,052

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	61	61	100.0%
2012	1	0	0.0%
2014	1	1	100.0%
2015	6	3	50.0%
2016	26	2	7.7%
2017	598	63	10.5%
2018	386	60	15.5%
2019	351	74	21.1%
2020	322	52	16.1%
2021	320	35	10.9%
2022	326	36	11.0%
2023	287	32	11.1%
2024	273	23	8.4%
2025	360	36	10.0%
2026	2,145	165	7.7%

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
2016	1m 41s	3m 18s
2017	1m 46s	4m 37s
2018	1m 50s	2m 38s
2019	1m 55s	2m 35s
2020	2m 00s	2m 52s
2021	2m 11s	3m 09s
2022	2m 14s	3m 58s
2023	2m 51s	3m 58s
2024	2m 43s	3m 39s
2025	2m 45s	4m 26s
2026	2m 52s	5m 20s

Test suites over PostgreSQL history

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

Show data

Base year	Suites median
2016	412
2017	451
2018	505
2019	537
2020	566
2021	621
2022	654
2023	777
2024	833
2025	900
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
9	stretch	13	13	61.5%	1m 34s	2m 41s	398	9
10	stretch	404	405	87.9%	1m 45s	5m 20s	443	392
11	stretch	347	348	87.1%	1m 48s	2m 35s	476	339
12	buster	275	275	86.9%	1m 51s	2m 35s	513	267
13	buster	273	273	84.6%	1m 57s	2m 37s	548	267
14	bullseye	290	292	86.3%	2m 08s	3m 06s	590	284
15	bullseye	279	281	86.5%	2m 11s	3m 18s	625	268
16	bookworm	269	268	82.8%	2m 46s	4m 12s	669	256
17	bookworm	250	250	84.4%	2m 54s	3m 27s	793	244
18	trixie	280	281	79.0%	2m 41s	3m 50s	858	267
19	trixie	373	351	86.3%	2m 49s	4m 42s	937	339
20	trixie	1,906	30,902	83.6%	2m 52s	5m 18s	1018	1,769

Files the corpus conflicts on

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

src/bin/pgbench/pgbench.c

11 (11 branches)

doc/src/sgml/ref/pgbench.sgml

10 (10 branches)

src/bin/pgbench/t/001_pgbench_with_server.pl

6 (6 branches)

src/backend/access/transam/xlog.c

5 (5 branches)

src/backend/parser/gram.y

5 (5 branches)

src/bin/pg_dump/pg_dump.c

5 (5 branches)

doc/src/sgml/config.sgml

4 (4 branches)

src/backend/access/common/reloptions.c

4 (4 branches)

src/backend/commands/tablecmds.c

4 (4 branches)

src/backend/postmaster/autovacuum.c

4 (4 branches)

src/include/utils/float.h

4 (4 branches)

templates/pages/about/policies/coc/ja.html

4 (4 branches)

configure.in

3 (3 branches)

doc/src/sgml/perform.sgml

3 (3 branches)

doc/src/sgml/ref/psql-ref.sgml

3 (3 branches)

doc/src/sgml/ref/select.sgml

3 (3 branches)

doc/src/sgml/release-19.sgml

3 (3 branches)

indent.c

3 (3 branches)

run_build.pl

3 (3 branches)

src/backend/commands/indexcmds.c

3 (3 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	4,069
unknown	cancelled	2
unknown	tests failed	537
unknown	build failed	165
unknown	infra error	4
unknown	no verdict	43
unknown	never applied	643

Patchset versions per topic

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

Show data

Versions	Topic	Topics
1	not committed	4,979
1	committed	171
2	not committed	158
2	committed	36
3	not committed	45
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,032
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