Lack of storage space in Autoware.Auto fork gitlab-runners for CI
Description
Right now the CI cannot pass the coverage job in the Autoware.Auto forks.
It doesn't occur on main repository because our runners now have 30GB storage space.
I have added a small df -H
command to the coverage.sh
and this is the result:
Filesystem Size Used Avail Use% Mounted on
overlay 22G 12G 11G 52% /
tmpfs 68M 0 68M 0% /dev
tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup
/dev/sda1 22G 12G 11G 52% /builds
shm 68M 0 68M 0% /dev/shm
tmpfs 2.0G 0 2.0G 0% /sys/devices/virtual/dmi/id
This means generic shared runners gitlab provides have about 22GB disk space and a built Autoware.Auto and the OS currently fills up 12GB of it. And running another build operation makes it run out of space.
I've put 4 dh -H
commands in the coverage.sh
file to debug, it only prints the first one and fails at the colcon build
command at https://gitlab.com/atsunori_yasuda.esol/AutowareAuto/-/blob/44850209835b9b709a470b1f1bcbf235c02cf6ee/tools/coverage/coverage.sh#L42
I am now testing if it will build if I remove the old build folders with rm -rf build/ install/ log/
in this commit.
If it passes, I will create an MR and hopefully it will solve the space issues in forks too.
How to Reproduce
Run the CI in an Autoware.Auto fork.
Current Behavior
Forks cannot pass the coverage phase.
Expected behavior
Forks pass the coverage phase.