Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-7627

Jenkins build failed on "No space left on device"

Details

    • Bug
    • Status: Resolved
    • P2
    • Resolution: Duplicate
    • None
    • Not applicable
    • build-system
    • None

    Description

      https://builds.apache.org/job/beam_PreCommit_Portable_Python_Commit/4382/console

      ```
      00:02:19.095 java.lang.IllegalStateException: java.io.IOException: No space left on device
      00:02:19.095 at com.gradle.scan.a.e.b.flush(SourceFile:233)
      00:02:19.095 at com.gradle.scan.a.e.b.close(SourceFile:244)
      00:02:19.095 at com.gradle.scan.a.e.c.close(SourceFile:68)
      00:02:19.095 at com.gradle.scan.plugin.internal.k.a(SourceFile:88)
      00:02:19.095 at com.gradle.scan.plugin.internal.e.c.c.b(SourceFile:121)
      00:02:19.095 at com.gradle.scan.plugin.internal.e.c.c.a(SourceFile:113)
      00:02:19.095 at com.gradle.scan.plugin.internal.o.a$a.a(SourceFile:30)
      00:02:19.095 at com.gradle.scan.plugin.internal.o.a$a.a(SourceFile:19)
      00:02:19.095 at com.gradle.scan.plugin.internal.o.a.c(SourceFile:60)
      00:02:19.095 Caused by: java.io.IOException: No space left on device
      00:02:19.095 at com.gradle.scan.a.e.b.flush(SourceFile:231)
      00:02:19.095 ... 8 more
      ```

      Looks like there is not enough space (disk?) on Jenkins worker for a build. If I remember correctly, a worker will run max of two build jobs concurrently. Not sure if it's caused by huge resource utilization in runtime, parallel execution or resource leak. For the third case, we should cleanup the worker and find out the leak place.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              markflyhigh Mark Liu
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: