Well, it still invokes make check-TESTS but I don't think it sets anything else up. Hmm, looks like latest autoconf might redirect check-TESTS to $test-name.log by default as opposed to stdout.
Still checking, but you can probably find the .log files in the build dirs, i.e.: $ tailf build/test/test-cppunit/zktest-st.log Zookeeper_watchers::testObjectSessionWatcher1 : elapsed 0 : OK Zookeeper_watchers::testObjectSessionWatcher2 : elapsed 200 : OK Zookeeper_watchers::testNodeWatcher1 : elapsed 400 : OK Zookeeper_watchers::testChildWatcher1 : elapsed 301 : OK ... -rgs On 8 July 2014 09:00, Patrick Hunt <ph...@apache.org> wrote: > The latter - test-core-cppunit. > > Patrick > > On Tue, Jul 8, 2014 at 8:56 AM, Raúl Gutiérrez Segalés > <r...@itevenworks.net> wrote: > > On 7 July 2014 23:18, Patrick Hunt <ph...@apache.org> wrote: > > > >> The test output for the c client seems to be broken. afaict this is a > >> recent change because the jenkins console output shows the test > >> details, but I don't see them in the latest trunk. > >> > >> I now see this (along with a long pause) > >> [exec] make[1]: Entering directory > >> `/home/phunt/dev/zookeeper-trunk/build/test/test-cppunit' > >> [exec] make[2]: Entering directory > >> `/home/phunt/dev/zookeeper-trunk/build/test/test-cppunit' > >> [exec] PASS: zktest-st > >> > >> whereas before we used to see output such as: > >> ZooKeeper server startedRunning > >> Zookeeper_init::testBasic : elapsed 1 : OK > >> Zookeeper_init::testAddressResolution : elapsed 0 : OK > >> Zookeeper_init::testMultipleAddressResolution : elapsed 0 : OK > >> Zookeeper_init::testNullAddressString : elapsed 0 : OK > >> Zookeeper_init::testEmptyAddressString : elapsed 0 : OK > >> > >> and so on. Which is now missing. > >> > >> Anyone know what happened here? It would be nice if we could turn this > >> back on - so that you get progress information as the test runs (also > >> captured in the jenkins console). > >> > > > > Is this running make check-TESTS manually or ant test-core-cppunit? > > > > -rgs >
