| 2e2e29c3e70abebaf4e56cadffeed37ccf862836 |
|
09-Jun-2015 |
Neil Fuller <nfuller@google.com> |
Explicitly set DateFormat.is24Hour value needed by tests
Some tests fail under CTS if the device is set to use the 24 hour clock.
The tests that depend on the value of the setting are now being explicit.
Bug: 20899571
Bug: 20937589
Bug: 20939139
Bug: 20378566
Bug: 21585934
Bug: https://code.google.com/p/android/issues/detail?id=162384
(cherry-picked from commit 38a0b85afd4231f46fac59e59ee38729bd5154c4)
Change-Id: I1a369baeeac929ef010e7906e92544b9f483f02c
|
| ad4a67f05d001ee1a9a1e9c0069db2d637223288 |
|
09-Jun-2015 |
Neil Fuller <nfuller@google.com> |
Explicitly set DateFormat.is24Hour value needed by tests
Some tests fail under CTS if the device is set to use the 24 hour clock.
The tests that depend on the value of the setting are now being explicit.
Bug: 20899571
Bug: 20937589
Bug: 20939139
Bug: 20378566
Bug: 21585934
Bug: https://code.google.com/p/android/issues/detail?id=162384
(cherry-picked from commit 38a0b85afd4231f46fac59e59ee38729bd5154c4)
Change-Id: Iac9eb15e8bf767bb5f3e96f9ba0486a995eef034
|
| 38a0b85afd4231f46fac59e59ee38729bd5154c4 |
|
09-Jun-2015 |
Neil Fuller <nfuller@google.com> |
Explicitly set DateFormat.is24Hour value needed by tests
Some tests fail under CTS if the device is set to use the 24 hour clock.
The tests that depend on the value of the setting are now being explicit.
Bug: 20899571
Bug: 20937589
Bug: 20939139
Bug: 20378566
Bug: 21585934
Bug: https://code.google.com/p/android/issues/detail?id=162384
Change-Id: I0f03f54b76dc5d343a2c842434412ff59908b129
|
| 0f702b5996488b8cc8cbe336e8098dd1b4de8dd3 |
|
18-Feb-2015 |
Narayan Kamath <narayan@google.com> |
Deal with quoted subformat patterns correctly.
This change might look like a hack, but the API it
implements is more than worthy of it.
bug: 19011159
Change-Id: I8a539f1b54282220fbb0a005a750819fa7873cc9
|
| ed1dd1f5a80c470eb9157a3ccc7285d4b1f1a0a6 |
|
15-Oct-2013 |
Elliott Hughes <enh@google.com> |
Fix a varargs warning in MessageFormatTest.
bdc was right.
Change-Id: I89c470d5deb4abcd0f3ecaeeac29da377e70eafb
|
| 74473971cc9d960376295fbcc430320c9ed62991 |
|
29-Aug-2013 |
Elliott Hughes <enh@google.com> |
Fix harmony java.text test failures.
There were plenty of bad tests here, but there were some real bugs too.
* DecimalFormat was only handling RoundingMode.UNNECESSARY for double
formatting.
* DecimalFormat was not ensuring that it's superclass' fields were
being correctly updated.
* NumberFormat was throwing NPE for a null object because of an
improved detail message, despite being specified to throw IAE.
* We weren't mapping NumberFormat.Field instances to the corresponding icu4c
UNUM_x_FIELD constant, so we weren't actually setting FieldPosition
objects correctly.
* SimpleDateFormat was not formatting milliseconds correctly with 'S'.
* NativeDecimalFormat wasn't handling JNI NewString OOME correctly.
Bug: 2528220
Bug: 3056865
Bug: 3057080
Bug: 3057090
Change-Id: Iac11f902f2e9649e596e7e7b7bc501b13e956fca
|
| 994e4e5ded616a100ca42b16cffa36aa9f595f64 |
|
28-Aug-2013 |
Elliott Hughes <enh@google.com> |
Add harmony java.text tests.
Change-Id: Id8d0acd77d08ff337b4851ae74a48cc002d66cd9
|