From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Jenkins Date: Mon, 14 Dec 2009 11:46:43 +0000 Subject: Re: udev-149 Message-Id: <4B2625A3.4050101@tuffmail.co.uk> List-Id: References: <4B240A70.70204@verizon.net> In-Reply-To: <4B240A70.70204@verizon.net> To: linux-hotplug@vger.kernel.org Ken Miller wrote: > 150 errors occured > > FAIL: test/udev-test.pl > ======================= > 1 of 1 test failed > Please report to linux-hotplug@vger.kernel.org > ======================= > make[3]: *** [check-TESTS] Error 1 > make[2]: *** [check-am] Error 2 > make[1]: *** [check-recursive] Error 1 > make: *** [check] Error 2 > * ERROR: sys-fs/udev-149 failed: > * Make check failed. See above for details. > * > * Call stack: > * ebuild.sh, line 61: Called src_test > * environment, line 3692: Called _eapi0_src_test > * ebuild.sh, line 626: Called die > * The specific snippet of code: > * hasq test $FEATURES && die "Make check > failed. See above for details." > * > * If you need support, post the output of 'emerge --info > =sys-fs/udev-149', > * the complete build log and the output of 'emerge -pqv > =sys-fs/udev-149'. Not really an upstream udev problem. udev-test.pl needs to be run as root. See forwarded message below. That said, udev-test.pl would ideally check for root before it spewed out 150 test failures :). On 11/20/09, mgmadden wrote: > > Ok I think this'll be a final missile, having compiled the new > > kernel,and made a change in the environment by adding userpriv to > > my FEATURES listing, the following occurred > > make -j2 -j1 check > > make --no-print-directory check-recursive > > making check in . > > CC libudev/test-libudev.o > > CCLD libudev/test-libudev > > CC udev/test-udev.o > > CCLD udev/test-udev > > make --no-print-directory check-TESTS > > Must have root perms ......... > > PASS: test/udev-test.pl > > =============> > 1 test passed > > ============== > > And what can one say to that, except many thanks for your > > patience. > > Geoff >