Thanks Yan!

On Fri, Jun 2, 2017 at 10:45 AM, Yan Xu <y...@jxu.me> wrote:

> +1 (binding)
>
> Ran it in a test cluster.
>
> ---
> Jiang Yan Xu <y...@jxu.me> | @xujyan <https://twitter.com/xujyan>
>
> On Thu, Jun 1, 2017 at 2:34 PM, Benjamin Mahler <bmah...@apache.org>
> wrote:
>
>> +1 (binding)
>>
>> Looks like ExamplesTest.DynamicReservationFramework is flaky,
>> unfortunately
>> wasn't able to get the logs for a failed run.
>>
>> On Thu, Jun 1, 2017 at 2:03 PM, Benjamin Mahler <bmah...@apache.org>
>> wrote:
>>
>> > Not a blocker, but noticed the parallel test runner isn't bundled in the
>> > release, if you configure with '--enable-parallel-test-execution':
>> >
>> > /Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-runner.py
>> > --sequential=*ROOT_* ./stout-tests
>> > /bin/sh: /Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-
>> runner.py:
>> > No such file or directory
>> >
>> > On Wed, May 31, 2017 at 1:48 PM, Vinod Kone <vinodk...@apache.org>
>> wrote:
>> >
>> >> Thanks for the triage.
>> >>
>> >> +1 (binding)
>> >>
>> >> On Wed, May 31, 2017 at 1:33 PM, Neil Conway <neil.con...@gmail.com>
>> >> wrote:
>> >>
>> >>> On Tue, May 30, 2017 at 3:43 PM, Neil Conway <neil.con...@gmail.com>
>> >>> wrote:
>> >>> > Attached is the test log for this failure. From a quick look, seems
>> as
>> >>> > though the agent starts to launch the task, including forking the
>> >>> > child process, but no subsequent task status updates or error
>> messages
>> >>> > are observed. Gaston, have you seen this before?
>> >>> >
>> >>> > I filed https://issues.apache.org/jira/browse/MESOS-7589 to track
>> >>> this.
>> >>>
>> >>> I wasn't able to repro this failure. Per Gaston's email, there isn't
>> >>> enough information in the logs to understand what is going on here,
>> >>> although it certainly seems weird that apparently the executor doesn't
>> >>> start.
>> >>>
>> >>> I think this doesn't justify blocking the release, but we should watch
>> >>> to see if the problem recurs.
>> >>>
>> >>> Neil
>> >>>
>> >>
>> >>
>> >
>>
>
>

Reply via email to