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 test to display such flaky behavior. Cheers! Sachin -- Sachin Goel Computer Science, IIT Delhi m. +91-9871457685 |
HI Sachin,
Let's file ticket for it so we could try to address it. These flaky tests could cause confusion for contributors. Thanks, - Henry On Tue, Oct 13, 2015 at 7:14 AM, Sachin Goel <[hidden email]> 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 test to > display such flaky behavior. > > Cheers! > Sachin > -- Sachin Goel > Computer Science, IIT Delhi > m. +91-9871457685 |
Will do that tomorrow.
I'll need to find the build where the jvm ran out of heap space. Cheers! Sachin On Oct 13, 2015 10:45 PM, "Henry Saputra" <[hidden email]> wrote: > HI Sachin, > > Let's file ticket for it so we could try to address it. > These flaky tests could cause confusion for contributors. > > Thanks, > > > - Henry > > On Tue, Oct 13, 2015 at 7:14 AM, Sachin Goel <[hidden email]> > 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 test > to > > display such flaky behavior. > > > > Cheers! > > Sachin > > -- Sachin Goel > > Computer Science, IIT Delhi > > m. +91-9871457685 > |
In reply to this post by Sachin Goel
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.
– Ufuk > On 13 Oct 2015, at 16:14, Sachin Goel <[hidden email]> 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 test to > display such flaky behavior. > > Cheers! > Sachin > -- Sachin Goel > Computer Science, IIT Delhi > m. +91-9871457685 |
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" <[hidden email]> 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. > > – Ufuk > > > On 13 Oct 2015, at 16:14, Sachin Goel <[hidden email]> 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 test > to > > display such flaky behavior. > > > > Cheers! > > Sachin > > -- Sachin Goel > > Computer Science, IIT Delhi > > m. +91-9871457685 > > |
Free forum by Nabble | Edit this page |