That's correct behavior. We have some tests that are a little flaky, so we disable them to prevent spurious test failures. Glad to see make check is passing for you now. What's next?
On Thu, Sep 11, 2014 at 4:15 PM, Luyi Wang <[email protected]> wrote: > updated, after rebuild the source and rerun the make check. > > 404 test ran and passed. 6 tests are disabled for unknown reason. > > > [----------] Global test environment tear-down > [==========] 404 tests from 66 test cases ran. (275125 ms total) > [ PASSED ] 404 tests. > > YOU HAVE 6 DISABLED TESTS > > > On Wed, Sep 10, 2014 at 3:00 PM, Luyi Wang <[email protected]> wrote: > >> Thanks. I did run everything under 'build' folder. I just removed all >> built result by using "make clean" in regarding the random failure and >> rebuilding now. Will probably update the thread later, probably tomorrow. >> >> Thanks. >> >> On Wed, Sep 10, 2014 at 2:56 PM, Till Toenshoff <[email protected]> wrote: >> >>> Luyi, >>> >>> please check the link that I had provided to enable enhanced verbosity >>> logging when running the tests. >>> Note that you do not need to rerun "make check” if you did that already >>> (which you obviously did). >>> >>> For your convenience, I copy pasted the answer and adapted it to fit one >>> of your failed tests (MasterAuthorizationTest.AuthorizedTask). You may >>> repeat the steps below for all other failed tests >>> (e.g. ShutdownTest.ShutdownEndpointBadCredentials as per your provided log >>> file). >>> >>> The following assumes that your current directory (pwd) is the build folder >>> within the extracted / cloned Mesos project directory structure. >>> >>> Let's assume that a test named MasterAuthorizationTest.AuthorizedTask had >>> failed for you. Now go ahead and run that test individually, with enhanced >>> output: >>> >>> ./bin/mesos-tests.sh >>> --gtest_filter="MasterAuthorizationTest.AuthorizedTask" --verbose >>> >>> That should reveal some more insights of the failure reasoning. >>> >>> In cases where the above still has too little output to understand the >>> problem, for some rare cases, it could be beneficial to increase the >>> verbosity even further. >>> >>> GLOG_v=2 ./bin/mesos-tests.sh >>> --gtest_filter="MasterAuthorizationTest.AuthorizedTask" --verbose >>> >>> That will enable all common VLOG levels of mesos. Those however usually >>> are not meant for users but for developers. So don't expect their output to >>> be too user friendly. >>> Hope that helps, >>> Till >>> >>> >>> On Sep 10, 2014, at 11:40 PM, Luyi Wang <[email protected]> wrote: >>> >>> seems it is more on random. >>> >>> I am using the source code checked out from git. The latest commit is >>> >>> commit fd798ffbeecee644b4674a9149c38d563bfa044e >>> Author: Timothy St. Clair <[email protected]> >>> Date: Tue Sep 9 13:28:10 2014 -0500 >>> >>> Update deploy_dir from localstate to sysconf >>> >>> Updates the mesos-env files to install to /etc/mesos vs. >>> /var/lib/deploy/mesos. >>> >>> Review: https://reviews.apache.org/r/25447 >>> >>> >>> The make check take less time than the first time running. The failed >>> test were also different. >>> >>> More insight would be helpful. >>> >>> Thanks. >>> >>> >>> On Wed, Sep 10, 2014 at 1:58 PM, Luyi Wang <[email protected]> >>> wrote: >>> >>>> rerunning the make check again with output redirect to a log file. It >>>> would take a while. will update afterward. >>>> >>>> On Wed, Sep 10, 2014 at 1:46 PM, Till Toenshoff <[email protected]> >>>> wrote: >>>> >>>>> >>>>> What's the error message / logs associated for those failed tests? >>>>> >>>>> >>>>> To expand on what Tim said, see the following for details: >>>>> >>>>> http://stackoverflow.com/questions/22619124/when-running-make-check-on-mesos-one-of-the-tests-fails-what-now >>>>> >>>>> >>>>> >>>>> Tim >>>>> >>>>> On Wed, Sep 10, 2014 at 1:27 PM, Luyi Wang <[email protected]> >>>>> wrote: >>>>> >>>>>> [ FAILED ] 3 tests, listed below: >>>>>> [ FAILED ] DRFAllocatorTest.DRFAllocatorProcess >>>>>> [ FAILED ] ResourceOffersTest.TaskUsesNoResources >>>>>> [ FAILED ] ShutdownTest.ShutdownEndpointGoodACLs >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>> <check.log> >>> >>> >>> >> >
