Eugen Martynov10/24/2023, 12:07 PM
From the past I remember it is probably due to memory limit. I’m trying to revamp all memory parameters for gradle and kotlin for the build.
The message received from the daemon indicates that the daemon has disappeared.
kaeawc10/24/2023, 12:45 PM
Eugen Martynov10/24/2023, 1:41 PM
kaeawc10/24/2023, 2:05 PM
Eugen Martynov10/24/2023, 2:26 PM
kaeawc10/24/2023, 2:27 PM
Eugen Martynov10/24/2023, 2:27 PM
kaeawc10/24/2023, 2:28 PM
Eugen Martynov10/24/2023, 2:28 PM
kaeawc10/24/2023, 2:29 PM
Eugen Martynov10/24/2023, 2:31 PM
kaeawc10/24/2023, 2:33 PM
Eugen Martynov10/24/2023, 2:34 PM
The relevant memory limits and default allocations are as follows: Regular steps have 4096 MB of memory in total, large build steps (which you can define using size: 2x) have 8192 MB in total. The build container is given 1024 MB of the total memory, which covers your build process and some Pipelines overheads (agent container, logging, etc). The total memory for services on each pipeline step must not exceed the remaining memory, which is 3072/7128 MB for 1x/2x steps respectively. Service containers get 1024 MB memory by default, but can be configured to use between 128 MB and the step maximum (3072/7128 MB). The Docker-in-Docker daemon used for Docker operations in Pipelines is treated as a service container, and so has a default memory limit of 1024 MB. This can also be adjusted to any value between 128 MB and 3072/7128 MB by changing the memory setting on the built-in docker service in the definitions section.
kaeawc10/24/2023, 2:39 PM
Eugen Martynov10/24/2023, 2:45 PM