Nightly builds with baseline profiles

[keyboardsurfer]

Change-Id: I162cd9eca724c30d839add912359482cbce7c68e

Thanks for submitting a pull request. Please include the following information.

What I have done and why
Enabled baseline profile generation for new nightly build type.
With KVM, GMD run smoothly and BP generation is not negatively affected any longer.
Enabling nightly builds for this keeps PR builds fast while allowing for baseline profiles to be generated regularly as well.

Enabled Startup Profiles for smaller classes.dex and faster app startup

Fixes #<issue_number_goes_here>

Do tests pass?

• Run local tests on DemoDebug variant: ./gradlew testDemoDebug
• Check formatting: ./gradlew --init-script gradle/init.gradle.kts spotlessApply

[keyboardsurfer]

RFR. @JoseAlcerreca & @dturner PTAL.

[mlykotom]

I'm generally ok with this, but it would be nice if Don/Jose took a look as they maintain the project.

[JoseAlcerreca]

I started the review assuming this nightly was only for BP generation and only realized you were creating a full nightly. I think the main build should be our SOT for status, so just make this one about BP.

[github-actions]

Combined test coverage report

Overall Project	40.4%	🍏

There is no coverage information present for the Files changed

[github-actions]

Combined test coverage report

Overall Project	40.4%	🍏

There is no coverage information present for the Files changed

[github-actions]

Combined test coverage report

Overall Project	40.4%	🍏

There is no coverage information present for the Files changed

[keyboardsurfer]

@JoseAlcerreca could this be a flaky test?

com.google.samples.apps.nowinandroid.ui.SnackbarScreenshotTests > snackbarShown_tablet FAILED
    java.lang.AssertionError at SnackbarScreenshotTests.kt:236

If so, could you show me how to fix it or approve the PR so it can be merged?

[JoseAlcerreca]

Let's merge #1395 first and make sure this one passes

[keyboardsurfer]

SGTM

[github-actions]

Combined test coverage report

Overall Project	40.37%	🍏

There is no coverage information present for the Files changed

[github-actions]

Combined test coverage report

Overall Project	40.4%	🍏

There is no coverage information present for the Files changed

[github-actions]

Combined test coverage report

Overall Project	40.4%	🍏

There is no coverage information present for the Files changed

[github-actions]

Combined test coverage report

Overall Project	40.4%	🍏

There is no coverage information present for the Files changed

[github-actions]

Combined test coverage report

Overall Project	40.4%	🍏

There is no coverage information present for the Files changed

[github-actions]

Combined test coverage report

Overall Project	42.34%	🍏

There is no coverage information present for the Files changed

Outdated

[github-actions]

Combined test coverage report

Overall Project	42.34%	🍏

There is no coverage information present for the Files changed

[github-actions]

Combined test coverage report

Overall Project	42.32%	🍏

There is no coverage information present for the Files changed

[github-actions]

Combined test coverage report

Overall Project	42.32%	🍏

There is no coverage information present for the Files changed

[github-actions]

Combined test coverage report

Overall Project	42.29%	🍏

There is no coverage information present for the Files changed

[github-actions]

Combined test coverage report

Overall Project	42.42%	🍏

There is no coverage information present for the Files changed

[github-actions]

Combined test coverage report

Overall Project	42.43%	🍏

There is no coverage information present for the Files changed

[github-actions]

Combined test coverage report

Overall Project	42.33%	🍏

There is no coverage information present for the Files changed

[lihenggui]

It seems that not enabling the KVM before setting up GMD causes this problem.

https://github.com/android/nowinandroid/actions/runs/10953338005/job/30413441493

* What went wrong:
Execution failed for task ':benchmarks:pixel6Api33Setup'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.ManagedDeviceInstrumentationTestSetupTask$ManagedDeviceSetupRunnable
   > com.android.build.gradle.internal.AvdSnapshotHandler$EmulatorSnapshotCannotCreatedException: Gradle was not able to complete device setup for: dev33_default_x86_64_Pixel_6
     The emulator failed to open the managed device to generate the snapshot.
     This is because the emulator closed unexpectedly (1),
     try updating the emulator and ensure a device can be run from Android Studio.

[keyboardsurfer]

@lihenggui the issue was caused by GMD requiring a lot more processing power than what the GitHub runners offer in the free tier. So the relevant step is this one

- name: Setup GMD
        run: ./gradlew :benchmarks:pixel6Api33Setup
          --info
          -Pandroid.experimental.testOptions.managedDevices.emulator.showKernelLogging=true
          -Pandroid.testoptions.manageddevices.emulator.gpu="swiftshader_indirect"

Which has to be executed before the entire build is kicked off.