Skip to content
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

tests(android): failure in CI #684

Open
markphelps opened this issue Feb 4, 2025 · 2 comments
Open

tests(android): failure in CI #684

markphelps opened this issue Feb 4, 2025 · 2 comments

Comments

@markphelps
Copy link
Contributor

Ever since last week the android SDK tests now fail consistently with:

io.flipt.client.TestFliptEvaluationClient > testListFlags[test(AVD) - 13] FAILED 

Tests on test(AVD) - 13 failed: There was 1 failure(s).
Test run failed to complete. Instrumentation run failed due to Process crashed.

> Task :connectedDebugAndroidTest FAILED
gradle/actions: Writing build results to /home/runner/work/_temp/.gradle-actions/build-results/__reactivecircus_android-emulator-runner-1738630954304.json

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':connectedDebugAndroidTest'.
> There were failing tests. See the report at: file:///home/runner/work/flipt-client-sdks/flipt-client-sdks/flipt-client-kotlin-android/build/reports/androidTests/connected/index.html

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

Example success: https://github.com/flipt-io/flipt-client-sdks/actions/runs/12951940855/job/36128114802
Example failure: https://github.com/flipt-io/flipt-client-sdks/actions/runs/12990936377/job/36227282622

@erka
Copy link
Collaborator

erka commented Feb 4, 2025

It started failing with #655 changes. Is it somehow related?

@markphelps
Copy link
Contributor Author

I dont think it would as the Android tests don't even run via Dagger. I wonder if GH updated some packages on the runner?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants