bazelbuild
Investigate using —unlimit_coredumps on CI
@jmmv Is there any reason why I shouldn't just add this to the set of flags we use on Bazel's CI when calling Bazel? Otherwise I'll just do it.
The next question is how to get the core files when Bazel crashes on CI...
The downside of enabling this is that writing the core dumps takes a long time (they are multi-GB files) and they need to be pruned by hand to avoid wasting a ton of disk space. But this is CI, so if we crash, we want that information.
Also note that core dumps go into /cores by default, but you can customize their location via the kern.corefile sysctl property. The manpage in macOS doesn't seem to document the format, but https://www.freebsd.org/cgi/man.cgi?core(5) should mostly apply.
