The reason is that there is no printer installed, so it hangs when
printing starts,
when windows tries to ask the non-existent user where to send the output but
gets no response. jtreg then times out the test. So requiring a printer
should fix that.
I think the mystery is not why it times out now, but why it did not do
so earlier.
-phil.
On 5/29/19 1:33 PM, Sergey Bylokhov wrote:
Hi, Phil.
Should not we create a new CR to evaluate this failure later?
On 29/05/2019 12:30, Phil Race wrote:
Bug : https://bugs.openjdk.java.net/browse/JDK-8225007
Webrev : http://cr.openjdk.java.net/~prr/8225007/
This is just adding the printer keyword to two jtreg tests.
This is useful for both selecting & excluding the tests and should
prevent
one of these tests from hanging in our nightly headful testing.
-phil.
