Github user ericl commented on the issue:

    https://github.com/apache/spark/pull/14690
  
    MiMa is supposed to detect binary incompatible changes. Looking at the 
console output though, it seems like MiMa just crashed.
    
    Running `./dev/mima` locally worked though, so maybe it was some transient 
jenkins issue.
    
    Btw, I noticed that this suite was failing in jenkins only.
    
    ```
    [info] - partitioned pruned table reports only selected files *** FAILED 
*** (610 milliseconds)
    [info]   
Array("file:/home/jenkins/workspace/SparkPullRequestBuilder@2/target/tmp/spark-e7d44560-5cc4-4d4c-b72c-7d68c1bd9de9/f1=2/f2=2",
 
"file:/home/jenkins/workspace/SparkPullRequestBuilder@2/target/tmp/spark-e7d44560-5cc4-4d4c-b72c-7d68c1bd9de9/f1=1/f2=1",
 
"file:/home/jenkins/workspace/SparkPullRequestBuilder@2/target/tmp/spark-e7d44560-5cc4-4d4c-b72c-7d68c1bd9de9/f1=4/f2=4",
 
"file:/home/jenkins/workspace/SparkPullRequestBuilder@2/target/tmp/spark-e7d44560-5cc4-4d4c-b72c-7d68c1bd9de9/f1=0/f2=0",
 
"file:/home/jenkins/workspace/SparkPullRequestBuilder@2/target/tmp/spark-e7d44560-5cc4-4d4c-b72c-7d68c1bd9de9/f1=3/f2=3")
 had length 5 instead of expected length 2 (HiveDataFrameSuite.scala:60)
    ```
    
    That's pretty weird, so I'll look into that (having acquired ssh access to 
jenkins).


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to