-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Encountered error after upgrading from 1.6.10-beta01 to 1.6.10-rc01 #4815
Comments
Do you have a reproducer for this issue? There is a template when you create a new issue. Please follow it. Especially the "Steps to reproduce" part |
@eymar It cannot be reproduced stably, but it will break my CI from time to time after upgrading. https://scans.gradle.com/s/43zyx7dja22yc |
Probably it is #4773. The solution is in the comments |
Not sure what's going on. |
for me it seems when I add compose plugin using it breaks CI .. because for the first time this happenes but after that its ok steps to reproduce ... cd projectDir
./gradlew clean
rm -rf .gradle
rm -rf buildSrc/.gradle
rm -rf buildSrc/build
./gradlew --stop
./gradlew the problem happens here |
I'm having the same problem since updating to Kotlin 2.0.0. I'm also using the Gradle plugins within convention plugins. Here's a failed build. This workaround didn't work for me. Also, this always fails on CI but just occasionally on my local machine. |
https://scans.gradle.com/s/hkyvpfi4jbpgs |
This doesn't work at all. Getting tired, let it fail all the time https://github.com/OmicoDev/wwm/actions/runs/9409655695. |
We had two build services: 1) to check unsupported compose compiler plugins were applied 2) to check a native cache kind configuration Both of them are outdated and we may get rid of them. Fixes #4815 ## Release Notes ### Fixes - Gradle Plugin - Delete outdated build services
It seems the fix was too late for |
1.7.0 |
Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks. |
The text was updated successfully, but these errors were encountered: