[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#67535: ci.guix.gnu.org 'Cannot allocate memory' while building for i
From: |
Efraim Flashner |
Subject: |
bug#67535: ci.guix.gnu.org 'Cannot allocate memory' while building for i686-linux |
Date: |
Wed, 6 Dec 2023 14:25:13 +0200 |
On Wed, Nov 29, 2023 at 03:55:15PM -0500, Leo Famulari wrote:
> I see that ci.guix.gnu.org's builders seem to run out of memory while
> building kernel headers for i686-linux:
>
> ------
> xz: (stdin): Cannot allocate memory
> /gnu/store/ns71xxkb3fzr37934bim9l8xiv68kc7w-tar-1.34/bin/tar:
> /gnu/store/536ifp75wv8i1kb1k0szv7zd57ygpg0n-linux-libre-6.5.13-guix.tar.xz:
> Wrote only 2048 of 10240 bytes
> /gnu/store/ns71xxkb3fzr37934bim9l8xiv68kc7w-tar-1.34/bin/tar: Child returned
> status 1
> /gnu/store/ns71xxkb3fzr37934bim9l8xiv68kc7w-tar-1.34/bin/tar: Error is not
> recoverable: exiting now
> ------
>
> https://ci.guix.gnu.org/build/2736161/details
This looks like more of the too-many-cores while decompressing tarballs
issues we've had in the past on i686-linux. Can we change that phase to
use a maximum of 4 cores or would that cause everything to rebuild?
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
signature.asc
Description: PGP signature
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#67535: ci.guix.gnu.org 'Cannot allocate memory' while building for i686-linux,
Efraim Flashner <=