-
Notifications
You must be signed in to change notification settings - Fork 59
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
Regression with Gradle's configuration cache in 0.9.15 #338
Comments
@wilkinsona would it be possible for you to try to build and test this branch? |
That was quick. Thank you, @melix. That's better as the configuration cache no longer reports a problem. Unfortunately, the build still fails:
I don't see the failure with 0.9.14. It occurs with 0.9.15 and 0.9.16-SNAPSHOT. nbt-configuration-cache-problem.zip contains a reproducer that should fail as above. |
Thanks for the reproducer! 👀 |
It seems we're actually hitting a Gradle bug here :/ I'm trying to see if we can workaround. |
How critical is this for you? I'm afraid I'm hitting wall after wall, there seem to be bugs in Gradle I can't workaround :( Latest problem is:
Happening when the cache is deserialized. |
Thanks for trying, @melix. It's not hugely critical. We have some users who care about the configuration cache but they're definitely a minority. I've disabled the failing test that alerted me to the problem so we're not blocked. Let's revisit this when there's more time to do so. |
This isn't a showstopper by any means, but it is causing a certain amount of pain -- we've recently put some effort into fixing our build to support the configuration cache, and this is one of the few issues preventing us turning it on globally. Just realised as I was typing this that #339 hasn't been merged yet – is it worth trying with that patch, or are the Gradle problems more deep-rooted than that? |
The patch isn't enough. There are other problems arising which have no solution yet in Gradle. |
That's disappointing, but good to know, thank you. |
I took another stab at it and I think I fixed it in #339, but it will require bumping the minimal version of Gradle to 7.4 (for the plugin, independently of the config cache) and 7.5 (with the configuration cache). |
* Use serializable lambdas This is an attempt to fix #338 * Fix compatibility with the configuration cache In the process, this commit removes use of deprecated Gradle APIs and therefore bumps the minimal version of Gradle to 7.4. The configuration cache tests only pass on Gradle 7.5+, which is reasonable given that it's an experimental feature. * Disable test
Describe the bug
In some circumstances, a Gradle build fails when run using
--configuration-cache
due to aConfiguration
instance that's captured by a lambda inNativeImpagePlugin
. The same build works with 0.9.14.To Reproduce
Sorry, I've yet to manage to boil things down into a minimal reproducer. Hopefully the configuration cache problem report (see below) will be sufficient to diagnose the problem.
Expected behavior
The Gradle plugin should work with
--configuration-cache
.Logs
System Info (please complete the following information):
The text was updated successfully, but these errors were encountered: