ci: fix intermittent build failures and some other things #80
Conversation
|
Build artifacts for this PR are available: You can download these artifacts from the "Artifacts" section of the workflow run. |
Code Coverage Report
|
📊 Code Coverage Summary
|
📊 Code Coverage Summary
|
1 similar comment
📊 Code Coverage Summary
|
|
Build artifacts for this PR are available: You can download these artifacts from the "Artifacts" section of the workflow run. |
📊 Code Coverage Summary
|
📊 Code Coverage Summary
|
|
Build artifacts for this PR are available: You can download these artifacts from the "Artifacts" section of the workflow run. |
📊 Code Coverage Summary
|
williscool
force-pushed
the
ci/fix_test_reporting_maybe_other_nicetys
branch
from
d6946ad to
9534179
Compare
|
Build artifacts for this PR are available: You can download these artifacts from the "Artifacts" section of the workflow run. |
📊 Code Coverage Summary
|
|
Build artifacts for this PR are available: You can download these artifacts from the "Artifacts" section of the workflow run. |
for now just deletes problematic node_modules files but could be used for whatever makes the build work on windows
📊 Code Coverage Summary
|
…ion line execution 'ANDROIDX_TEST_ORCHESTRATOR' weird that it only broke cAT but not the instrument runner
|
Build artifacts for this PR are available: You can download these artifacts from the "Artifacts" section of the workflow run. |
📊 Code Coverage Summary
|
williscool
changed the title
HUGE intermittent build failure fix!
What Was the Problem?
Some Android instrumentation tests were intermittently failing with a
NullPointerException(NPE) when the system tried to accessResources.getConfiguration()on a mockedContext. This happened because the mock context returned a realResourcesobject, but the underlyingConfigurationwasnullin the test environment. This caused failures during test setup or when Android tried to bind the application context.this was causing reporting to break (as it caused the app would crash and break the xml listener )
Why Did This Happen?
every { getResources() } returns realContext.resourcesto delegate resource calls to the real context.Resourcesobject sometimes had anullConfigurationproperty, which is not expected in production.getConfiguration()on thisResourcesobject, it triggered an NPE.How Was It Fixed?
Resourcesobject using MockK.Configurationobject:will add more docs about it to next pr but this is blocking all builds so just going to merge now.
also