mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Klues (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (MESOS-6836) Immediately failing tasks show incomplete logs in the sandbox
Date Fri, 06 Jan 2017 23:47:58 GMT

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

Kevin Klues reassigned MESOS-6836:
----------------------------------

    Assignee: Kevin Klues

> Immediately failing tasks show incomplete logs in the sandbox
> -------------------------------------------------------------
>
>                 Key: MESOS-6836
>                 URL: https://issues.apache.org/jira/browse/MESOS-6836
>             Project: Mesos
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: Joseph Wu
>            Assignee: Kevin Klues
>              Labels: mesosphere
>
> I started a master with default settings:
> {code}
> src/mesos-master --work_dir=/tmp/master
> {code}
> And an agent with default settings (on OSX and CentOS 7)
> {code}
> sudo src/mesos-agent --work_dir=/tmp/agent --master=...
> {code}
> Then I ran a task which I expect to fail immediately:
> {code}
> src/mesos-execute --master=... --name=fail --command=asdf
> {code}
> When I look inside the sandbox, I see a {{stderr}} like this:
> {code}
>     @           0x4156be _Abort()
>     @           0x4156fc _Abort()
> {code}
> The stack trace is apparently clipped.  I have a hunch (insubstantiated) that this output
clipping is due to the IO Switchboard.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message