Re: udev-149

[Alan Jenkins <alan-jenkins@tuffmail.co.uk>]

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
> ^[[31;01m*^[[0m ERROR: sys-fs/udev-149 failed:
> ^[[31;01m*^[[0m   Make check failed. See above for details.
> ^[[31;01m*^[[0m
> ^[[31;01m*^[[0m Call stack:
> ^[[31;01m*^[[0m     ebuild.sh, line   61:  Called src_test
> ^[[31;01m*^[[0m   environment, line 3692:  Called _eapi0_src_test
> ^[[31;01m*^[[0m     ebuild.sh, line  626:  Called die
> ^[[31;01m*^[[0m The specific snippet of code:
> ^[[31;01m*^[[0m               hasq test $FEATURES && die "Make check 
> failed. See above for details."
> ^[[31;01m*^[[0m
> ^[[31;01m*^[[0m If you need support, post the output of 'emerge --info 
> =sys-fs/udev-149',
> ^[[31;01m*^[[0m 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 <mgmadden@internode.on.net> 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
>