Mark Liu created BEAM-7627:
------------------------------
Summary: Jenkins build failed on "No space left on device"
Key: BEAM-7627
URL: https://issues.apache.org/jira/browse/BEAM-7627
Project: Beam
Issue Type: Bug
Components: build-system
Reporter: Mark Liu
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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
