On 4/25/12 8:05 PM, Benjamin Hindman wrote:
Hi Andy,
This looks to do with the timeout that is used in that test. The timeout
only allows 1 second, but the test shows 2.6 seconds have elapsed (2625
ms). You can easily check this by changing the Timeout values in
log_test.cpp to something greater than 1 second.
Is this also the likely cause of this Jenkins build failure:
https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Trunk-Ubuntu-Build-In-Src-Set-JAVA_HOME/120/console
?
Can we up the timeout a bunch to keep the continuous builds error-free?
- Charles
I'm curious though, where are you running this? I've only seen this on EC2
and I'm curious if it has to do with hiccups from the virtualization.
Ben.
On Wed, Apr 25, 2012 at 5:00 PM, Hao Lin <[email protected]> wrote:
Hi,
I have reached a problem in
make check.
It fails the one of test
called CoordinatorTest.MultipleAppendsNotLearnedFill:
[ RUN ] CoordinatorTest.MultipleAppendsNotLearnedFill
tests/log_tests.cpp:860: Failure
Value of: result.isSome()
Actual: false
Expected: true
[ FAILED ] CoordinatorTest.MultipleAppendsNotLearnedFill (2625 ms)
[ RUN ] CoordinatorTest.Truncate
/bin/bash: line 5: 15919 Segmentation fault ${dir}$tst
FAIL: mesos-tests
Any thought about the error is appreciated.
Thanks.
Andy
