spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Rosen <rosenvi...@gmail.com>
Subject Re: Test failures after Jenkins upgrade
Date Mon, 15 Dec 2014 19:30:31 GMT
Opened one more PR for this: https://github.com/apache/spark/pull/3704


On December 15, 2014 at 10:59:00 AM, Patrick Wendell (pwendell@gmail.com) wrote:

Ah cool Josh - I think for some reason we are hitting this every time  
now. Since this is holding up a bunch of other patches, I just pushed  
something ignoring the tests as a hotfix. Even waiting for a couple  
hours is really expensive productivity-wise given the frequency with  
which we run tests. We should just re-enable them when we merge the  
appropriate fix.  

On Mon, Dec 15, 2014 at 10:54 AM, Josh Rosen <rosenville@gmail.com> wrote:  
> There's a JIRA for this: https://issues.apache.org/jira/browse/SPARK-4826  
>  
> And two open PRs:  
>  
> https://github.com/apache/spark/pull/3695  
> https://github.com/apache/spark/pull/3701  
>  
> We might be close to fixing this via one of those PRs, so maybe we should  
> try using one of those instead?  
>  
> On December 15, 2014 at 10:51:46 AM, Patrick Wendell (pwendell@gmail.com)  
> wrote:  
>  
> Hey All,  
>  
> It appears that a single test suite is failing after the jenkins  
> upgrade: "org.apache.spark.streaming.rdd.WriteAheadLogBackedBlockRDDSuite".  
> My guess is the suite is not resilient in some way to differences in  
> the environment (JVM, OS version, or something else).  
>  
> I'm going to disable the suite to get the build passing. This should  
> be done in the next 30 minutes or so.  
>  
> - Patrick  
>  
> ---------------------------------------------------------------------  
> To unsubscribe, e-mail: dev-unsubscribe@spark.apache.org  
> For additional commands, e-mail: dev-help@spark.apache.org  
>  

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message