Fix to show PR coverage report

[blue928sky]

What I have done and why

Currently the action to show coverage does not seem to be working.
#1803

Changed the target API to display from 30 to 34.

It looks like API 30 is still turned off in the PR here.
#1724

[blue928sky]

Hmm.
I don't know why it's stuck here.

> Task :core:designsystem:testDemoDebugUnitTest

Of course, locally, ./gradlew :core:designsystem:testDemoDebugUnitTest and ./gradlew :core:designsystem:testDemoDebugUnitTest have been successful 😓

./gradlew testDemoDebugUnitTest -Proborazzi.test.verify=false

Starting a Gradle Daemon, 1 stopped Daemon could not be reused, use --status for details
Parallel Configuration Cache is an incubating feature.
Calculating task graph as no cached configuration is available for tasks: testDemoDebugUnitTest
Type-safe project accessors is an incubating feature.

> Task :core:model:compileKotlin
w: Opt-in requirement marker kotlinx.coroutines.ExperimentalCoroutinesApi is unresolved. Please make sure it's present in the module dependencies

> Task :core:datastore-proto:compileDemoDebugKotlin
w: Opt-in requirement marker kotlinx.coroutines.ExperimentalCoroutinesApi is unresolved. Please make sure it's present in the module dependencies

[Incubating] Problems report is available at: file:///Users/blue928sky/Study/nowinandroid/build/reports/problems/problems-report.html

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.12/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

BUILD SUCCESSFUL in 7m 5s

[Jaehwa-Noh]

It is as though need to be re-run CI.

[blue928sky]

I did an empty commit and re-run, but it failed as before 🤔

[anhtuannd]

The error

The hosted runner: GitHub Actions 222 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

Could come from resource limitation problem.

Also, now there is some problems with ubuntu-latest as they are migrating it to ubuntu-24.04, can you retry with ubuntu-22.04 or ubuntu-20.04 instead?

[anhtuannd]

Also, could be related to #1738

[blue928sky]

AAPT2 aapt2-8.7.3-12006047-linux Daemon #0 Failed to shutdown within timeout
java.util.concurrent.TimeoutException: AAPT2 aapt2-8.7.3-12006047-linux Daemon #0: Failed to shut down within 30 seconds. Forcing shutdown
	at com.android.builder.internal.aapt.v2.Aapt2DaemonImpl.stopProcess(Aapt2DaemonImpl.kt:249)
	at com.android.builder.internal.aapt.v2.Aapt2Daemon.shutDown(Aapt2Daemon.kt:171)
	at com.android.builder.internal.aapt.v2.Aapt2DaemonManager$LeasableAaptDaemon.shutdown(Aapt2DaemonManager.kt:66)
	at com.android.builder.internal.aapt.v2.Aapt2DaemonManager.maintain(Aapt2DaemonManager.kt:89)
	at com.android.build.gradle.internal.services.Aapt2DaemonManagerMaintainer$firstDaemonStarted$1.run(Aapt2DaemonBuildService.kt:239)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
	at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:840)

https://github.com/android/nowinandroid/actions/runs/12885712069/job/35924748312#step:9:685