+1 for a "test-stability" label and labeling these issues as "critical"
On Mon, Aug 24, 2015 at 6:31 PM, Stephan Ewen wrote:
> Pushed a fix for the StateCheckpointedITCase
>
> On Mon, Aug 24, 2015 at 12:19 PM, Maximilian Michels
> wrote:
>
>> +1 for labeling the JIRAs with "test-stability".
>>
Pushed a fix for the StateCheckpointedITCase
On Mon, Aug 24, 2015 at 12:19 PM, Maximilian Michels wrote:
> +1 for labeling the JIRAs with "test-stability".
>
> On Sat, Aug 22, 2015 at 8:21 PM, Márton Balassi
> wrote:
>
> > +1 for Vasia's suggestion
> > On Aug 22, 2015 8:07 PM, "Vasiliki Kalavri
+1 for labeling the JIRAs with "test-stability".
On Sat, Aug 22, 2015 at 8:21 PM, Márton Balassi
wrote:
> +1 for Vasia's suggestion
> On Aug 22, 2015 8:07 PM, "Vasiliki Kalavri"
> wrote:
>
> > I just came across 2 more :/
> > I'm also in favor of tracking these with JIRA. How about "test-stabil
+1 for Vasia's suggestion
On Aug 22, 2015 8:07 PM, "Vasiliki Kalavri"
wrote:
> I just came across 2 more :/
> I'm also in favor of tracking these with JIRA. How about "test-stability"
> for a label?
>
> -V.
>
> On 21 August 2015 at 12:47, Matthias J. Sax >
> wrote:
>
> > I like the idea with the
I just came across 2 more :/
I'm also in favor of tracking these with JIRA. How about "test-stability"
for a label?
-V.
On 21 August 2015 at 12:47, Matthias J. Sax
wrote:
> I like the idea with the special label. Otherwise, it will be difficult
> to find the correct tickets.
>
> -Matthias
>
> O
I like the idea with the special label. Otherwise, it will be difficult
to find the correct tickets.
-Matthias
On 08/21/2015 12:15 PM, Till Rohrmann wrote:
> I'm also in favor of JIRA, because I fear that nobody will keep the wiki
> page in sync. Maybe we can assign a special label for test stabi
I'm also in favor of JIRA, because I fear that nobody will keep the wiki
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.
On Fri, Aug 21, 2015 at 11:02 AM, Robert Metzger
wrote:
> I agree that w
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 be
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
11 matches
Mail list logo
