Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-2230 Improvements to Jenkins QA Harness
  3. SPARK-3076

Gracefully report build timeouts in Jenkins

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • None
    • 1.2.0
    • Build
    • None

    Description

      Copy of dev list thread:

      Jenkins runs for this PR https://github.com/apache/spark/pull/1960 timed out without notification. The relevant Jenkins logs are at

      https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18588/consoleFull
      https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18592/consoleFull
      https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18597/consoleFull

      On Fri, Aug 15, 2014 at 11:44 AM, Nicholas Chammas <nicholas.chammas@gmail.com> wrote:
      Shivaram,

      Can you point us to an example of that happening? The Jenkins console output, that is.

      Nick

      On Fri, Aug 15, 2014 at 2:28 PM, Shivaram Venkataraman <shivaram@eecs.berkeley.edu> wrote:
      Also I think Jenkins doesn't post build timeouts to github. Is there anyway
      we can fix that ?
      On Aug 15, 2014 9:04 AM, "Patrick Wendell" <pwendell@gmail.com> wrote:

      > Hi All,
      >
      > I noticed that all PR tests run overnight had failed due to timeouts. The
      > patch that updates the netty shuffle I believe somehow inflated to the
      > build time significantly. That patch had been tested, but one change was
      > made before it was merged that was not tested.
      >
      > I've reverted the patch for now to see if it brings the build times back
      > down.
      >
      > - Patrick
      >

      Attachments

        Activity

          People

            nchammas Nicholas Chammas
            nchammas Nicholas Chammas
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: