+1
On 1/27/2016 5:26 AM, Stephen Colebourne wrote:
From the name of the test and looking at the code, running in English only
is fine.
Stephen
On 27 January 2016 at 05:53, Masayoshi Okutsu <masayoshi.oku...@oracle.com>
wrote:
Looks OK to me. But I'd like some java.time people to review this change
to see if the intention of this test is to run only in English.
Thanks,
Masayoshi
On 1/27/2016 1:51 PM, Ramanand Patil wrote:
Hi all,
Please help me in reviewing this test fix.
Regards,
Ramanand.
From: Ramanand Patil
Sent: Monday, January 25, 2016 1:05 PM
To: i18n-...@openjdk.java.net
Cc: core-libs-dev@openjdk.java.net
Subject: <i18n dev>RFR: JDK-8147912: test "parseWithZoneWithoutOffset" of
java/time/tck/java/time/format/TCKDTFParsedInstant.java fail on de_DE locale
Hi all,
Please review the trivial test bug fix for:
https://bugs.openjdk.java.net/browse/JDK-8147912
Bug Description: Since the test case "parseWithZoneWithoutOffset" is
using hard code as input data it will fail on some non-English locales
(de_DE locale).
Webrev: http://cr.openjdk.java.net/~rpatil/8147912/webrev.00
Fix: Even though hardcoded data is not preferred in compatibility test
cases, this case was exception. English is provided as the default locale
data for DateTimeFormatter in this testcase.
Regards,
Ramanand.
