Performance tests failing on Darwin due to mixed environments
Since enabling the new Darwin runners we are seeing quite frequent CI failures in the Darwin jobs due to inconsistencies in compiler allocations across the new (nix-based) and old (homebrew-based) environments.
I believe that the new jobs exhibit higher allocations which may be due to the longer nix store paths. However, this is a bit concerning as I wouldn't expect that the stage2 compiler would be sensitive to this.