pgstat: allow a stats kind to use its own dedicated dsa/dshash

back to CI dashboard

1 patchset tracked - current t253087_1

v1t253087_1posted Jul 15, 17:16successwon't retrystale 44dpg 20
base44056f649 Aug 07, 03:30 on master
applyapplied Aug 07, 04:02
rebaselast tried Sep 05, 07:09 on 798bdcae8
Applying: pgstat: allow a stats kind to use its own dedicated dshash
Using index info to reconstruct a base tree...
M	src/backend/utils/activity/pgstat.c
M	src/backend/utils/activity/pgstat_shmem.c
M	src/include/utils/pgstat_internal.h
M	src/test/modules/test_custom_stats/test_custom_var_stats.c
Falling back to patching base and 3-way merge...
Auto-merging src/test/modules/test_custom_stats/test_custom_var_stats.c
Auto-merging src/include/utils/pgstat_internal.h
Auto-merging src/backend/utils/activity/pgstat_shmem.c
CONFLICT (content): Merge conflict in src/backend/utils/activity/pgstat_shmem.c
Auto-merging src/backend/utils/activity/pgstat.c
Patch failed at 0001 pgstat: allow a stats kind to use its own dedicated dshash

error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
conflicts on master: src/backend/utils/activity/pgstat_shmem.c
pushAug 07, 04:02 -> 3552ceaabbranchdiff vs base
ResultAttPGTestsBuild / testImageWhen
success1201018 / 10182m 47s / 5m 22sdocker run ... :t253087Aug 07, 04:14
run 31146180850
executed 1018 - ccache 166 hit / 6452 miss - head 3552ceaab - digest sha256:657cb5568a00a9... - run 31146180850
success1201018 / 10182m 55s / 5m 35sdocker run ... @sha256:74a84a6...Aug 05, 22:53
run 31053729597
executed 1018 - ccache 166 hit / 6452 miss - head 7f88c155b - digest sha256:74a84a665d52f4... - run 31053729597
success1201018 / 10182m 45s / 4m 41sdocker run ... @sha256:0864f64...Aug 04, 22:50
run 30957264392
executed 1018 - ccache 166 hit / 6452 miss - head 0962a090f - digest sha256:0864f64480ca8f... - run 30957264392
success1201018 / 10182m 49s / 5m 26sdocker run ... @sha256:6d393cd...Aug 03, 22:49
run 30859452904
executed 1018 - ccache 166 hit / 6452 miss - head d5a26b59c - digest sha256:6d393cd8e3bd03... - run 30859452904
success1201017 / 10172m 52s / 5m 08sdocker run ... @sha256:fdc82d7...Aug 02, 22:48
run 30770529347
executed 1017 - ccache 166 hit / 6452 miss - head e483e9407 - digest sha256:fdc82d796307f9... - run 30770529347
success1201017 / 10172m 58s / 5m 08sdocker run ... @sha256:a4fe54e...Aug 01, 22:47
run 30721650621
executed 1017 - ccache 166 hit / 6452 miss - head 5b85ec708 - digest sha256:a4fe54e732b34c... - run 30721650621
success1201017 / 10172m 45s / 5m 16sdocker run ... @sha256:f50caeb...Jul 31, 22:46
run 30670456452
executed 1017 - ccache 166 hit / 6452 miss - head 0f82f9a0f - digest sha256:f50caebebdd5ab... - run 30670456452
tests failed1201015 / 10162m 55s / 5m 28sdocker run ... @sha256:ee7763c...Jul 30, 22:45
run 30587624045
failed: recovery/051_effective_wal_level
executed 1016 - ccache 166 hit / 6452 miss - head b98bb0904 - digest sha256:ee7763c3edf4e2... - run 30587624045
success1201016 / 10162m 59s / 5m 22sdocker run ... @sha256:ebba16d...Jul 29, 22:43
run 30496533182
executed 1016 - ccache 166 hit / 6452 miss - head 4fa261557 - digest sha256:ebba16d2280b88... - run 30496533182
success1201015 / 10152m 53s / 5m 34sdocker run ... @sha256:34d058f...Jul 28, 22:44
run 30404924030
executed 1015 - ccache 166 hit / 6452 miss - head 3269ae31b - digest sha256:34d058ff76e1ca... - run 30404924030