On Tue, 30 Jan 2024 10:34:40 GMT, Aleksey Shipilev wrote:
> See the description in the bug. This mitigates the issue by splitting out the
> only test job that has two test suites in it.
Marked as reviewed by clanger (Reviewer).
-
PR Review:
On Tue, 30 Jan 2024 19:05:02 GMT, Magnus Ihse Bursie wrote:
>> See the description in the bug. This mitigates the issue by splitting out
>> the only test job that has two test suites in it.
>
> I think this combination of two tests were made due to fear of too much
> overhead of creating a
On Tue, 30 Jan 2024 19:05:02 GMT, Magnus Ihse Bursie wrote:
> or was it just a premature optimization that is causing us headache now?
This one. When I did this originally, I thought why have another job when we
can stash some groups together? But the cost for additional job is not actually
On Tue, 30 Jan 2024 10:34:40 GMT, Aleksey Shipilev wrote:
> See the description in the bug. This mitigates the issue by splitting out the
> only test job that has two test suites in it.
I think this combination of two tests were made due to fear of too much
overhead of creating a small test
On Tue, 30 Jan 2024 10:34:40 GMT, Aleksey Shipilev wrote:
> See the description in the bug. This mitigates the issue by splitting out the
> only test job that has two test suites in it.
Marked as reviewed by erikj (Reviewer).
-
PR Review:
See the description in the bug. This mitigates the issue by splitting out the
only test job that has two test suites in it.
-
Commit messages:
- Revert test breakage and touchups
- Break the tier1_compiler test and see what happens
- Fix
Changes:
