We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Actions to build daily SDK is failing and not published on aarch64 these days.
This is because GitHub seems to change disk layout of runners recently, which causes easimon/maximize-build-space no longer works as expected, as reported in easimon/maximize-build-space#48.
In concrete, looking at an recent build log, using this action rather eats rootfs.
Before running this action, we have 46 GiB space on rootfs, which is enough to build our SDK:
Memory and swap: total used free shared buff/cache available Mem: 16342544 512020 14818212 57796 1012312 15543588 Swap: 3145724 0 3145724 NAME TYPE SIZE USED PRIO /swapfile file 3G 0B -2 Available storage: Filesystem Size Used Avail Use% Mounted on /dev/root 73G 28G 46G 38% / tmpfs 7.8G 204K 7.8G 1% /dev/shm tmpfs 3.2G 1008K 3.2G 1% /run tmpfs 5.0M 0 5.0M 0% /run/lock efivarfs 128M 16K 128M 1% /sys/firmware/efi/efivars /dev/sda15 98M 6.3M 92M 7% /boot/efi tmpfs 1.6G 12K 1.6G 1% /run/user/1001
After running this action, there are almost no space on rootfs:
Memory and swap: total used free shared buff/cache available Mem: 16342544 546256 14674280 63324 1122008 15502072 Swap: 1048572 0 1048572 NAME TYPE SIZE USED PRIO /dev/dm-0 partition 1024M 0B -2 Available storage: Filesystem Size Used Avail Use% Mounted on /dev/root 73G 73G 100M 100% / tmpfs 7.8G 204K 7.8G 1% /dev/shm tmpfs 3.2G 1016K 3.2G 1% /run tmpfs 5.0M 0 5.0M 0% /run/lock efivarfs 128M 16K 128M 1% /sys/firmware/efi/efivars /dev/sda15 98M 6.3M 92M 7% /boot/efi tmpfs 1.6G 12K 1.6G 1% /run/user/1001 /dev/mapper/buildvg-buildlv 46G 24K 46G 1% /home/runner/work/flatpak-platform/flatpak-platform
Our SDK build succeeds.
8.x (Circe)
Classic Session (X11, This is the default)
Compiled from git
No response
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
What Happened?
Actions to build daily SDK is failing and not published on aarch64 these days.
This is because GitHub seems to change disk layout of runners recently, which causes easimon/maximize-build-space no longer works as expected, as reported in easimon/maximize-build-space#48.
In concrete, looking at an recent build log, using this action rather eats rootfs.
Before running this action, we have 46 GiB space on rootfs, which is enough to build our SDK:
After running this action, there are almost no space on rootfs:
Steps to Reproduce
Expected Behavior
Our SDK build succeeds.
OS Version
8.x (Circe)
Session Type
Classic Session (X11, This is the default)
Software Version
Compiled from git
Log Output
Hardware Info
No response
The text was updated successfully, but these errors were encountered: