How to run tests before pushing a backport changeset?

[Rob McKenna]

This is not quite correct:

On 27/02/19 10:43, Aleksey Shipilev wrote:
> Hi,
> 
> I see actual 12u maintainers have not replied yet, so I am willing to share my understanding.
> 
> On 2/26/19 8:04 PM, Man Cao wrote:
> > We have a follow-up question: is there any difference on the testing policy
> > for JDK12u? Should we seek sponsorship from one of the maintainers from
> > Oracle to run tests before pushing a backport changeset to JDK12u? Or could
> > we just run tier1 tests for fastdebug|release locally and then push?
> 
> It seems that jdk12u-fix-yes is only set when jdk12u-fix-SQE-ok is set. jdk12u-fix-SQE-ok is
> apparently done by Oracle-internal QA department, which probably indicates the patch went through
> the internal QA process? Anyway, jdk12u-fix-yes and local testing should be enough to push.

The SQE-ok keyword indicates that the fix can be accommodated by the
test plan.

> 
> > Also, any changeset that goes into jdk-updates/jdk12u should NOT affect the
> > soon-to-be-released JDK12 that is currently in Release Candidate phase,
> > right?
> 
> Yes, that is correct. JDK 12 Release Candidate is in jdk/jdk12, not in jdk-updates/jdk12u. Whatever
> you push to jdk-updates/jdk12u now would be in 12.0.2.

Correct.

I would like to see potential fixes pass tiers 1 & 2 of the affected area
(e.g. hs or jdk) but tier1 is *must* pass.

(http://mail.openjdk.java.net/pipermail/jdk9-dev/2015-June/002325.html)

    -Rob

> 
> -Aleksey
> 
>