summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/elfutils
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2019-06-06 19:33:02 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2019-06-07 09:10:34 +0100
commitc7e131a76e522503df55e211dd261829feacfa28 (patch)
treee24903a723fdac17fe7ba36eaf753f547b585b6d /meta/recipes-devtools/elfutils
parent4059d8eedc5cf6f46a834997b7120150fcec4c0e (diff)
downloadopenembedded-core-c7e131a76e522503df55e211dd261829feacfa28.tar.gz
openembedded-core-c7e131a76e522503df55e211dd261829feacfa28.tar.bz2
openembedded-core-c7e131a76e522503df55e211dd261829feacfa28.zip
gpg_sign/selftest: Fix secmem parameter handling
We keep seeing "cannot allocate memory" errors from rpm when signing packages on the autobuilder. The following were tried: * checking locked memory use (isn't hitting limits) * Restricting RPM_GPG_SIGN_CHUNK to 1 * Limiting to 10 parallel do_package_write_rpm tasks * Allowing unlimied memory overcommit * Disabling rpm parallel compression and the test still failed. Further invetigation showed that the --auto-expand-secmem wasn't being passed to gpg-agent which meant the secmem couldn't be expanded hence the errors when there was pressure on the agent. The reason this happens is that some of the early gpg commands can start the agent without the option and it sticks around in memory so a version with the correct option may or may not get started. We therefore add the option to all the key gpg calls. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/elfutils')
0 files changed, 0 insertions, 0 deletions