On 9/23/2021 11:00 PM, Alan Bateman wrote:
On Thu, 23 Sep 2021 12:53:23 GMT, Aleksey Shipilev <sh...@openjdk.org> wrote:
Now that OpenJDK has more or less complete `tier{1,2,3,4}` definitions, let's
mention them in `testing.md`.
Current patch is my braindump, I am open for suggestions :)
Aleksey Shipilev has updated the pull request incrementally with one additional
commit since the last revision:
More fixes
Marked as reviewed by alanb (Reviewer).
doc/testing.html line 80:
78: <ul>
79: <li><p><code>tier1</code>: This is the lowest test tier. Multiple developers run these tests every day. Because of the
widespread use, the tests in <code>tier1</code> are carefully selected and optimized to run fast, and to run in the most stable manner. The
test failures in <code>tier1</code> are usually followed up on quickly, either with fixes, or adding relevant tests to problem list. GitHub
Actions workflows, if enabled, run <code>tier1</code> tests.</p></li>
80: <li><p><code>tier2</code>: This test group covers even more ground. These contain, among other
things, tests that either run for too long to be at <code>tier1</code>, or may require special configuration, or
tests that are less stable, or cover the broader range of less critical JVM and JDK features/components (for example,
jaxp).</p></li>
Thanks for the updates, I think it reads much better now.
A small suggestion is to change "less critical" to "non-core", and "jaxp" to
"XML" as I don't expect too many people know what JAXP is.
Catching up on email, for some belated context, the initial tired
testing email thread did included some discussion about what the tiered
were intended to mean including:
http://mail.openjdk.java.net/pipermail/jdk9-dev/2015-March/001991.html
Thanks,
-Joe
-------------
PR: https://git.openjdk.java.net/jdk/pull/5615
