🐞 Github Actions build process received Segmentation fault signal and terminated, but the job is treated as successfully complete

[shoce]

What is the issue?

So i have a long-running build job and recently Github started stopping them with Segmentation fault (the builds finish successfully locally).

This is the job: https://github.com/shoce/tgbotserver/actions/runs/13333316328/job/37242559156

If you look under the "Run dagger/dagger-for-github@v7" you will see the messages:

...
59  : │ │ [2h20m38s] | c++: internal compiler error: Segmentation fault signal terminated program cc1plus
...
60  : │ │ Container.file ERROR [2h20m38s]
60  : │ │ ! process "/dev/.buildkit_qemu_emulator cmake --build . --target install" did not complete successfully: exit code: 2
41  : │ Tgbotserver.publish DONE [2h20m41s]
...

Before moving to Dagger building with a Dockerfile the same situation (Segmentation fault) was processed correctly as a failed run.

Dagger version

registry.dagger.io/engine:v0.15.4

Steps to reproduce

Not sure how to reproduce it locally, but in my case with Github actions it happens when a job is running longer than 20 minutes, sometimes longer than 2 hours, not obvious how to predict.

Log output

https://github.com/shoce/tgbotserver/actions/runs/13333316328/job/37242559156#step:4:2230