Hi Sergey,
The general tiered testing policy is described in:
http://mail.openjdk.java.net/pipermail/jdk9-dev/2015-March/001991.html
with tier 3 specifically discussed in
http://mail.openjdk.java.net/pipermail/jdk9-dev/2015-June/002325.html
Quoting from the latter:
As a reminder, JDK 9 is now using a tiered testing policy where about
9,000 tests have been placed into one of two tiers, with tier 1 tests
having a stricter policy on passing than tier 2. [1] The overall policy
is that tier 1 tests should always pass in master and that integrations,
both dev -> master and hotspot main -> dev, should preserve the property
that all tier 1 tests pass. In addition, only a limited number of tier 2
tests should fail.
[...]
The next iteration of refining tiered testing is to add a third tier,
tier 3. The initial tier 1 and tier 2 test definitions did not include
any client library tests. As mentioned as a possibility in the earlier
tiered testing proposal, tier 3 can start hosting client library tests,
beginning with sets of tests which do not require a "headful"
environment. [5] Detailed discussions about which test sets to include
will be conducted with the appropriate client libs teams.
As a point of comparison, the automated beans and imageio tests are
already in tier 3.
Thanks,
-Joe
On 8/27/2015 9:31 AM, Sergey Bylokhov wrote:
Hi, Joe.
Can you clarify a little bit a "tier 3"?
On 27.08.15 3:14, joe darcy wrote:
Hello,
Please review the changes below for
JDK-8134554: Add sound tests to tier 3
Thanks,
-Joe
diff -r ee8b1bc2f534 test/TEST.groups
--- a/test/TEST.groups Thu Aug 27 07:52:12 2015 +0800
+++ b/test/TEST.groups Wed Aug 26 17:12:23 2015 -0700
@@ -50,7 +50,8 @@
tier3 = \
:jdk_rmi \
:jdk_beans \
- :jdk_imageio
+ :jdk_imageio \
+ :jdk_sound
###############################################################################
#
