configureCMakeDebug flakily crashing with null pointer exception [255788407]

Fixed

Bug

Status Update

No update yet.

Description

au...@google.com

created issue #1

Oct 26, 2022 05:46PM

DESCRIBE THE ISSUE IN DETAIL:

STEPS TO REPRODUCE:

Run builds that include cmake in androidx

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':test:integration-tests:junit-gtest-test:configureCMakeDebug[arm64-v8a]'.
Caused by: java.lang.NullPointerException
	at com.android.build.gradle.internal.cxx.configure.ConfigureInvalidationStateKt.createConfigurationInvalidationState(ConfigureInvalidationState.kt:88)
	at com.android.build.gradle.tasks.ExternalNativeJsonGenerator$configureOneAbi$1$1$invalidationState$1.invoke(ExternalNativeJsonGenerator.kt:168)
	at com.android.build.gradle.tasks.ExternalNativeJsonGenerator$configureOneAbi$1$1$invalidationState$1.invoke(ExternalNativeJsonGenerator.kt:167)
	at com.android.build.gradle.internal.cxx.timing.TimingEnvironmentKt.time(TimingEnvironment.kt:32)
	at com.android.build.gradle.tasks.ExternalNativeJsonGenerator.configureOneAbi(ExternalNativeJsonGenerator.kt:167)
	at com.android.build.gradle.tasks.ExternalNativeJsonGenerator.configure(ExternalNativeJsonGenerator.kt:103)
	at com.android.build.gradle.tasks.ExternalNativeBuildJsonTask.doTaskAction(ExternalNativeBuildJsonTask.kt:72)
	at com.android.build.gradle.internal.tasks.UnsafeOutputsTask$taskAction$$inlined$recordTaskAction$1.invoke(BaseTask.kt:65)
	at com.android.build.gradle.internal.tasks.Blocks.recordSpan(Blocks.java:51)
	at com.android.build.gradle.internal.tasks.UnsafeOutputsTask.taskAction(UnsafeOutputsTask.kt:63)
	at jdk.internal.reflect.GeneratedMethodAccessor1484.invoke(Unknown Source)

https://ci.android.com/builds/submitted/9220848/androidx_incremental/latest/view/logs/build_error.log

Studio Build: N/A Version of Gradle Plugin: 8.0.0-alpha05 Version of Gradle: 7.5 Version of Java: 17 OS: Linux

Comments

au...@google.com <au...@google.com> #2Oct 26, 2022 08:02PM

I have not seen any information about it so just asking here to avoid opening another issue. It also seems that when generating APK with alpha 8 the dex is no more compressed in the APK and stored as is. Leading to way bigger APKs.

While this is not an issue when distributing via Play Store, this could have impact for all the other distribution channels. Is this a normal wanted change and we'll have to deal with it? Or is there some new parameter to control this?

ya...@google.com <ya...@google.com> Oct 26, 2022 08:23PM

Assigned to an...@google.com.

jo...@google.com <jo...@google.com> Oct 26, 2022 09:11PM

Reassigned to jo...@google.com.

jo...@google.com <jo...@google.com> #3Nov 4, 2022 09:01PM

I can reproduce the originally reported issue of missing Baseline Profiles with AGP 8.0.0-alpha08. To verify, check out the bw/agp8 branch of the samples, create and inspect release builds.

je...@google.com <je...@google.com> #4Nov 11, 2022 07:21PM

AS for comment#2, I recommend creating a new issue.

jeff.gradle.log

67 KB

View

Download

jeff.nativeBuildStaging.zip

908 KB

Download

jo...@google.com <jo...@google.com> #5Nov 16, 2022 07:40PM

Marked as fixed.

Created https://issuetracker.google.com/issues/259832799 can't triage to proper component.

je...@google.com <je...@google.com> #6Nov 23, 2022 05:20PM

the location of the baseline profile has changed, it is now in dexopt folder instead of com.android.tools.build.profiles

please file a different bug for other issues so we can assign them correctly for each issue.