Re: macOS Sonoma bulk build rust failures

[Greg Troxel <gdt%lexort.com@localhost>]

Jonathan Perkin <jperkin%mnx.io@localhost> writes:

> This is enough to reliably kill check-portability.sh.  The only
> workaround is to restart the bulk build and only build rust by itself
> so that all the other sandboxes are idle.
>
> If anyone has any ideas for workarounds here I'd love to hear them.
> Adding _ULIMIT_CMD to mk/check just feels all sorts of wrong :(

In general, I think it would be  nice if we had some per-package db of
needed resources, like size of workdir and perhaps cpu time, and now
this rlimit :-) and would have the pbulk scheduler only start workers if
there are adequate resources.  So rust would be coded as piggy and be
run with no others, sort of how you are doing in manually in the end,
but automatically.

This would help small bulk builders, who can run 10 jobs of reasonable
size but only one firefox (just making that up, but some value of 10 I
bet it's roughly true).