May be an issue with the embedded YARN mini cluster...

On Mon, Aug 10, 2015 at 8:37 PM, Stephan Ewen <se...@apache.org> wrote:

> I think the YARN problem is as before, but with a longer timeout.
>
> Before, when after 60 seconds the expected output did not come, the tests
> aborted.
> The timeout is now 180 seconds, which is probably so long that the
> deadlock detector (5 minutes no output) kicks in.
>
> In any case, there is something broken, because the YARN program does not
> properly finish.
>
> On Sun, Aug 9, 2015 at 9:49 PM, Matthias J. Sax <
> mj...@informatik.hu-berlin.de> wrote:
>
>> Not sure about the yarn test... As yarn was instable all the time I just
>> ignored it...
>>
>> -Matthias
>>
>> On 08/09/2015 09:38 PM, Ufuk Celebi wrote:
>> > PS what about the yarn test case... Is that one known (with that trace)?
>> >
>> > On Sunday, August 9, 2015, Ufuk Celebi <u...@apache.org> wrote:
>> >
>> >> There is an issue for this from last week. Couldn't look into it last
>> >> week, will do tomorrow. Thanks for the logs. :)
>> >>
>> >> On Sunday, August 9, 2015, Matthias J. Sax <
>> mj...@informatik.hu-berlin.de
>> >> <javascript:_e(%7B%7D,'cvml','mj...@informatik.hu-berlin.de');>>
>> wrote:
>> >>
>> >>> Wrong link... sorry.
>> >>>
>> >>> https://travis-ci.org/mjsax/flink/jobs/74787655
>> >>>
>> >>>
>> >>>
>> >>> On 08/09/2015 04:02 PM, Maximilian Michels wrote:
>> >>>> Hi Matthias,
>> >>>>
>> >>>> Is that the correct build URL? I can't spot any failing Gelly tests.
>> The
>> >>>> build appears to be stuck in the YARNSessionFIFOITCase.
>> >>>>
>> >>>> Cheers,
>> >>>> Max
>> >>>>
>> >>>> On Sun, Aug 9, 2015 at 3:37 PM, Matthias J. Sax <
>> >>>> mj...@informatik.hu-berlin.de> wrote:
>> >>>>
>> >>>>> Hi,
>> >>>>>
>> >>>>> I got a new failing test in this build (flink-gelly)
>> >>>>> https://travis-ci.org/mjsax/flink/jobs/74787658
>> >>>>>
>> >>>>> The branch is basically the current master, as I only fixed
>> >>>>> documentation stuff in this PR.
>> >>>>>
>> >>>>>
>> >>>>> -Matthias
>> >>>>>
>> >>>>>
>> >>>>
>> >>>
>> >>>
>> >
>>
>>
>

Reply via email to