[
https://issues.apache.org/jira/browse/MESOS-6356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15564659#comment-15564659
]
haosdent commented on MESOS-6356:
---------------------------------
As you see in this ticket, https://issues.apache.org/jira/browse/MESOS-3235
{code}
stderr: Failed to wait 15secs for awaitFinished(task.get())
stderr: *** Aborted at 1438968214 (unix time) try "date -d @1438968214" if you
are using GNU date ***
stdout: [ FAILED ] FetcherCacheHttpTest.HttpCachedSerialized (28685 ms)
stdout: [ RUN ] FetcherCacheHttpTest.HttpCachedConcurrent
stderr: PC: @ 0x113723618 process::Owned<>::get()
stderr: *** SIGSEGV (@0x0) received by PID 52313 (TID 0x118d59000) stack trace:
***
{code}
is interleaved logging.
> ASF CI has interleaved logging.
> -------------------------------
>
> Key: MESOS-6356
> URL: https://issues.apache.org/jira/browse/MESOS-6356
> Project: Mesos
> Issue Type: Bug
> Reporter: Anand Mazumdar
> Priority: Critical
> Labels: flaky, flaky-test, mesosphere, test
> Attachments: consoleText.zip
>
>
> It seems that the build output for test runs from ASF CI has interleaved
> logging making it very hard to debug test failures. This looks to have
> started happening after the unified unified cgroups isolator patches went in
> but we are yet to find a correlation.
> An example ASF CI run with interleaved logs:
> https://builds.apache.org/job/Mesos/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-6)/2762/changes
> (Also attached this to the ticket)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
