resolve failing CI

[epicadk]

IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).

Fixes #[issue number]

Description
Clear and concise code change description.

Alternative(s) considered
Have you considered any alternatives? And if so, why have you chosen the approach in this PR?

Type
Choose one: (Bug fix | Feature | Documentation | Testing | Code health | Builds | Releases | Other)

Screenshots (if applicable)

Checklist

• I have read and acknowledged the Code of conduct
• I have read the Contributing page
• I have signed the Google Individual CLA, or I am covered by my company's Corporate CLA
• I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach
• I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the style guide of this project
• I have run ./gradlew check and ./gradlew connectedCheck to test my changes locally
• I have built and run the reference app(s) to verify my change fixes the issue and/or does not break the reference app(s)

[FikriMilano]

@epicadk In my case, I got an OOM the last time I pushed a code. Works fine locally though

[epicadk]

@epicadk In my case, I got an OOM the last time I pushed a code. Works fine locally though

Yeah what's weird is this time it's failing only on the coverage step (where I increased the ram). Perhaps it's an issue with SqlCipher?

[jingtang10]

@stevenckngaa not sure if you can shed a light on this.

What i've noticed locally is that if i run the instrumentation tests on my pixel6 everything passes, but if i run it on nokia 4.2 it fails.

so i wonder if this is related to any recent emulator update similar to what happened in ReactiveCircus/android-emulator-runner#160

i am also trying to resolve this in #1118 but haven't gone very far

[jingtang10]

doesn't look like the change worked :(

[epicadk]

not a ram issue maybe bumping the dependencies might work?

[codecov]

Codecov Report

Merging #1119 (19157b3) into master (c06c2a3) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1119      +/-   ##
============================================
- Coverage     84.53%   84.52%   -0.01%     
  Complexity      608      608              
============================================
  Files           134      134              
  Lines         10279    10279              
  Branches        756      756              
============================================
- Hits           8689     8688       -1     
- Misses         1214     1215       +1     
  Partials        376      376              

Impacted Files	Coverage Δ
...va/com/google/android/fhir/db/impl/DatabaseImpl.kt	88.88% <0.00%> (-1.24%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c06c2a3...19157b3. Read the comment docs.

[jingtang10]

Amazing @epicadk

[epicadk]

I think @stevenckngaa did something similar before in #1125 😅

[jingtang10]

Not sure this actually fixed it https://github.com/google/android-fhir/runs/5105727288?check_suite_focus=true

[jingtang10]

maybe it was a fluke when all the tests passed?