Testlibrary changes need their own changesets
david.holmes at oracle.com
Mon Apr 7 01:49:07 UTC 2014
Unfortunately enhancements to the testlibrary infrastructure code tend
to be done in conjunction with the changes to the tests (and sometimes
corresponding VM changes) that need the enhancement. This makes it very
difficult (sometimes impossible) to backport updates to the testlibrary.
Can I suggest that all updates to the testlibrary classes be done under
their own CR (they can still be reviewed alongside the main changes) and
committed into a distinct changeset so that they can be readily backported.
More information about the hotspot-dev