alfie
February 4, 2015, 2:57am
1
I made PR #21895 which modifies src/libcoretest/. However for some reason when running ‘make check’, the libcoretest tests don’t get run. I’ve run ‘make check’ within script and the output is here:
https://gist.github.com/alfie/ce51c107c5edc31ca3e5
Compare this to a ‘make check’ run by Travis:
http://buildbot.rust-lang.org/builders/auto-linux-64-opt/builds/3428/steps/test/logs/stdio
If you search for “libcoretest”, you’ll see zero in my Gist but 1832 results from the Travis run.
Does anyone have any idea why some tests aren’t running on my local machine?
You make check failed during the run-valgrind tests which are executed before crate unit tests, hence you didn’t get to run coretest tests.
If you want to run only coretest unit tests, you can use the command make check-stage1-coretest. See make tips for more info.
(I’m not sure why the run-valgrind tests failed, but it seems that your valgrind is too old, and doesn’t recognize some flags?)
alfie
February 4, 2015, 11:23am
3
Ok, thanks for pointing that out. Upgrading Valgrind and will see how I go.
alfie
February 5, 2015, 9:09am
4
Upgraded valgrind, installed a couple of other requirements, upgraded gdb, and now getting:
Debuginfo tests failing
system
March 25, 2019, 8:23am
5
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.