Mailing-List: contact dev-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
MIME-Version: 1.0
In-Reply-To: <4E631665-FEFF-4D19-995C-7A2582D65C0B@apache.org>
References: 
 <CAL3J2zR+CFhSq-rqfvrBy=0yNxHEDKz9FoXuvtpSJKeMyfYrQQ@mail.gmail.com>
	<4E631665-FEFF-4D19-995C-7A2582D65C0B@apache.org>
Date: Wed, 14 Oct 2015 11:46:41 +0200
Message-ID: 
 <CAC27z=PLZFDWFTyxNwYdud8fQA351NJPPtqF3hDdhPg6RAyJ+Q@mail.gmail.com>
Subject: Re: Flaky ScalaShellLocalStartupITCase
From: Till Rohrmann <till.rohrmann@gmail.com>
To: dev@flink.apache.org
Content-Type: multipart/alternative; boundary=f46d043be2768ec1c405220d703d

--f46d043be2768ec1c405220d703d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Yeah I'm also struggling with the test case which has some wrong
assumptions about the log output.

I can also open the JIRA. Working on it today.

Cheers,
Till
On Oct 14, 2015 11:32 AM, "Ufuk Celebi" <uce@apache.org> wrote:

> I know that Till observed issues with the ScalaShell tests as well. If I
> remember correctly, the issues were caused by checking the log file for
> specific order of events, which is not necessarily the case.
>
> =E2=80=93 Ufuk
>
> > On 13 Oct 2015, at 16:14, Sachin Goel <sachingoel0101@gmail.com> wrote:
> >
> > Hi all
> > Over the past few days, I've observed multiple failures of this test
> case.
> > There is no single reason.
> > 1. The assertion to check the output fails [either the finished status =
or
> > the actual job output].
> > https://travis-ci.org/apache/flink/jobs/84664370
> > 2. JVM runs out of heap space [weirdly].
> > 3. Just recently, observed a loss of the task manager.
> > https://travis-ci.org/apache/flink/jobs/85108827
> >
> > Has someone else observed any such issues? It seems a simple enough tes=
t
> to
> > display such flaky behavior.
> >
> > Cheers!
> > Sachin
> > -- Sachin Goel
> > Computer Science, IIT Delhi
> > m. +91-9871457685
>
>

--f46d043be2768ec1c405220d703d--