|
From: Tom H. <th...@cy...> - 2005-11-14 03:14:10
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2005-11-14 03:00:03 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Last 20 lines of verbose log follow echo make[3]: Leaving directory `/tmp/valgrind.23458/valgrind/docs/lib' Making check in images make[3]: Entering directory `/tmp/valgrind.23458/valgrind/docs/images' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/tmp/valgrind.23458/valgrind/docs/images' Making check in internals make[3]: Entering directory `/tmp/valgrind.23458/valgrind/docs/internals' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/tmp/valgrind.23458/valgrind/docs/internals' make[3]: Entering directory `/tmp/valgrind.23458/valgrind/docs' make[3]: Nothing to be done for `check-am'. make[3]: Leaving directory `/tmp/valgrind.23458/valgrind/docs' make[2]: Leaving directory `/tmp/valgrind.23458/valgrind/docs' make[1]: Leaving directory `/tmp/valgrind.23458/valgrind' /usr/bin/perl tests/vg_regtest memcheck cachegrind massif lackey none -- Running tests in memcheck/tests ------------------------------------ addressable: valgrind ./addressable Bad line in insn_basic.vgtest: link ../../../none/tests/amd64/insn_basic.vgtest -- Running tests in memcheck/tests/amd64 ------------------------------ make: *** [regtest] Error 255 |
|
From: Julian S. <js...@ac...> - 2005-11-14 15:31:34
|
Any idea what happened here? I get this even with a clean checkout on amd64. J On Monday 14 November 2005 03:13, Tom Hughes wrote: > Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2005-11-14 > 03:00:03 GMT Results unchanged from 24 hours ago > > Checking out valgrind source tree ... done > Configuring valgrind ... done > Building valgrind ... done > Running regression tests ... failed > > Last 20 lines of verbose log follow echo > make[3]: Leaving directory `/tmp/valgrind.23458/valgrind/docs/lib' > Making check in images > make[3]: Entering directory `/tmp/valgrind.23458/valgrind/docs/images' > make[3]: Nothing to be done for `check'. > make[3]: Leaving directory `/tmp/valgrind.23458/valgrind/docs/images' > Making check in internals > make[3]: Entering directory `/tmp/valgrind.23458/valgrind/docs/internals' > make[3]: Nothing to be done for `check'. > make[3]: Leaving directory `/tmp/valgrind.23458/valgrind/docs/internals' > make[3]: Entering directory `/tmp/valgrind.23458/valgrind/docs' > make[3]: Nothing to be done for `check-am'. > make[3]: Leaving directory `/tmp/valgrind.23458/valgrind/docs' > make[2]: Leaving directory `/tmp/valgrind.23458/valgrind/docs' > make[1]: Leaving directory `/tmp/valgrind.23458/valgrind' > /usr/bin/perl tests/vg_regtest memcheck cachegrind massif lackey none > -- Running tests in memcheck/tests ------------------------------------ > addressable: valgrind ./addressable > Bad line in insn_basic.vgtest: link > ../../../none/tests/amd64/insn_basic.vgtest -- Running tests in > memcheck/tests/amd64 ------------------------------ make: *** [regtest] > Error 255 > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. > Download it for free - -and be entered to win a 42" plasma tv or your very > own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers |
|
From: Tom H. <to...@co...> - 2005-11-14 15:43:37
|
In message <200...@ac...>
Julian Seward <js...@ac...> wrote:
> Any idea what happened here? I get this even with a clean checkout
> on amd64.
That machine had a rather old subversion (1.0.7) and it looks like
it couldn't handle symbolic links.
A symbolic link appears to be handled by committing the text of the
link as the file with an svn:special property to indicate that it is
actually and subversion 1.0.7 was ignoring the property and getting
a nonsense file body.
I upgraded that machine to the latest subversion this morning.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|