Self-hosted Github action runner takes forever on SDK

I was trying to make sense why I waste so much time when compiling my home-brewed packages against OpenWrt SDK on Github self-hosted runner nodes and now I can reproduce it in a much simpler way :

While a simple make package/toolchain/compile V=s will complete in a second On any SDK, it takes an eternal sunshine of a spotless mind to finish on a github self-hosted action-runner node.

This is the last line that shows up on my github logs that takes more than 20 minutes to finish :

/actions-runner/_work/testrepo/testrepo/openwrt-sdk-24.10.5-ath79-nand_gcc-13.3.0_musl.Linux-x86_64/staging_dir/host/bin/fakeroot /actions-runner/_work/testrepo/testrepo/openwrt-sdk-24.10.5-ath79-nand_gcc-13.3.0_musl.Linux-x86_64/staging_dir/host/bin/bash /actions-runner/_work/testrepo/testrepo/openwrt-sdk-24.10.5-ath79-nand_gcc-13.3.0_musl.Linux-x86_64/scripts/ipkg-build -m "" /actions-runner/_work/testrepo/testrepo/openwrt-sdk-24.10.5-ath79-nand_gcc-13.3.0_musl.Linux-x86_64/build_dir/target-mips_24kc_musl/toolchain/ipkg-mips_24kc/libgcc /actions-runner/_work/testrepo/testrepo/openwrt-sdk-24.10.5-ath79-nand_gcc-13.3.0_musl.Linux-x86_64/bin/targets/ath79/nand/packages

They add artificial pauses between free workflow steps.... Just use your own container

1 Like