[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem with running tests during installing coreutils-5.94

From: Bob Proulx
Subject: Re: Problem with running tests during installing coreutils-5.94
Date: Mon, 17 Apr 2006 10:00:26 -0600
User-agent: Mutt/1.5.9i

Thanks for the bug report.  Please keep bug-coreutils in the CC line
so that others may participate in the discussion.

Adam Waltman wrote:
>   I am trying to install coreutils-5.94 on my Gentoo system.
>   It fails during test stage. I have entered the error report here:
>   http://forums.gentoo.org/viewtopic-p-3262580.html#3262580

Which links to the bug report here:


The bug report states:

  make[3]: Entering directory
  ./remove: /var/tmp/portage/coreutils-5.94-r1/work/coreutils-5.94/tests/shred:
  not writable by user `nobody'
  ./remove: skipping this test
  SKIP: remove
  ./exact: line 25: 23017 Segmentation fault      shred --remove $opt a b
  ./exact: line 25: 23018 Segmentation fault      shred --remove $opt c
  FAIL: exact

>   Maybe this error is caused by Gentoo misconfiguration, but on the
>   other hand the error message asks for sending reports to
>   address@hidden - so here you are :-)

:-) I don't think anyone here has a Gentoo system so first we start by
asking questions.

>   Please tell me if you can help me somehow? Do you need any additional
>   information?

Can you recreate this build manually?  Probably the best place to
start is to get a current copy of the package and build it yourself.
Because to debug this we will want to see what is happening in the
test.  After building if you could send us the debug output from the
test it would be good.

  env DEBUG=yes VERBOSE=yes make check -C tests/shred TESTS=exact

Send us that output.  It will show the details of the test.  But if it
the shred program core dumping then that would probably take a more
detailed look at the shred program itself, if that is the one dumping.
If you have the capability of running the debugger to find out why it
is having a problem that would be good.  But I suggest starting with
the test details first.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]