| cf08dd1c5a225ea0137e390e1976ce1fd77f0ff4 |
|
07-Nov-2017 |
Neil Fuller <nfuller@google.com> |
DO NOT MERGE: Remove test that depends on tz data
Commenting out a test that will pass with <= 2017b
time zone data but fail on >= 2017c time zone data.
The has been removed for historic CTS releases because
there should be adequate coverage from the other tests
and it would be more complicated to provide a test
that works on a range of devices. We can expect OEMs
to release system images for releases >= O with 2017c
data. The affected test does not exist prior to O.
Bug: 68878031
Test: build only
Change-Id: I4320d6145a9d6506b5f427069a4fe0906158b070
(cherry picked from commit 5674120f14053d74822bae107c21a4150c4cb728)
|
| 5674120f14053d74822bae107c21a4150c4cb728 |
|
07-Nov-2017 |
Neil Fuller <nfuller@google.com> |
DO NOT MERGE: Remove test that depends on tz data
Commenting out a test that will pass with <= 2017b
time zone data but fail on >= 2017c time zone data.
The has been removed for historic CTS releases because
there should be adequate coverage from the other tests
and it would be more complicated to provide a test
that works on a range of devices. We can expect OEMs
to release system images for releases >= O with 2017c
data. The affected test does not exist prior to O.
Bug: 68878031
Test: build only
Change-Id: I4320d6145a9d6506b5f427069a4fe0906158b070
|
| 772deb8892ef033f3bd8fed70d9536142e454299 |
|
07-Nov-2017 |
Neil Fuller <nfuller@google.com> |
Fix OpenJDK TCK test after 2017c update
A 2017c data change for historic transitions broke one
of the upstream tests. See also
https://bugs.openjdk.java.net/browse/JDK-8190259
Bug: 68878031
Test: run cts -m CtsLibcoreOjTestCases -t tck.java.time.zone.TCKZoneRules
Change-Id: I6c15c0a19202d1ad90ec7d05b6e01750e0815849
|
| 6975f84c2ed72e1e26d20190b6f318718c849008 |
|
01-Mar-2017 |
Tobias Thierer <tobiast@google.com> |
Make Android patch docs in ojluni more consistent with style guide
This CL consists of an automated and a manual part (originally
reviewed as separate CLs, then squashed together before submitting
in order to minimize the number of times each Android-changed line
is touch, since that makes future git archaeology on these simpler).
Automated part: Run the following command (performs regex replacements):
find ojluni -name \*\.java | xargs sed -i \
-e 's/Android[- ]changed/Android-changed/ig' \
-e 's/Android-changed :/Android-changed:/g' \
-e 's/Android-changed \(BEGIN\|END\)/\1 Android-changed/g' \
-e 's/Android-changed - /Android-changed: /g' \
-e 's/Android[- ]removed/Android-removed/ig' \
-e 's/Android-removed :/Android-removed:/g' \
-e 's/Android-removed \(BEGIN\|END\)/\1 Android-removed/g' \
-e 's/Android-removed - /Android-removed: /g' \
-e 's/Android[- ]added/Android-added/ig' \
-e 's/Android-added :/Android-added:/g' \
-e 's/Android-added \(BEGIN\|END\)/\1 Android-added/g' \
-e 's/Android-added - /Android-added: /g' \
-e 's/----- \(BEGIN\|END\) android\( -----\)\?/\1 Android-changed/g' \
-e 's/\/\* \(BEGIN\|END\) Android-changed \*\//\/\/ \1 Android-changed/g'
Manual part: Move BEGIN Android-* lines out of block comments
Some Android-{changed,removed,added} lines occurred inside block comments.
This CL targets places in ojluni that contained the String "* BEGIN Android-"
Changes made by this CL include:
- Move the "BEGIN Android-" line into a line comment (the style guide
mandates that "Android-" lines are always in line comments). In many
cases, that line comment is immediately followed by a block comment
holding commented-out upstream code.
- Add corresponding "// END Android-" line comments, where missing.
- Drop documented import changes altogether. These create noise for
little benefit:
(1.) Most import problems will be found at compile time
(2.) They generally correspond to documented changes elsewhere in
the file.
- In most cases, the phrasing of comments and the decision whether to
keep commented out upstream code was not changed by this CL.
- Some additional tweaks were made in line with the style guide.
No attempt was made to:
- Verify that commented-out upstream code actually matches the
current upstream.
- Make any fixes (eg. to comments) that would have required
git archaeology (looking up historic commits).
Bug: 35841464
Test: make droid cts update-api
Change-Id: Ibc60979cb6061cfb0e9c7096cc9dcab30ddfa733
|
| 6540d509192372a74098bb4b36ba5d7b6afb91ac |
|
23-Nov-2016 |
Joachim Sauer <jsauer@google.com> |
Modify test assumptions.
Modify test assumptions that are not true on Android, for several
reasons:
- java.time RI uses non-CLDR data sources by default which has slightly
different data, whereas Android basically uses CLDR for almost
everything.
- Arabic locale actually uses arabic digits
- Portuguese month names are not capitalized in CLDR
- Russian month names are not capitalized in CLDR and use a full stop
after abbreviations
- java.time RI uses an older CLDR version, so many data points such as
format patterns have seen significant changes in the one we use
(currently CLDR 31).
- field names use lower case for locale en in CLDR
- change Locale in TCKFormatStyle because en_US doesn't use "CEST" as an
abbreviation for european time zones in CLDR, but en_GB does.
- TCK ZoneRule assumes an optimization that our data source doesn't
contain and are not necessary for correct operation.
Bug: 28832222
Test: artrun testng-time.xml
Change-Id: I42edefb052c9c2f007f971abe70740feb92a3a17
|
| c9dd3385ea6f927052783f42fb1282fb093e636e |
|
01-Sep-2016 |
Joachim Sauer <jsauer@google.com> |
Initial import of java.time.
This is a verbatim copy of the classes in java.time from the jdk8u60
branch of the OpenJDK.
They are not yet part of the build and wouldn't compile yet (no local
modifications whatsoever).
Bug: 28832222
Test: Not build, not tested.
Change-Id: I8bb148cb1095b08af895c4abffed9f22b107c218
|