You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Neil Conway (JIRA)" <ji...@apache.org> on 2017/05/23 17:59:04 UTC

[jira] [Updated] (MESOS-6356) ASF CI has interleaved logging.

     [ https://issues.apache.org/jira/browse/MESOS-6356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Neil Conway updated MESOS-6356:
-------------------------------
    Priority: Major  (was: Critical)

Downgrading this from "Critical" to "Major" -- this is a problem but IMO not a critical one.

> 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
>              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.15#6346)