guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNU Guix (pull?) on i686 broke after zstd grafting


From: Ludovic Courtès
Subject: Re: GNU Guix (pull?) on i686 broke after zstd grafting
Date: Wed, 10 Mar 2021 11:37:42 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)

Hi Léo,

Léo Le Bouter <lle-bout@zaclys.net> skribis:

> After commit: 
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=6f873731a030dd7ecbd8a5e756b38b26306f6966
>
> This happened:
> https://ci.guix.gnu.org/build/369538/details
>
> I made the commit, and not sure what to do here.
>
> The test suite seems to fail on i686..?

I’ve retried this i686-linux build and it seems to fail consistently:

--8<---------------cut here---------------start------------->8---
*** zstd command line interface 32-bits v1.4.9, by Yann Collet ***
(L3) Buffered :   0 MB - Consumed :   0 MB - Compressed :   0 MB => 0.00%
roundTripTest: datagen -g8M  | zstd -v19 -T0 --long | zstd -d19 -T0 --long

*** zstd command line interface 32-bits v1.4.9, by Yann Collet ***
Note: 48 physical core(s) detected
zstd: error 11 : Allocation error : not enough memory 
zstd: /*stdin*\: unexpected end of file
Files tmp1 and tmp2 differ
make[1]: *** [Makefile:329: test-zstd] Error 1
make[1]: Leaving directory '/tmp/guix-build-zstd-1.4.9.drv-0/zstd-1.4.9/tests'
make: *** [Makefile:90: shortest] Error 2

Test suite failed, dumping logs.
command "make" "check" "-j" "4" "CC=gcc" 
"PREFIX=/gnu/store/krx4mfj2yyg099kr1bj9pg0rs03fnymb-zstd-1.4.9" 
"LIBDIR=/gnu/store/la177xpxz00biapfhrrnx51pf1d9r8r3-zstd-1.4.9-lib/lib" 
"INCLUDEDIR=/gnu/store/la177xpxz00biapfhrrnx51pf1d9r8r3-zstd-1.4.9-lib/include" 
"HAVE_LZMA=0" "HAVE_LZ4=0" "HAVE_ZLIB=0" failed with status 2
builder for `/gnu/store/w0lbczib88vv83id42i2dx05v84fmpbv-zstd-1.4.9.drv' failed 
with exit code 1
build of /gnu/store/w0lbczib88vv83id42i2dx05v84fmpbv-zstd-1.4.9.drv failed
--8<---------------cut here---------------end--------------->8---

So I think there’s a genuine bug here.  Could you take a look?  At
worst, we should skip the offending test on i686 (and perhaps ARMv7?).

Thanks,
Ludo’.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]