|
From: Victor R. <vm....@gm...> - 2015-10-06 16:49:14
|
Hi team I had the idea that I was running the make check of valgrind: # make check But apparently and in my build.log there is something wrong like if the tests are not executed I can see that the tests are generated well: check_headers_and_includes check_makefile_consistency [...] I wonder if there is any requirement I am missing ( any package that are necessary for this) or how can I run them manually Best regards Victor Rodriguez |
|
From: Tom H. <to...@co...> - 2015-10-06 17:01:48
|
On 06/10/15 17:49, Victor Rodriguez wrote: > I had the idea that I was running the make check of valgrind: > > # make check > > But apparently and in my build.log there is something wrong like if > the tests are not executed > > > I can see that the tests are generated well: > > check_headers_and_includes > check_makefile_consistency > [...] > > I wonder if there is any requirement I am missing ( any package that > are necessary for this) or how can I run them manually You want "make regtest" not "make check". The latter only builds the tests while the former runs them as well. Tom -- Tom Hughes (to...@co...) http://compton.nu/ |
|
From: Victor R. <vm....@gm...> - 2015-10-06 19:56:27
|
On Tue, Oct 6, 2015 at 12:01 PM, Tom Hughes <to...@co...> wrote: > On 06/10/15 17:49, Victor Rodriguez wrote: > >> I had the idea that I was running the make check of valgrind: >> >> # make check >> >> But apparently and in my build.log there is something wrong like if >> the tests are not executed >> >> >> I can see that the tests are generated well: >> >> check_headers_and_includes >> check_makefile_consistency >> [...] >> >> I wonder if there is any requirement I am missing ( any package that >> are necessary for this) or how can I run them manually > > > You want "make regtest" not "make check". The latter only builds the tests > while the former runs them as well. Yea now I see , thanks a lot Tom it really help us ;) However now it get hang here : -- Running tests in gdbserver_tests ----------------------------------- hginfo: (skipping, prereq failed: test -e gdb.eval) hgtls: valgrind --tool=helgrind --vgdb=yes --vgdb-error=0 --vgdb-prefix=./vgdb-prefix-hgtls -q ./../none/tests/tls (progB: ./gdb --quiet -l 60 --nx ../none/tests/tls) We will check and see why this is happening . The good part is that now we are actually running some tests :) Regards Victor > Tom > > -- > Tom Hughes (to...@co...) > http://compton.nu/ |
|
From: Rhys K. <rhy...@gm...> - 2015-10-06 22:53:33
|
Hello Victor, What platform (OS, architecture) and Valgrind release version are you running 'make regtest' on there? Regards, Rhys On Wednesday, 7 October 2015, Victor Rodriguez <vm....@gm...> wrote: > On Tue, Oct 6, 2015 at 12:01 PM, Tom Hughes <to...@co... <javascript:;>> > wrote: > > On 06/10/15 17:49, Victor Rodriguez wrote: > > > >> I had the idea that I was running the make check of valgrind: > >> > >> # make check > >> > >> But apparently and in my build.log there is something wrong like if > >> the tests are not executed > >> > >> > >> I can see that the tests are generated well: > >> > >> check_headers_and_includes > >> check_makefile_consistency > >> [...] > >> > >> I wonder if there is any requirement I am missing ( any package that > >> are necessary for this) or how can I run them manually > > > > > > You want "make regtest" not "make check". The latter only builds the > tests > > while the former runs them as well. > > Yea now I see , thanks a lot Tom it really help us ;) > > However now it get hang here : > > -- Running tests in gdbserver_tests ----------------------------------- > hginfo: (skipping, prereq failed: test -e gdb.eval) > hgtls: valgrind --tool=helgrind --vgdb=yes --vgdb-error=0 > --vgdb-prefix=./vgdb-prefix-hgtls -q ./../none/tests/tls (progB: > ./gdb --quiet -l 60 --nx ../none/tests/tls) > > We will check and see why this is happening . The good part is that > now we are actually running some tests :) > > Regards > > Victor > > > Tom > > > > -- > > Tom Hughes (to...@co... <javascript:;>) > > http://compton.nu/ > > > ------------------------------------------------------------------------------ > _______________________________________________ > Valgrind-developers mailing list > Val...@li... <javascript:;> > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |
|
From: Victor R. <vm....@gm...> - 2015-10-07 00:18:02
|
On Tue, Oct 6, 2015 at 5:53 PM, Rhys Kidd <rhy...@gm...> wrote: > Hello Victor, > > What platform (OS, architecture) and Valgrind release version are you > running 'make regtest' on there? Hi Rhys I am running it on Clear Linux OS ( https://clearlinux.org/) in a Haswell machine ( 4th generation x86) Any clue ? What does this test do ? I really appreciate all the help > Regards, > Rhys > > > On Wednesday, 7 October 2015, Victor Rodriguez <vm....@gm...> wrote: >> >> On Tue, Oct 6, 2015 at 12:01 PM, Tom Hughes <to...@co...> wrote: >> > On 06/10/15 17:49, Victor Rodriguez wrote: >> > >> >> I had the idea that I was running the make check of valgrind: >> >> >> >> # make check >> >> >> >> But apparently and in my build.log there is something wrong like if >> >> the tests are not executed >> >> >> >> >> >> I can see that the tests are generated well: >> >> >> >> check_headers_and_includes >> >> check_makefile_consistency >> >> [...] >> >> >> >> I wonder if there is any requirement I am missing ( any package that >> >> are necessary for this) or how can I run them manually >> > >> > >> > You want "make regtest" not "make check". The latter only builds the >> > tests >> > while the former runs them as well. >> >> Yea now I see , thanks a lot Tom it really help us ;) >> >> However now it get hang here : >> >> -- Running tests in gdbserver_tests ----------------------------------- >> hginfo: (skipping, prereq failed: test -e gdb.eval) >> hgtls: valgrind --tool=helgrind --vgdb=yes --vgdb-error=0 >> --vgdb-prefix=./vgdb-prefix-hgtls -q ./../none/tests/tls (progB: >> ./gdb --quiet -l 60 --nx ../none/tests/tls) >> >> We will check and see why this is happening . The good part is that >> now we are actually running some tests :) >> >> Regards >> >> Victor >> >> > Tom >> > >> > -- >> > Tom Hughes (to...@co...) >> > http://compton.nu/ >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Valgrind-developers mailing list >> Val...@li... >> https://lists.sourceforge.net/lists/listinfo/valgrind-developers |
|
From: Victor R. <vm....@gm...> - 2015-10-07 00:26:07
|
Also I forgot to add that I am building using mock :) Regards Victor Rodriguez On Tue, Oct 6, 2015 at 7:17 PM, Victor Rodriguez <vm....@gm...> wrote: > On Tue, Oct 6, 2015 at 5:53 PM, Rhys Kidd <rhy...@gm...> wrote: >> Hello Victor, >> >> What platform (OS, architecture) and Valgrind release version are you >> running 'make regtest' on there? > > Hi Rhys > > I am running it on Clear Linux OS ( https://clearlinux.org/) in a > Haswell machine ( 4th generation x86) > > Any clue ? > > What does this test do ? > > I really appreciate all the help > > >> Regards, >> Rhys >> >> >> On Wednesday, 7 October 2015, Victor Rodriguez <vm....@gm...> wrote: >>> >>> On Tue, Oct 6, 2015 at 12:01 PM, Tom Hughes <to...@co...> wrote: >>> > On 06/10/15 17:49, Victor Rodriguez wrote: >>> > >>> >> I had the idea that I was running the make check of valgrind: >>> >> >>> >> # make check >>> >> >>> >> But apparently and in my build.log there is something wrong like if >>> >> the tests are not executed >>> >> >>> >> >>> >> I can see that the tests are generated well: >>> >> >>> >> check_headers_and_includes >>> >> check_makefile_consistency >>> >> [...] >>> >> >>> >> I wonder if there is any requirement I am missing ( any package that >>> >> are necessary for this) or how can I run them manually >>> > >>> > >>> > You want "make regtest" not "make check". The latter only builds the >>> > tests >>> > while the former runs them as well. >>> >>> Yea now I see , thanks a lot Tom it really help us ;) >>> >>> However now it get hang here : >>> >>> -- Running tests in gdbserver_tests ----------------------------------- >>> hginfo: (skipping, prereq failed: test -e gdb.eval) >>> hgtls: valgrind --tool=helgrind --vgdb=yes --vgdb-error=0 >>> --vgdb-prefix=./vgdb-prefix-hgtls -q ./../none/tests/tls (progB: >>> ./gdb --quiet -l 60 --nx ../none/tests/tls) >>> >>> We will check and see why this is happening . The good part is that >>> now we are actually running some tests :) >>> >>> Regards >>> >>> Victor >>> >>> > Tom >>> > >>> > -- >>> > Tom Hughes (to...@co...) >>> > http://compton.nu/ >>> >>> >>> ------------------------------------------------------------------------------ >>> _______________________________________________ >>> Valgrind-developers mailing list >>> Val...@li... >>> https://lists.sourceforge.net/lists/listinfo/valgrind-developers |
|
From: Mark W. <mj...@re...> - 2015-10-07 11:29:50
|
On Tue, 2015-10-06 at 19:17 -0500, Victor Rodriguez wrote: > On Tue, Oct 6, 2015 at 5:53 PM, Rhys Kidd <rhy...@gm...> wrote: > > What platform (OS, architecture) and Valgrind release version are you > > running 'make regtest' on there? > > I am running it on Clear Linux OS ( https://clearlinux.org/) in a > Haswell machine ( 4th generation x86) > > Any clue ? > > What does this test do ? The test (or actually the whole group) tests the interaction between valgrind and gdb. It it probably a good idea to first see whether the "basic" tools tests look sane with: make nonexp-regtest If those look sane then it will help to run tests that seem to hang individually with perl tests/vg_regtest gdbserver_tests/mcblocklistsearch.vgtest So try running that first outside mock and see if you can see where the script seems to stall. Cheers, Mark |
|
From: Victor R. <vm....@gm...> - 2015-10-09 16:11:51
|
On Wed, Oct 7, 2015 at 6:29 AM, Mark Wielaard <mj...@re...> wrote: > On Tue, 2015-10-06 at 19:17 -0500, Victor Rodriguez wrote: >> On Tue, Oct 6, 2015 at 5:53 PM, Rhys Kidd <rhy...@gm...> wrote: >> > What platform (OS, architecture) and Valgrind release version are you >> > running 'make regtest' on there? >> >> I am running it on Clear Linux OS ( https://clearlinux.org/) in a >> Haswell machine ( 4th generation x86) >> >> Any clue ? >> >> What does this test do ? > > The test (or actually the whole group) tests the interaction between > valgrind and gdb. It it probably a good idea to first see whether the > "basic" tools tests look sane with: make nonexp-regtest > > If those look sane then it will help to run tests that seem to hang > individually with > perl tests/vg_regtest gdbserver_tests/mcblocklistsearch.vgtest > > So try running that first outside mock and see if you can see where the > script seems to stall. > > Cheers, > > Mark Thanks a lot Mark That works just fine i had to split the test a bit caus etwo of them are hanging I remove the memcheck and none because of that reason . So my spec now looks like : 48 %build 49 # -fexceptions causes memcheck link command to fail when built with GCC 5.1 50 export CFLAGS=`echo $CFLAGS | sed s,-fexceptions,,g | sed s:-Wp,-D_FORTIFY_SOURCE=2::g | sed s:-fstack-protector::g ` 51 ./autogen.sh 52 %configure --disable-static --enable-only64bit --enable-tls 53 make V=1 %{?_smp_mflags} 54 55 %check 56 make VERBOSE=1 V=1 %{?_smp_mflags} check 57 /usr/bin/perl tests/vg_regtest cachegrind ||: 58 /usr/bin/perl tests/vg_regtest callgrind ||: 59 /usr/bin/perl tests/vg_regtest massif ||: 60 /usr/bin/perl tests/vg_regtest lackey ||: 61 /usr/bin/perl tests/vg_regtest helgrind ||: 62 /usr/bin/perl tests/vg_regtest drd ||: In the mean time we will debug what is worn and why they are hanging or failing Best Regards Victor Rodriguez |