Ahmed Hamdy created FLINK-27756:
---
Summary: Fix Intermittingly failing test in `AsyncSinkWriterTest`
Key: FLINK-27756
URL: https://issues.apache.org/jira/browse/FLINK-27756
Project: Flink
Issue
Thanks, the actual problem is that the ActorSystem gets shutdown. This
breaks the testing code. Should be fixed once
https://github.com/apache/flink/pull/1852 is merged.
On Tue, Apr 5, 2016 at 12:25 PM, Matthias J. Sax wrote:
> Happened again after your fix:
> https://travis-ci.org/apache/flink/j
Happened again after your fix:
https://travis-ci.org/apache/flink/jobs/120620482
-Matthias
On 04/01/2016 08:57 PM, Maximilian Michels wrote:
> Fixed with the resolution of https://issues.apache.org/jira/browse/FLINK-3689.
>
> On Fri, Apr 1, 2016 at 12:40 PM, Maximilian Michels wrote:
>> Hi Mat
Thanks. Just tried is out and it works :)
On 04/01/2016 08:57 PM, Maximilian Michels wrote:
> Fixed with the resolution of https://issues.apache.org/jira/browse/FLINK-3689.
>
> On Fri, Apr 1, 2016 at 12:40 PM, Maximilian Michels wrote:
>> Hi Matthias,
>>
>> Thanks for spotting the test failure.
Fixed with the resolution of https://issues.apache.org/jira/browse/FLINK-3689.
On Fri, Apr 1, 2016 at 12:40 PM, Maximilian Michels wrote:
> Hi Matthias,
>
> Thanks for spotting the test failure. It's actually a bug in the code
> and not a test problem. Fixing it.
>
> Cheers,
> Max
>
> On Fri, Apr
Hi Matthias,
Thanks for spotting the test failure. It's actually a bug in the code
and not a test problem. Fixing it.
Cheers,
Max
On Fri, Apr 1, 2016 at 9:33 AM, Ufuk Celebi wrote:
> Hey Matthias,
>
> the test has been only recently added with the resource management
> refactoring. It's probabl
Hey Matthias,
the test has been only recently added with the resource management
refactoring. It's probably just a too aggressive timeout for Travis.
@Max: Did you ever see this fail?
– Ufuk
On Fri, Apr 1, 2016 at 9:24 AM, Matthias J. Sax wrote:
> Anyone seen this before? One-time thing or tes
Anyone seen this before? One-time thing or test instability?
> ClusterShutdownITCase.testClusterShutdown:71 assertion failed: timeout
> (29848225634 nanoseconds) during expectMsgClass waiting for class
> org.apache.flink.runtime.clusterframework.messages.StopClusterSuccessful
-Matthias
sign
Gabor Gevay created FLINK-2839:
--
Summary: Failing test:
OperatorStatsAccumulatorTest.testAccumulatorAllStatistics
Key: FLINK-2839
URL: https://issues.apache.org/jira/browse/FLINK-2839
Project: Flink
Vasia Kalavri created FLINK-2832:
Summary: Failing test:
RandomSamplerTest.testReservoirSamplerWithReplacement
Key: FLINK-2832
URL: https://issues.apache.org/jira/browse/FLINK-2832
Project: Flink
If there is none yet, then we do. Label it with "test-stability". I think
the consensus was also to mark it as critical.
Otherwise, just add the log to the JIRA.
On Tue, Oct 6, 2015 at 2:57 PM, Matthias J. Sax wrote:
> Hi,
>
> One test just failed on current master:
> https://travis-ci.org/apac
Hi,
One test just failed on current master:
https://travis-ci.org/apache/flink/jobs/83871008
Do we need a JIRA?
> LeaderChangeStateCleanupTest.testReelectionOfSameJobManager:245 » Timeout
> Futu...
-Matthias
signature.asc
Description: OpenPGP digital signature
I have a patch pending that should help with these timeout issues (and null
checks)...
On Mon, Sep 7, 2015 at 2:41 PM, Matthias J. Sax wrote:
> Please lock here:
>
> https://travis-ci.org/apache/flink/jobs/79086396
>
> > Failed tests:
> > KafkaITCase>KafkaTestBase.prepare:155 Test setup failed:
Please lock here:
https://travis-ci.org/apache/flink/jobs/79086396
> Failed tests:
> KafkaITCase>KafkaTestBase.prepare:155 Test setup failed: Unable to connect to
> zookeeper server within timeout: 6000
> KafkaProducerITCase>KafkaTestBase.prepare:155 Test setup failed: Unable to
> connect to zo
Martin Liesenberg created FLINK-2628:
Summary: Failing Test:
StreamFaultToleranceTestBase.runCheckpointedProgram
Key: FLINK-2628
URL: https://issues.apache.org/jira/browse/FLINK-2628
Project
Matthias J. Sax created FLINK-2616:
--
Summary: Failing Test: ZooKeeperLeaderElectionTest
Key: FLINK-2616
URL: https://issues.apache.org/jira/browse/FLINK-2616
Project: Flink
Issue Type: Bug
Matthias J. Sax created FLINK-2599:
--
Summary: Failing Test: SlotCountExceedingParallelismTest
Key: FLINK-2599
URL: https://issues.apache.org/jira/browse/FLINK-2599
Project: Flink
Issue Type
Matthias J. Sax created FLINK-2596:
--
Summary: Failing Test: RandomSamplerTest
Key: FLINK-2596
URL: https://issues.apache.org/jira/browse/FLINK-2596
Project: Flink
Issue Type: Bug
Matthias J. Sax created FLINK-2578:
--
Summary: Failing-Test: TaskAsyncCallTest
Key: FLINK-2578
URL: https://issues.apache.org/jira/browse/FLINK-2578
Project: Flink
Issue Type: Bug
> > > > page in sync. Maybe we can assign a special label for test
>> stability
>> > to
>> > > > > these JIRA issues. Then we can quickly find all currently instable
>> > test
>> > > > > cases.
>> > > > >
1:02 AM, Robert Metzger <
> > rmetz...@apache.org>
> > > > > wrote:
> > > > >
> > > > >> I agree that we should look for a solution other than opening a
> lot
> > of
> > > > >> small discussion threads on the maili
Hi Matthias,
Thanks for reporting. The label test-stability exists now.
Cheers,
Max
On Sun, Aug 23, 2015 at 12:32 PM, Matthias J. Sax <
mj...@informatik.hu-berlin.de> wrote:
> Hi,
>
> because there is (not yet) a label for failing tests, I just report it
> over the mailing list again. I also op
015 at 11:02 AM, Robert Metzger <
> rmetz...@apache.org>
> > > > wrote:
> > > >
> > > >> I agree that we should look for a solution other than opening a lot
> of
> > > >> small discussion threads on the mailing list.
> >
Matthias J. Sax created FLINK-2564:
--
Summary: Failing Test: RandomSamplerTest
Key: FLINK-2564
URL: https://issues.apache.org/jira/browse/FLINK-2564
Project: Flink
Issue Type: Bug
Hi,
because there is (not yet) a label for failing tests, I just report it
over the mailing list again. I also open a JIRA for it).
> Tests run: 17, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 15.943 sec
> <<< FAILURE! - in org.apache.flink.api.java.sampling.
> testPoissonSamplerFract
02 AM, Robert Metzger
> > > wrote:
> > >
> > >> I agree that we should look for a solution other than opening a lot of
> > >> small discussion threads on the mailing list.
> > >>
> > >> When I have a test failure, I usually search
t;>
> >> When I have a test failure, I usually search my gmail inbox to see
> whether
> >> somebody else wrote something about the error already.
> >> Creating a JIRA for each failing test might be a better approach.
> Because
> >> that's what
ds on the mailing list.
>>
>> When I have a test failure, I usually search my gmail inbox to see whether
>> somebody else wrote something about the error already.
>> Creating a JIRA for each failing test might be a better approach. Because
>> that's what bugtracke
ree that we should look for a solution other than opening a lot of
> small discussion threads on the mailing list.
>
> When I have a test failure, I usually search my gmail inbox to see whether
> somebody else wrote something about the error already.
> Creating a JIRA for each failing
I agree that we should look for a solution other than opening a lot of
small discussion threads on the mailing list.
When I have a test failure, I usually search my gmail inbox to see whether
somebody else wrote something about the error already.
Creating a JIRA for each failing test might be a
Thanks for the info.
Over the weeks I lost track which errors/failing/instable tests are know
an which not. Should we start a wiki page or similar to collect know
errors? If a test fails on a know error, it can just be ignored. This
would avoid "spam" on the mailing list.
Any thoughts about this?
Sachin saw the error as well, as reported here:
https://issues.apache.org/jira/browse/FLINK-2468
I also see it from time to time.I have a wip branch where I relaxed the
constraints for the test to pass a bit.
On Thu, Aug 20, 2015 at 10:05 PM, Matthias J. Sax <
mj...@informatik.hu-berlin.de> wrote:
Error message is:
> Failed tests:
> StateCheckpoinedITCase>StreamFaultToleranceTestBase.runCheckpointedProgram:103->postSubmit:98
> Test inconclusive: failure occurred before first checkpoint
See: https://travis-ci.org/mjsax/flink/jobs/76483093
-Matthias
signature.asc
Description: OpenPGP d
Looks like a rare race between the cleanup (two changes) and the test
validating both changes.
I'll push a fix to make the test more reliable.
On Sun, Aug 16, 2015 at 11:04 PM, Matthias J. Sax <
mj...@informatik.hu-berlin.de> wrote:
> Hi,
>
> I hit a failing test in flink-
Hi,
I hit a failing test in flink-runtime. Not sure if it is known already:
> Failed tests:
> CheckpointCoordinatorTest.testCheckpointTimeoutIsolated:594 expected:<0> but
> was:<1>
Please see: https://travis-ci.org/mjsax/flink/jobs/75847501
-Matthias
signature.asc
e
> >>>> 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
> >>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >
>
>
;
>> >>>
>> >>>
>> >>> 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
>> &
o 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:
>>>>
>>
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
> >>
> >>
> >
>
>
t 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>
gt;
> 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
>>
>> Th
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 failin
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
signature.asc
Description: OpenPGP digital signature
I've also seen the BufferSpillerTest fail:
https://travis-ci.org/apache/flink/jobs/74057503
On Tue, 4 Aug 2015 at 14:10 Robert Metzger wrote:
> I've assigned https://issues.apache.org/jira/browse/FLINK-1680 to myself.
> Maybe Tachyon 0.7 will fix the issues.
>
> On Tue, Aug 4, 2015 at 1:57 PM,
I've assigned https://issues.apache.org/jira/browse/FLINK-1680 to myself.
Maybe Tachyon 0.7 will fix the issues.
On Tue, Aug 4, 2015 at 1:57 PM, Stephan Ewen wrote:
> Yes.
>
> We should know, though, whether this is a Java 6 bug, or a bug in our
> system that just happens to occur only with Java
Yes.
We should know, though, whether this is a Java 6 bug, or a bug in our
system that just happens to occur only with Java 6 (because of different
timings in this other engine)
On Tue, Aug 4, 2015 at 12:27 PM, Chesnay Schepler <
chesnay.schep...@fu-berlin.de> wrote:
> Aren't we dropping java 6
Aren't we dropping java 6 support?
On 04.08.2015 12:21, Stephan Ewen wrote:
The "StateCheckpointedITCase" has not failed so far, which also test these
guarantees thoroughly.
But we need to first rule out the BarrierBuffer. The problem is that the
bug occur only on Java 6 and cannot be reproduce
The "StateCheckpointedITCase" has not failed so far, which also test these
guarantees thoroughly.
But we need to first rule out the BarrierBuffer. The problem is that the
bug occur only on Java 6 and cannot be reproduced locally...
On Tue, Aug 4, 2015 at 12:14 PM, Gyula Fóra wrote:
> Honestly I
Honestly I don't think the partitioned state changes have anything to do
with the stability, only the reworked test case, which now test proper
exactly-once which was missing before.
Stephan Ewen ezt írta (időpont: 2015. aug. 4., K, 12:12):
> Yes, the build stability is super serious right now.
Yes, the build stability is super serious right now.
Here are the problems in question, and what we could do about this:
BarrierBuffer:
Barrier Buffer tests fail in Java 6 builds.
I have not found a way to diagnose that problem, yet, but if we cannot find
the issue today,
I've also seen this fail: https://travis-ci.org/apache/flink/jobs/74025862
in SuccessAfterNetworkBuffersFailureITCase
Build seems quite flaky recently.
On Tue, 4 Aug 2015 at 10:27 Matthias J. Sax
wrote:
> Rebased on:
>
>
> https://github.com/mjsax/flink/commit/fab61a1954ff1554448e826e1d273689e
Rebased on:
https://github.com/mjsax/flink/commit/fab61a1954ff1554448e826e1d273689ed520fc3
But if the gap between two rebases is large, it's hard to say what the
problem might be...
The old parent commit (ie, rebase before last rebase) was
https://github.com/mjsax/flink/commit/148395bcd81a93bcb1
What are the commits that you rebased on? Could you maybe narrow down what
caused the regression?
On Mon, 3 Aug 2015 at 23:31 Matthias J. Sax
wrote:
> I only report failing tests after a rebase. ;)
>
> -Matthias
>
> On 08/03/2015 11:23 PM, Henry Saputra wrote:
> > Thanks for reporting it , Matth
I only report failing tests after a rebase. ;)
-Matthias
On 08/03/2015 11:23 PM, Henry Saputra wrote:
> Thanks for reporting it , Matthias. Will try to run Travis for latest Flink.
>
> Tachyon test is a bit flaky. Maybe updating to latest release could help.
>
> - Henry
>
> On Mon, Aug 3, 2015
Thanks for reporting it , Matthias. Will try to run Travis for latest Flink.
Tachyon test is a bit flaky. Maybe updating to latest release could help.
- Henry
On Mon, Aug 3, 2015 at 2:18 PM, Matthias J. Sax
wrote:
> Today, not a single built was successful completely. Please see here:
>
> Flink
Today, not a single built was successful completely. Please see here:
Flink Streaming Core:
https://travis-ci.org/mjsax/flink/jobs/73938109
https://travis-ci.org/mjsax/flink/jobs/73951362
https://travis-ci.org/apache/flink/jobs/73938124
https://travis-ci.org/apache/flink/jobs/73899795
https://trav
Seen this a few times as well.
May be something with the latest "partitioned state" changes...
On Mon, Aug 3, 2015 at 5:48 PM, Matthias J. Sax <
mj...@informatik.hu-berlin.de> wrote:
> Hi,
>
> I just hit a failing test
> (https://travis-ci.org/apache/flink/jobs/
Hi,
I just hit a failing test
(https://travis-ci.org/apache/flink/jobs/73899795). It is know or new?
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 86.929 sec
> <<< FAILURE! - in
> org.apache.flink.test.checkpointing.StreamCheckpointingITCase
> r
s there is a bit strict. Actually, I've
> already
> >>>>> integrated a retry mechanism that fails only if the assertions don't
> >> hold
> >>>>> for a configured number of times.
> >>>>>
> >>>>> I'll commit
>>>>> integrated a retry mechanism that fails only if the assertions don't
>> hold
>>>>> for a configured number of times.
>>>>>
>>>>> I'll commit a fix to the master. Thanks for reporting!
>>>>>
>>
t fails only if the assertions don't
> hold
> >>> for a configured number of times.
> >>>
> >>> I'll commit a fix to the master. Thanks for reporting!
> >>>
> >>> Cheers,
> >>> Max
> >>>
> >>> O
ul 16, 2015 at 11:33 AM, Ufuk Celebi wrote:
>>>
>>>> Hey,
>>>>
>>>> this has been merged yesterday. I guess it's a timing issue when
>>>> verifying the results. Can you file an issue for this?
>>>>
>>>> – Ufuk
&
been merged yesterday. I guess it's a timing issue when
>>> verifying the results. Can you file an issue for this?
>>>
>>> – Ufuk
>>>
>>> On 16 Jul 2015, at 11:30, Matthias J. Sax
>>> wrote:
>>>
>>>> Hi,
>>>
has been merged yesterday. I guess it's a timing issue when
>> verifying the results. Can you file an issue for this?
>>
>> – Ufuk
>>
>> On 16 Jul 2015, at 11:30, Matthias J. Sax
>> wrote:
>>
>> > Hi,
>> >
>> > I hit another fa
it's a timing issue when verifying
> the results. Can you file an issue for this?
>
> – Ufuk
>
> On 16 Jul 2015, at 11:30, Matthias J. Sax
> wrote:
>
> > Hi,
> >
> > I hit another failing test (that is new to me):
> >
> >> Result
Hey,
this has been merged yesterday. I guess it's a timing issue when verifying the
results. Can you file an issue for this?
– Ufuk
On 16 Jul 2015, at 11:30, Matthias J. Sax wrote:
> Hi,
>
> I hit another failing test (that is new to me):
>
>> Re
Hi,
I hit another failing test (that is new to me):
> Results :
> Failed tests:
> AccumulatorLiveITCase.testProgram:106->access$1100:68->checkFlinkAccumulators:189
> null
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 8.694 sec
Matthias J. Sax created FLINK-2349:
--
Summary: Instable (failing) Test
Key: FLINK-2349
URL: https://issues.apache.org/jira/browse/FLINK-2349
Project: Flink
Issue Type: Bug
68 matches
Mail list logo
