Github user javadba commented on the pull request:

    https://github.com/apache/spark/pull/1586#issuecomment-51065193
  
    Hi,
      For some reason the CORE module testing has ballooned in overall testing 
time: it took over 7.5 hours to run. There was one timeout error out of 736 
tests - and it is quite unlikely to have anything to do with the code added in 
this PR.  
    
    Here is the test that failed and then the overall results:
    
    DriverSuite:
        Spark assembly has been built with Hive, including Datanucleus jars on 
classpath
        - driver should exit after finishing *** FAILED ***
          TestFailedDueToTimeoutException was thrown during property 
evaluation. (DriverSuite.scala:40)
            Message: The code passed to failAfter did not complete within 60 
seconds.
            Location: (DriverSuite.scala:41)
            Occurred at table row 0 (zero based, not counting headings), which 
had values (
              master = local
            )
    
      Tests: succeeded 723, failed 1, canceled 0, ignored 7, pending 0
        *** 1 TEST FAILED ***
        [INFO] 
------------------------------------------------------------------------
        [INFO] Reactor Summary:
        [INFO] 
        [INFO] Spark Project Parent POM ........................... SUCCESS [  
1.180 s]
        [INFO] Spark Project Core ................................. FAILURE [  
07:35 h]
    
    So I am not presently in a position to run regression tests - given the 
overall runtime will be doulbe-digit hours.  Would someone please run Jenkins 
on this code?  
    



---
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 [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to