-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
configuration cache with included build causes --profile unable to create directory #18386
Comments
Also interesting, if I run |
It seems that in this situation, Gradle is trying to put the reports into |
Also adding an exemption for it being in the source dir Also informing `./gradlew --clean` where to find it Bug: 180423646 Bug: gradle/gradle#18386 Test: enable configuration caching and run `./busytown/androidx.sh` and see that it no longer fails to create the report directory Change-Id: Id32c350c3bcb1328669a3c04c2a2d110930627f0
I'm seeing this same problem in another script where i run the profile multiple times. I think the real issue in my case is the date
|
FWIW, in the IntelliJ debugger, I see that the canonical path for 'reports/profile' resolves to '~/.gradle/daemon/7.4.2/reports/profile' and the mkdirs() call below fails with the exception.
|
same question |
Same here |
same question +1 |
Hi, same here. Any ideas? |
Still same issue today using gradle 8.3 |
Likewise with Gradle 8.6 |
Expected Behavior
If I run a build that uses an included build, has configuration caching enabled, and uses the --profile argument, I'd like the process of generating the profile report to succeed.
Current Behavior
Currently if I do the above, I observe that Gradle says it cannot create the report directory:
Context
This makes it slightly more difficult to enable configuration caching in androidx ( https://android.googlesource.com/platform/frameworks/support/ )
Steps to Reproduce
See https://github.com/mathjeff/gradle-samples/tree/master/included-build-configuration-cache-profile
Your Environment
Build scan URL: https://scans.gradle.com/s/22l2n2jlpv5ac
Note that the failure is in generating the profile report file, which happens after publishing the build scan, and so the build scan might not mention the failure to create the profile report file
The text was updated successfully, but these errors were encountered: