On Tue, 30 Nov 2021 18:48:15 GMT, Aleksey Shipilev wrote:
> OpenJDK tiered tests definitions have the catch-all `tier4` that runs all
> tests not defined in the lower tiers. `hotspot:tier4` has lots of them,
> mostly long-running vmTestbase tests, which take many hours even on a very
>
On Tue, 30 Nov 2021 18:48:15 GMT, Aleksey Shipilev wrote:
> OpenJDK tiered tests definitions have the catch-all `tier4` that runs all
> tests not defined in the lower tiers. `hotspot:tier4` has lots of them,
> mostly long-running vmTestbase tests, which take many hours even on a very
>
On Tue, 30 Nov 2021 18:48:15 GMT, Aleksey Shipilev wrote:
> OpenJDK tiered tests definitions have the catch-all `tier4` that runs all
> tests not defined in the lower tiers. `hotspot:tier4` has lots of them,
> mostly long-running vmTestbase tests, which take many hours even on a very
>
On Mon, 6 Dec 2021 09:11:07 GMT, Aleksey Shipilev wrote:
>>> I've solicited feedback from core-libs folk as this affects them the most.
>>> At present we, Oracle, run the jdk_svc tests as part of hotspot testing,
>>> but this change will suddenly cause jdk testing to include them. That is
>>>
On Fri, 3 Dec 2021 07:34:16 GMT, Alan Bateman wrote:
> No objection to the change, I think it is just a re-balancing of tiers for CI
> systems.
Yes, quite. @dholmes-ora, are you happy with Alan's assessment?
-
PR: https://git.openjdk.java.net/jdk/pull/6619
On Thu, 2 Dec 2021 12:15:51 GMT, David Holmes wrote:
> I've solicited feedback from core-libs folk as this affects them the most. At
> present we, Oracle, run the jdk_svc tests as part of hotspot testing, but
> this change will suddenly cause jdk testing to include them. That is probably
>
On Thu, 2 Dec 2021 12:15:51 GMT, David Holmes wrote:
> I've solicited feedback from core-libs folk as this affects them the most. At
> present we, Oracle, run the jdk_svc tests as part of hotspot testing, but
> this change will suddenly cause jdk testing to include them. That is probably
>
On 2/12/2021 6:25 pm, Aleksey Shipilev wrote:
On Tue, 30 Nov 2021 18:48:15 GMT, Aleksey Shipilev wrote:
All right then. Thanks for followups!
Hi Aleksey,
I've solicited feedback from core-libs folk as this affects them the
most. At present we, Oracle, run the jdk_svc tests as part of
On Thu, 2 Dec 2021 08:21:30 GMT, Aleksey Shipilev wrote:
> All right then. Thanks for followups!
>
> @egahlin, @mgronlun: this affects JFR tests a bit, subsumes `jfr_tier_3` into
> `tier3`, basically. Are you good with this?
Seems reasonable.
I'm reluctant to become (R)eviewer on this, since
On Tue, 30 Nov 2021 18:48:15 GMT, Aleksey Shipilev wrote:
> OpenJDK tiered tests definitions have the catch-all `tier4` that runs all
> tests not defined in the lower tiers. `hotspot:tier4` has lots of them,
> mostly long-running vmTestbase tests, which take many hours even on a very
>
On Thu, 2 Dec 2021 02:00:11 GMT, Mikhailo Seledtsov
wrote:
>> Hi @shipilev ,
>> We need to have someone look at the impact of this on our CI. I don't think
>> we run the tier4 group as defined in our tier 4 so we may not see those
>> execution time savings that offset the extra cost to tier3.
On Wed, 1 Dec 2021 02:29:14 GMT, David Holmes wrote:
>> OpenJDK tiered tests definitions have the catch-all `tier4` that runs all
>> tests not defined in the lower tiers. `hotspot:tier4` has lots of them,
>> mostly long-running vmTestbase tests, which take many hours even on a very
>>
On Tue, 30 Nov 2021 18:48:15 GMT, Aleksey Shipilev wrote:
> OpenJDK tiered tests definitions have the catch-all `tier4` that runs all
> tests not defined in the lower tiers. `hotspot:tier4` has lots of them,
> mostly long-running vmTestbase tests, which take many hours even on a very
>
On Wed, 1 Dec 2021 02:29:14 GMT, David Holmes wrote:
> Hi @shipilev , We need to have someone look at the impact of this on our CI.
> I don't think we run the tier4 group as defined in our tier 4 so we may not
> see those execution time savings that offset the extra cost to tier3.
OK, I can
On Tue, 30 Nov 2021 18:48:15 GMT, Aleksey Shipilev wrote:
> OpenJDK tiered tests definitions have the catch-all `tier4` that runs all
> tests not defined in the lower tiers. `hotspot:tier4` has lots of them,
> mostly long-running vmTestbase tests, which take many hours even on a very
>
OpenJDK tiered tests definitions have the catch-all `tier4` that runs all tests
not defined in the lower tiers. `hotspot:tier4` has lots of them, mostly
long-running vmTestbase tests, which take many hours even on a very parallel
machines.
This, unfortunately, has a chilling effect on
16 matches
Mail list logo
