The emerge for cups-1.1.20-r5 has an interactive test which halts a large emerge (e.g. world) when FEATURES=maketest. The build will sit forever waiting for user input. This will also cause problems for systems that are updated via cron. In addition, the test does not flush the typeahead buffer, so the tests performed may do all sorts of strange things. The test can also use Valgrind upon user request, so any typeahead strings may launch testing with Valgrind and do all sorts of strange things (yes, I got hit by this :-). Reproducible: Always Steps to Reproduce: 1. add maketest to FEATURES 2. emerge cups Actual Results: The build finished but the test stops and waits for user intervention: Welcome to the CUPS Automated Test Script. Before we begin, it is important that you understand that the larger tests require significant amounts of RAM and disk space. If you attempt to run one of the big tests on a system that lacks sufficient disk and virtual memory, the UNIX kernel might decide to kill one or more system processes that you've grown attached to, like the X server. The question you may want to ask yourself before running a large test is: Do you feel lucky? OK, now that we have the Dirty Harry quote out of the way, please choose the type of test you wish to perform: 1 - Basic conformance test, no load testing (all systems) 2 - Basic conformance test, some load testing (minimum 256MB VM, 50MB disk) 3 - Basic conformance test, extreme load testing (minimum 1GB VM, 500MB disk) 4 - Basic conformance test, torture load testing (minimum 2GB VM, 1GB disk) Please enter the number of the test you wish to perform: Expected Results: Continue with the emerge if no user input was supplied. Should it just perform the most basic test? Should there be some way of changing what tests will be performed in a USE flag? piste root # emerge info Portage 2.0.51-r3 (default-linux/x86/2004.0, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.4.26-gentoo-r9 i686) ================================================================= System uname: 2.4.26-gentoo-r9 i686 AMD Duron(tm) Processor Gentoo Base System version 1.4.16 distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.14.90.0.8-r1 Headers: sys-kernel/linux-headers-2.4.19-r1,sys-kernel/linux-headers-2.4.21-r1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=athlon-xp -funroll-loops -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=athlon-xp -funroll-loops -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distcc distlocks maketest sandbox severe sfperms strict userpriv" GENTOO_MIRRORS="http://128.213.5.34/gentoo/ http://cudlug.cudenver.edu/gentoo/ http://gentoo.noved.org/ http://mirror.tucdemonic.org/gentoo/ http://gentoo.osuosl.org http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow X alsa apache2 apm arts avi berkdb bitmap-fonts bonobo cdr cjk crypt cups curl dga directfb divx4linux doc dvb dvd dvdread emacs encode esd ethereal f77 fam fastcgi fbcon foomaticdb fortran gb gd gdbm gif gnome gpm gtk gtk2 gtkhtml guile imap imlib innodb java jpeg kde libg++ libwww live mad maildir mailwrapper mikmod mmx motif mozilla mpeg mysql nas ncurses network nls odbc ofx oggvorbis opengl oss pam pda pdflib perl png python qt quicktime quotes readline ruby samba sasl sdl slang slp spell sse ssl svga tcltk tcpd theora tiff truetype unicode usb wmf x86 xml xml2 xmms xv xvid zeo zlib" piste root #
come on guys... this is still a problem in 1.1.23-r1 couldn't you just do this for the time being: src_test() { # upstream is a bunch of losers and we don't have time, so... true }
I would agree to this proposal.
Lars, bug wranglers really won't solve this issue, so re-assigning the bug to them will not help at all. ;)
I'm so sorry. Don't know what forces me!
i got permission from genstef to add a dummy src_test so it won't break upgrades, but unfortunatly, it doesn't actually test anything. hopefully someone from printing will actually fix this... marking LATER
