Unit Test Gradle Failed #4988
Unanswered
XichengSpencer
asked this question in
Q&A (Other)
Replies: 2 comments 1 reply
-
|
Hi @XichengSpencer, sometimes the CI run times out, and will need to be restarted manually, like in this instance. Here is the link to the Wiki on how to intepret the CI results: https://github.com/oppia/oppia-android/wiki/Interpreting-CI-Results |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thanks, I didn't find any option to rerun the CI on the GitHub site. Should I wait for the reviewer to do that? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
My code run successfully on my Android Studio, but when I submit pr and the only test failed is

Try:
Run with --info or --debug option to get more log output. Run with --scan to get full insights.
Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':app:testDebugUnitTest'.
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$3(ExecuteActionsTaskExecuter.java:186)
...
BUILD FAILED in 13m 40s
Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.8/userguide/command_line_interface.html#sec:command_line_warnings
Is it pure gradle file problem, and what can I do with it?
Beta Was this translation helpful? Give feedback.
All reactions