| Summary: | AB-INT: bb.process.CmdError: Cannot allocate memory | ||
|---|---|---|---|
| Product: | [Infrastructure] AutoBuilder | Reporter: | Mathieu Dubois-Briand <mathieu.dubois-briand> |
| Component: | autobuilder | Assignee: | Unassigned <unassigned> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | infras.ab.watcher, Infras.watcher, pidge, randy.macleod, richard.purdie |
| Version: | unspecified | ||
| Target Milestone: | 5.3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | AB-INT | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Mathieu Dubois-Briand
2024-12-12 09:35:16 UTC
oe-selftest-centos rocky9-vk-2 mathieu/master-next completed at 2024-12-01T17:18:25Z https://valkyrie.yoctoproject.org/#/builders/76/builds/521/steps/14/logs/stdio Let's see if this happens again. It would be nice to a utility to snapshot what was happening on the build host. Looking at the logs for rocky9-vk-2 there didn't appear to be anything else other than indexing running at the time which makes this all the more strange. Not sure this is the same one: same issue with failed memory allocation, but a completely different place in the code. musl-qemux86-64 stream9-vk-1 master completed at 2024-12-29T01:13:19Z https://valkyrie.yoctoproject.org/#/builders/3/builds/738/steps/11/logs/stdio oe-selftest-centos alma9-vk-1 master completed at 2025-02-08T02:31:18Z https://autobuilder.yoctoproject.org/valkyrie/#/builders/76/builds/932/steps/14/logs/stdio qemuppc alma9-vk-2 stable/kirkstone-nut completed at 2025-03-20T15:47:43Z https://autobuilder.yoctoproject.org/valkyrie/#/builders/31/builds/1215/steps/18/logs/stdio Bulk move of all unassigned 5.2 medium importance bugs to 5.3. oe-selftest-fedora rocky9-vk-3 master-next completed at 2025-05-13T17:35:58Z https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/1495/steps/14/logs/stdio We think this was diffoscope abusing RAM usage which is now limited. Re-open if seen again. |