> On Jan. 23, 2015, 3:31 p.m., Adam B wrote: > > src/tests/fetcher_tests.cpp, line 269 > > <https://reviews.apache.org/r/30034/diff/2/?file=826090#file826090line269> > > > > How do we get verbose fetcher output now? If it's a libprocess actor, > > can we just set the GTEST_v environment variable? Where do those logs go?
The logs go to the sandbox work dir's stderr, where the task output is, too. This helpfully separates them by task. This is not a libprocess actor, it is an external OS process (mesos-fetcher). - Bernd ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/30034/#review69501 ----------------------------------------------------------- On Jan. 20, 2015, 12:33 a.m., Bernd Mathiske wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/30034/ > ----------------------------------------------------------- > > (Updated Jan. 20, 2015, 12:33 a.m.) > > > Review request for mesos, Adam B, Benjamin Hindman, Till Toenshoff, and > Timothy Chen. > > > Bugs: MESOS-2069 > https://issues.apache.org/jira/browse/MESOS-2069 > > > Repository: mesos-git > > > Description > ------- > > Makes the code structure of all fetcher tests the same. Instead of calling > the run mathod of the fetcher directly, calling through fetch(). Also removes > all uses of I/O redirection, which is not really needed for debugging, and > thus the next patch can refactor fetch() and run(). (The latter comes in two > varieties, which complicates matters without much benefit.) > > > Diffs > ----- > > src/tests/fetcher_tests.cpp 8c0b0757eb388f1684d8b94393983f1844a769a7 > > Diff: https://reviews.apache.org/r/30034/diff/ > > > Testing > ------- > > make check > > > Thanks, > > Bernd Mathiske > >
