| Summary: | test_signing_packages failed | ||
|---|---|---|---|
| Product: | [QA/Testing] Functional (self) Testing | Reporter: | Chen Qi <Qi.Chen> |
| Component: | oe-selftest | Assignee: | Richard Purdie <richard.purdie> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | randy.macleod, richard.purdie |
| Version: | 2.7 | ||
| Target Milestone: | 2.8 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Chen Qi
2018-12-14 09:38:53 UTC
Robert, the amount of locked memory, from: ulimit -a | grep lock is 16MB on my system and likely 32MB on larger servers. It's not clear how even with say 16 parallel users of gpg, we can end up with that much locked memory to result in an allocation error. It would be best to understand and document how the allocation is getting out of hand and arrange via locks perhaps to reduce contention for this scarce resource so that the error is avoided. Finally tracked this down: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=1334b064d3f04a976a42fe9dad64831b33d93755 |