Source: php-yac
Version: 2.0.2+0.9.2-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/<<PKGBUILDDIR>>/build-7.4'
> 
> Build complete.
> Don't forget to run 'make test'.
> 
> 
> =====================================================================
> PHP         : /usr/bin/php7.4 
> PHP_SAPI    : cli
> PHP_VERSION : 7.4.3
> ZEND_VERSION: 3.4.0
> PHP_OS      : Linux - Linux ip-172-31-2-119 4.19.0-6-cloud-amd64 #1 SMP 
> Debian 4.19.67-2+deb10u2 (2019-11-11) x86_64
> INI actual  : /<<PKGBUILDDIR>>/build-7.4/tmp-php.ini
> More .INIs  :   
> CWD         : /<<PKGBUILDDIR>>/build-7.4
> Extra dirs  : 
> VALGRIND    : Not used
> =====================================================================
> TIME START 2020-02-23 02:51:40
> =====================================================================
> TEST 1/16 [tests/001.phpt]
> PASS Check for yac presence [tests/001.phpt] 
> TEST 2/16 [tests/002.phpt]
> PASS Check for yac basic functions [tests/002.phpt] 
> TEST 3/16 [tests/003.phpt]
> PASS Check for yac errors [tests/003.phpt] 
> TEST 4/16 [tests/004.phpt]
> PASS Check for yac ttl [tests/004.phpt] 
> TEST 5/16 [tests/005.phpt]
> FAIL Check for yac non-string key [tests/005.phpt] 
> TEST 6/16 [tests/006.phpt]
> PASS Check for yac multi set/get [tests/006.phpt] 
> TEST 7/16 [tests/007.phpt]
> PASS Check for yac info [tests/007.phpt] 
> TEST 8/16 [tests/008.phpt]
> PASS Check for yac prefix [tests/008.phpt] 
> TEST 9/16 [tests/009.phpt]
> PASS Check for yac multi ops [tests/009.phpt] 
> TEST 10/16 [tests/010.phpt]
> PASS Check for yac::flush [tests/010.phpt] 
> TEST 11/16 [tests/011.phpt]
> PASS Check for yac::add [tests/011.phpt] 
> TEST 12/16 [tests/012.phpt]
> SKIP Check for functional apis [tests/012.phpt] reason: Functional style APIs 
> are not enabled
> TEST 13/16 [tests/013.phpt]
> PASS Check for ttl bug [tests/013.phpt] 
> TEST 14/16 [tests/014.phpt]
> PASS Check for ttl bug [tests/014.phpt] 
> TEST 15/16 [tests/015.phpt]
> PASS Check for Yac::dump [tests/015.phpt] 
> TEST 16/16 [tests/issue012.phpt]
> PASS ISSUE #12 segfault if use mmap&k_size bigger than 4M 
> [tests/issue012.phpt] 
> =====================================================================
> TIME END 2020-02-23 02:51:45
> 
> =====================================================================
> TEST RESULT SUMMARY
> ---------------------------------------------------------------------
> Exts skipped    :    0
> Exts tested     :   15
> ---------------------------------------------------------------------
> 
> Number of tests :   16                15
> Tests skipped   :    1 (  6.2%) --------
> Tests warned    :    0 (  0.0%) (  0.0%)
> Tests failed    :    1 (  6.2%) (  6.7%)
> Tests passed    :   14 ( 87.5%) ( 93.3%)
> ---------------------------------------------------------------------
> Time taken      :    5 seconds
> =====================================================================
> 
> =====================================================================
> FAILED TEST SUMMARY
> ---------------------------------------------------------------------
> Check for yac non-string key [tests/005.phpt]
> =====================================================================
> make[2]: *** [Makefile:132: test] Error 1
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/build-7.4'
> dh_auto_test: error: cd build-7.4 && make -j1 test VERBOSE=1 
> INSTALL_ROOT=/<<BUILDDIR>>/php-yac-2.0.2\+0.9.2/debian/php-yac returned exit 
> code 2

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/php-yac_2.0.2+0.9.2-4_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Reply via email to