I have emerged new gcc-4.1 and db4.5 with test feature enabled. 6+ hours test failed. # gcc --version gcc (GCC) 4.1.2 20070214 ( (gdc 0.24, using dmd 1.020)) (Gentoo 4.1.2 p1.1) # binutils-config -c i686-pc-linux-gnu-2.18 Reproducible: Always Steps to Reproduce: 1.emerge new gcc-4.1 2.fix_libtool_files 3.emerge libtool 4.emerge libstdc++ 5.emerge autoconf 6.emerge db4.5 Actual Results: 6+ hour tests failed Expected Results: test to be passed ebuild test log end: Test suite run started at: 17:00 06/25/08 Berkeley DB 4.5.20: (September 20, 2006) Running environment tests Running archive tests Running file operations tests Running locking tests Running logging tests Running memory pool tests Running transaction tests Running deadlock detection tests Running subdatabase tests Running byte-order tests Running recno backing file tests Running DBM interface tests Running NDBM interface tests Running Hsearch interface tests Running secondary index tests Running replication tests Running security tests Running recovery tests Running join test Running btree tests Running rbtree tests Running queue tests Running queueext tests Running recno tests Running frecno tests Running rrecno tests Running hash tests UNEXPECTED OUTPUT: Berkeley DB 4.5.20: (September 20, 2006) UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32029: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32027: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32080: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32078: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32130: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32132: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32130: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32132: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32130: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32132: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32130: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32132: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32130: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32132: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32130: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32132: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32130: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32132: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32130: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32132: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32130: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32132: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32130: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32132: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32130: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32132: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32130: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32132: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32130: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32132: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32130: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32132: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32130: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32132: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32130: child process exited abnormally UNEXPECTED OUTPUT: FAIL: Problem reported killing process 32132: child process exited abnormally UNEXPECTED OUTPUT: FAIL:17:03:44 (00:00:00) open_create_err: expected db open:permission denied, got db7890 UNEXPECTED OUTPUT: FAIL: Problem reported killing process 26793: child process exited abnormally UNEXPECTED OUTPUT: FAIL:19:47:02 (00:00:23) stat_mprlog: expected 0, got 1 UNEXPECTED OUTPUT: WARNING: log record type __bam_merge: not tested UNEXPECTED OUTPUT: WARNING: log record type __bam_pgno: not tested UNEXPECTED OUTPUT: WARNING: log record type __crdel_inmem_create: not tested UNEXPECTED OUTPUT: WARNING: log record type __crdel_inmem_remove: not tested UNEXPECTED OUTPUT: WARNING: log record type __crdel_inmem_rename: not tested UNEXPECTED OUTPUT: WARNING: log record type __db_pg_new: not tested UNEXPECTED OUTPUT: WARNING: log record type __db_pg_prepare can be seen only on systems without FTRUNCATE. UNEXPECTED OUTPUT: WARNING: log record type __db_pg_prepare: not tested UNEXPECTED OUTPUT: WARNING: log record type __db_pg_sort: not tested Regression Tests Failed Check UNEXPECTED OUTPUT lines. Review ALL.OUT.x for details. Test suite run completed at: 03:36 06/26/08 [31;01m*[0m [31;01m*[0m ERROR: sys-libs/db-4.5.20_p2 failed. [31;01m*[0m Call stack: [31;01m*[0m ebuild.sh, line 49: Called src_test [31;01m*[0m environment, line 4173: Called db_src_test [31;01m*[0m environment, line 910: Called die [31;01m*[0m The specific snippet of code: [31;01m*[0m egrep -qs '^FAIL' ALL.OUT && die "Some tests failed, please see ${S}/ALL.OUT"; [31;01m*[0m The die message: [31;01m*[0m Some tests failed, please see /var/tmp/portage/sys-libs/db-4.5.20_p2/work/db-4.5.20/build_unix/ALL.OUT [31;01m*[0m [31;01m*[0m If you need support, post the topmost build error, and the call stack if relevant. [31;01m*[0m A complete build log is located at '/var/tmp/portage/sys-libs/db-4.5.20_p2/temp/build.log'. [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/sys-libs/db-4.5.20_p2/temp/environment'. [31;01m*[0m !!! When you file a bug report, please include the following information: GENTOO_VM=sun-jdk-1.5 CLASSPATH="" JAVA_HOME="/opt/sun-jdk-1.5.0.15" JAVACFLAGS="-source 1.4 -target 1.4" COMPILER="gcc-4.1" and of course, the output of e
Created attachment 158479 [details] build.log all build log
`emerge --info` output missing.
I don't know anything we can do for this. db 4.5 seems to work just fine for about everyone, so I don't think these tests should account for much. reopen if you have a suggestion for how to fix.
