Fixed
Status Update
No update yet.
Comments
il...@google.com
We don't use any java.io.Closeable objects in our tests, so this is a bit concerning. I also can't reproduce this at all locally.
je...@google.com
Also interesting is the androidx_host_tests target has now encountered what looks like the same error: https://android-build.googleplex.com/builds/pending/P18822477/androidx_host_tests/latest/view/logs/build_error.log
> Task :fragment:fragment:testDebugUnitTest
System.logW: A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.java.lang.Throwable: Explicit termination method 'dispose' not called
System.logW: A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.java.lang.Throwable: Explicit termination method 'dispose' not called
System.logW: A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.java.lang.Throwable: Explicit termination method 'dispose' not called
> Task :fragment:fragment:testDebugUnitTest
System.logW: A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.java.lang.Throwable: Explicit termination method 'dispose' not called
System.logW: A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.java.lang.Throwable: Explicit termination method 'dispose' not called
System.logW: A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.java.lang.Throwable: Explicit termination method 'dispose' not called
il...@google.com
ap...@google.com
Project: platform/frameworks/support
Branch: androidx-main
commit 6ebaf3a90dd81f97685f82a7a8983536ea43f7d7
Author: Ian Lake <ilake@google.com>
Date: Mon Jan 11 16:57:06 2021
Destroy ActivityController at the end of unit tests
Ensure that each ActivityController created
via Robolectric.buildActivity() is properly
destroyed at the endd of the test.
Test: tests pass without Closeable warnings
BUG: 176979872
Change-Id: I5fcd7d3bff2a9df1ce764f9f6bfc24286cd29a58
M fragment/fragment/src/test/java/androidx/fragment/app/FragmentPagerAdapterRoboTest.kt
M fragment/fragment/src/test/java/androidx/fragment/app/FragmentRoboAnimTest.kt
https://android-review.googlesource.com/1546380
Branch: androidx-main
commit 6ebaf3a90dd81f97685f82a7a8983536ea43f7d7
Author: Ian Lake <ilake@google.com>
Date: Mon Jan 11 16:57:06 2021
Destroy ActivityController at the end of unit tests
Ensure that each ActivityController created
via Robolectric.buildActivity() is properly
destroyed at the endd of the test.
Test: tests pass without Closeable warnings
BUG: 176979872
Change-Id: I5fcd7d3bff2a9df1ce764f9f6bfc24286cd29a58
M fragment/fragment/src/test/java/androidx/fragment/app/FragmentPagerAdapterRoboTest.kt
M fragment/fragment/src/test/java/androidx/fragment/app/FragmentRoboAnimTest.kt
Description
The build athttps://android-build.googleplex.com/builds/submitted/7067732/androidx_host_tests_max_dep_versions/latest/view/logs/build_error.log failed due to generating this output:
If it happens more than a few times then I'll probably add an exemption for this output, but it'd be great if we could figure out why resources are sometimes leaking
Thanks!
This also looks related to