We're experiencing a lot of failed CI builds with gcc lately. What happens is that the GA jobs are just stopped with Error: Process completed with exit code 143., indicating the job is simply killed for some reason. The running times widely vary so this is not about some timeout. I stumbled on actions/runner-images#6680 which is totally familiar.

Probably the recent changes we introduced (switching to C++20 and using more features from 20 following the sonarcloud reports) somehow increased the load on gcc, causing the builds to get killed.

Maybe switching to gcc 12 could help here. Also it would be an easy switch as version 12 is packaged for the Ubuntu images we're using on CI. Plus it's a good idea to update at some point anyway.