New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable integration_tests:sparsearray tests #7006
Enable integration_tests:sparsearray tests #7006
Conversation
Oh, it also fixes "sparsearray" not found when executing |
Oh, looks like |
After enabling those tests, looks like they can't find |
I believe as-is the @JuliaSullivanGoogle is working on a change that adds a system property to disable preinstrumented jars, which will be used in the GitHub CI. It might slow things down a small amount, but not significantly. When we do another release and release a new set of preinstrumented jars, we can switch back to using them in GitHub CI. |
Oh, I forget preinstrumented jar. It actually failed on my local machine, and I just push related commit to this PR for testing and reviewing.
That's cool. It's very useful for GitHub CI and local testing/debugging. I will keep this PR to draft state, and wait @JuliaSullivanGoogle 's system property to disable preinstrumented jar. |
…fault. Some changes only occur when a new version of the jars are released. This will ensure all changes are tested when copied over. This will allow integration_tests:sparsearray to run in Gradle before a new version of preinstrumented jars are released. Related to #7006 PiperOrigin-RevId: 428547156
…fault. Some changes only occur when a new version of the jars are released. This will ensure all changes are tested when copied over. This will allow integration_tests:sparsearray to run in Gradle before a new version of preinstrumented jars are released. Related to #7006 PiperOrigin-RevId: 428547156
…fault. Some changes only occur when a new version of the jars are released. This will ensure all changes are tested when copied over. This will allow integration_tests:sparsearray to run in Gradle before a new version of preinstrumented jars are released. Related to #7006 PiperOrigin-RevId: 428547156
…fault. Some changes only occur when a new version of the jars are released. This will ensure all changes are tested when copied over. This will allow integration_tests:sparsearray to run in Gradle before a new version of preinstrumented jars are released. Related to #7006 PiperOrigin-RevId: 428547156
I will rebase and check it again, today. |
622c375
to
5d49802
Compare
Very strange that some tests are skipped:
|
Okay, I found the reason: the current config uses legacy resource, and it is not supported after P with thrown exception from |
5d49802
to
33265c3
Compare
Fixed by transferring to use Robolectric's Android module plugin to enable Anyway, I think this PR is ready for reviewing. cc /@hoisie . |
33265c3
to
6a25900
Compare
It's strange: |
f2a625f
to
e32adea
Compare
Looks like this PR triggers ICU building for instrumentation-tests on Emulator, and it failed with some reasons. |
3223729
to
03bbc7e
Compare
multidex error raised for sparsearray. |
13109ff
to
b813d91
Compare
The BTW, will i4 version of preinstrumented jars published recent days? |
@utzcoz preinstrumented jars got bumped, also 4.8-alpha-1 is released, so this should be unblocked? |
Yup. I will rebase and rerun checking today. |
After included, Android Studio will mark directories for source code correctly. Signed-off-by: utzcoz <utzcoz@outlook.com>
Signed-off-by: utzcoz <utzcoz@outlook.com>
Signed-off-by: utzcoz <utzcoz@outlook.com>
b813d91
to
e823a12
Compare
After included, Android Studio will mark directories for source code correctly.