-
Notifications
You must be signed in to change notification settings - Fork 288
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
Integration test out of memory for API 29 #73
Comments
This might be fixed by #74. Will close if the next few actions succeed. |
Still seeing OOM failures on some branches. |
A more recent run: https://github.com/google/android-fhir/runs/2054399134?check_suite_focus=true This blocked code submission over the weekend. We should treat this as high-priority. |
Related issue: ReactiveCircus/android-emulator-runner#131 |
This has not been happening - let's close for now and reopen if recurs. |
looks like 29 has memory issues google/android-fhir#73
* Add github-specific setup Change-Id: Iad8edf3c16182807eda6893c696244d9147f7cab * Update Build.yaml Replaces cC for cAT * Filters out benchmark tests * Trying to increase storage with disk.dataPartition.size * Increasing size a bit more for API 23 * Remove API 23 * Reverting, using correct param name * Increase again to 1500M * heap=512M java.lang.OutOfMemoryError: java.lang.OutOfMemoryError: OutOfMemoryError thrown while trying to throw an exception; no stack trace available * replace 29 for 31 looks like 29 has memory issues google/android-fhir#73 * API 30 * Arch x86_64 as there's no API 30 x86 Co-authored-by: Jose Alcérreca <JoseAlcerreca@users.noreply.github.com>
In recent github action runs for PRs, tests for API 29 consistently failed due to out of memory issue. e.g:
com.google.fhirengine.db.impl.DatabaseImplTest > select_invalidResourceType_shouldThrowIllegalArgumentException[test(AVD) - 10] FAILED
java.lang.OutOfMemoryError: OutOfMemoryError thrown while trying to throw an exception; no stack trace available
See trace: https://github.com/google/android-fhir/runs/824594488
Note this doesn't happen for API 24 or 27, nor does this happen locally.
The text was updated successfully, but these errors were encountered: