[PATCH] Memory leak in pg_config
1 patchset tracked - current t39673_1
v1t39673_1posted Nov 14, 2018successwon't retrystale 56dpg 20
basee395fbd32 Jul 25, 21:13 on master
applyapplied Jul 26, 07:31
rebaselast tried Aug 24, 08:03 on 9673a0aa9
Applying: pg_config: Avoid leaking configdata Using index info to reconstruct a base tree... M src/backend/utils/misc/pg_config.c M src/bin/pg_config/pg_config.c M src/common/config_info.c M src/include/common/config_info.h Falling back to patching base and 3-way merge... Auto-merging src/include/common/config_info.h Auto-merging src/common/config_info.c Auto-merging src/bin/pg_config/pg_config.c Auto-merging src/backend/utils/misc/pg_config.c CONFLICT (content): Merge conflict in src/backend/utils/misc/pg_config.c Patch failed at 0001 pg_config: Avoid leaking configdata 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/misc/pg_config.c
pushJul 27, 19:43 -> aeef53d10branchdiff vs base
| Result | Att | PG | Tests | Build / test | Image | When |
|---|---|---|---|---|---|---|
| success | 1 | 20 | 1013 / 1013 | 2m 50s / 4m 48s | docker run ... :t39673 | Jul 27, 19:57 |
run 30299462866executed 1013 - ccache 166 hit / 6452 miss - head aeef53d10 - digest sha256:ddf672136a288b... - run 30299462866 | ||||||