Shared buffer access rule violations?

back to CI dashboard

1 patchset tracked - current t39038_5

v5t39038_5posted Aug 08, 2018successwon't retryancient 8ypg 12
base130beba36 Jul 13, 2018 - 2990 days / 20151 commits behind master (from history)
applyapplied Aug 18, 16:40
rebaselast tried Aug 18, 16:40 on 195e8e427
Applying: Facility to detect shared buffer access violations
Using index info to reconstruct a base tree...
M	src/backend/storage/buffer/buf_init.c
M	src/backend/storage/buffer/bufmgr.c
M	src/backend/storage/ipc/shmem.c
Falling back to patching base and 3-way merge...
Auto-merging src/backend/storage/ipc/shmem.c
CONFLICT (content): Merge conflict in src/backend/storage/ipc/shmem.c
Auto-merging src/backend/storage/buffer/bufmgr.c
CONFLICT (content): Merge conflict in src/backend/storage/buffer/bufmgr.c
Auto-merging src/backend/storage/buffer/buf_init.c
CONFLICT (content): Merge conflict in src/backend/storage/buffer/buf_init.c
Patch failed at 0001 Facility to detect shared buffer access violations

/ci/repo/worktrees/worktree/rebase-apply/patch:298: indent with spaces.
    BufferMProtect(buf, forInput ? PROT_WRITE|PROT_READ : PROT_READ);
warning: 1 line adds whitespace errors.
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/storage/ipc/shmem.c, src/backend/storage/buffer/bufmgr.c, src/backend/storage/buffer/buf_init.c
pushAug 18, 16:40 -> 9fc2373e8branchdiff vs base
ResultAttPGTestsBuild / testImageWhen
success112509 / 5091m 47s / 2m 39sdocker run ... :t39038Aug 18, 16:48
run 32161586592
executed 509 - ccache 84 hit / 3975 miss - head 9fc2373e8 - digest sha256:3231d8dcd11209... - run 32161586592