JDK submit repo
goetz.lindenmaier at sap.com
Tue Mar 6 21:36:14 UTC 2018
Thanks for the quick answer!
At SAP, we can put the patch into our nightly build, which then
- hotspot or jdk (not headful) jtreg tests depending on repo (almost all)
- a huge subset of jck tests (excluding those not stable or requiring tester action)
in a variety of compile modes (tiered, c1, c2, Xcomp Xbatch)
- some SAP applications
- spec benchmarks
We run all this with the fastdebug and/or release build on the platforms
ntintel, ntamd, linuxppc64, linuxppc64le, linuxs390x, linuxx86_64
So basically this should suffice to catch bigger flaws , but
there can always be just this one test missing you expect always
> -----Original Message-----
> From: Philip Race [mailto:philip.race at oracle.com]
> Sent: Tuesday, March 6, 2018 7:19 PM
> To: Vladimir Kozlov <vladimir.kozlov at oracle.com>
> Cc: Lindenmaier, Goetz <goetz.lindenmaier at sap.com>; jdk-
> dev at openjdk.java.net
> Subject: Re: JDK submit repo
> And it definitely isn't enough for UI client changes .. there are just
> some subset of the image i/o & beans tests that maybe run.
> You may not need to ask anyone at Oracle but you at least would need to
> locally run the jtreg "jdk_desktop" tests in such cases.
> On 3/6/18, 10:05 AM, Vladimir Kozlov wrote:
> > My understanding is currently it is not enough for *HotSpot* changes.
> > You still need to ask for sponsor to run additional Hotspot tests.
> > Regards,
> > Vladimir
> > On 3/6/18 6:51 AM, Lindenmaier, Goetz wrote:
> >> Hi,
> >> What is the status of the tests executed on the JDK submit repo?
> >> Can I push my change if it passes these tests? Or are there still
> >> tests missing that would be executed by Oracle engineers if they
> >> sponsor? Are these relevant?
> >> Best regards,
> >> Goetz.
More information about the jdk-dev