How to run tests before pushing a backport changeset?

Martin Buchholz martinrb at google.com
Thu Feb 21 03:55:37 UTC 2019


On Wed, Feb 20, 2019 at 4:10 PM Aleksey Shipilev <shade at redhat.com> wrote:

> On 2/20/19 11:38 PM, Man Cao wrote:
> > I wonder if there is a recommended way to run automated tests before
> pushing a changeset to
> > jdk11u or jdk12u. Is there something like Submit Repo
> > <https://wiki.openjdk.java.net/display/Build/Submit+Repo> for the
> jdk-updates project?
> There is no submit repo for JDK updates.
>
> > I read the links on https://openjdk.java.net/projects/jdk-updates/, but
> couldn't find any
> > description on testing. Does the backporting process require running
> such automated tests before
> > pushing a changeset?
> I think it is maintainer's duty to decide if testing was enough (this is
> why Fix Request requires
> [1] to spell out what testing was done). That said, it seems the more
> tests you run, the more less
> chance backport would be problematic.
>

I'm surprised to see you say that, because you are the king of build/test
automation.
I prefer to lessen the burden on backport developers and instead invest in
better release testing automation (e.g. "presubmit queue").


More information about the jdk-updates-dev mailing list