Write detail into logs if step get's killed by resource limits #69

loke commented 2022年08月08日 12:38:55 +02:00

I'm getting random errors when running a build. In the following example, the gradle daemon seems to have been killed while compiling:

1934 The message received from the daemon indicates that the daemon has disappeared.
1935 Build request sent: Build{id=e93f53ee-9c13-48c7-8df1-b96c07911052, currentDir=/woodpecker/src/codeberg.org/loke/array}
1936 Attempting to read last messages from the daemon log...
1937 Daemon pid: 5571
1938 log file: /root/.gradle/daemon/7.3/daemon-5571.out.log

I have also had other random test failues. If I restart the build, it seems to work.

Here the link to the failure: https://ci.codeberg.org/loke/array/build/14/3

I'm getting random errors when running a build. In the following example, the gradle daemon seems to have been killed while compiling: ``` 1934 The message received from the daemon indicates that the daemon has disappeared. 1935 Build request sent: Build{id=e93f53ee-9c13-48c7-8df1-b96c07911052, currentDir=/woodpecker/src/codeberg.org/loke/array} 1936 Attempting to read last messages from the daemon log... 1937 Daemon pid: 5571 1938 log file: /root/.gradle/daemon/7.3/daemon-5571.out.log ``` I have also had other random test failues. If I restart the build, it seems to work. Here the link to the failure: https://ci.codeberg.org/loke/array/build/14/3

loke commented 2022年08月08日 12:40:22 +02:00

It would also be helful if it was possible to retrieve files from the image after the build failed. In the case of Kotlin test results, the build generates a HTML file in the build idrectory that contains all details. It would be very useful to be able to access this file.

It would also be helful if it was possible to retrieve files from the image after the build failed. In the case of Kotlin test results, the build generates a HTML file in the build idrectory that contains all details. It would be very useful to be able to access this file.

6543 commented 2022年08月08日 16:58:36 +02:00

" ... well it's java and that eat a lot of ram
so it could be that you got hit by the ram limit ..."

so I'll change this issue into a feature request ...

" ... well it's java and that eat a lot of ram so it could be that you got hit by the ram limit ..." so I'll change this issue into a feature request ...