March AOSP builds failing with undefined module "java_api_finder" [150626837]

Fixed

Bug

Status Update

No update yet.

Description

da...@vittegleo.com

created issue #1

Mar 3, 2020 01:14AM

Building stock AOSP with android-10.0.0_r30 branch of platform/manifest results in the following error currently:

[100% 136/136] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
FAILED: out/soong/build.ninja
out/soong/.bootstrap/bin/soong_build -t -l out/.module_paths/Android.bp.list -b out/soong -n out -d out/soong/build.ninja.d -globFile out/soong/.bootstrap/build-globs.ninja -o out/soong/build.ninja Android.bp
error: packages/modules/ExtServices/Android.bp:15:1: "ExtServices-core" depends on undefined module "java_api_finder"
ninja: build stopped: subcommand failed.
00:48:34 soong bootstrap failed with: exit status 1

It appears there was a dependency added to

https://android.googlesource.com/platform/tools/apifinder/ but it is not included anywhere.

Comments

cc...@google.com <cc...@google.com> #2Mar 3, 2020 07:16PM

Hey, sorry for coming back to this so late. We've never seen this. Without any repro steps it's going to be hard to do anything about it.

We've some cases where the Gradle daemon gets started but Studio cannot connect to it and the Studio side Gradle code handling connection to the daemon will keep spawning new ones if the connection does not get established. In this instance though the fact that the build window shows all these daemon running means that this is a different problem.

lu...@gmail.com <lu...@gmail.com> #3Mar 3, 2020 07:21PM

Hello, I had the issue reproduce on first project open after upgrading Android Studio from JetBrains Toolbox. Note that the project has a buildSrc.

I think you can reproduce it with the same steps if nothing changed since Arctic Fox alpha 08.

dw...@google.com <dw...@google.com> #4Mar 3, 2020 07:51PM

Assigned to by...@google.com.

When you upgraded from the toolbox, can you indicate which version you started from and what you upgraded to?

dw...@google.com <dw...@google.com> #5Mar 3, 2020 07:51PM

Yes, actually it's in the title of the issue: Canary 7 to 8 of Arctic Fox.

lu...@gmail.com <lu...@gmail.com> #6Mar 3, 2020 08:00PM

oops, thanks :)

by...@google.com <by...@google.com> #7Mar 3, 2020 10:40PM

Accepted by by...@google.com.

I just had that again when upgrading from AS BB Canary 2 to AS BB Canary 6. I am attaching screenshots and a screencast so you can see how it is materializing.

Note that for some reason, Gradle sync is complaining about JDK location while it was working perfectly on Canary 2 (and I only touched the AGP version), I don't know why and I don't plan to investigate that now, I'll just try to fix it and move it.

by...@google.com <by...@google.com> Mar 3, 2020 11:57PM

Marked as fixed.