Sporadic IllegalStateException while initializing build #2239
Comments
eriwen
changed the title
eriwen
changed the title
|
Step for reproduction:
|
|
Using the steps given by @gastonlagaf I can reproduce this problem as well |
|
There are two issues here:
Fix for (1): #2331 @eskatos can you check what we could do about (2)? Is reverting (at least for a 4.0.1 release) an option? |
|
Looks like we have an issue with supporting two setters for the same property with different types (see #1866). We need to fix this: At the moment depends on the order in which methods are iterated if we grep the right one. That explains why it is difficult to reproduce. Here is a test that fails sometimes, but not always: |
jjohannes
added a commit
that referenced
this issue
Jun 20, 2017
|
A possible fix: #2332 |
|
First issue fixed and merged. Follow up for second issue: #2385 |
|
I'm running into this, or something similar to this with gradle 4.0.1. It's an IllegalStateException in a gradle execution involving a GradleBuild task in a plugin. It happens during spock tests that invoke gradle with a GradleRunner, when gradle itself and the GradleRunner both use a daemon, as well as when neither do (by invoking gradlew with --no-daemon, and using withDebug(true) in the spock test). A couple of notes:
Here's a stack trace using a daemon: Here's a stack trace with no daemon: Thanks for your help. |
|
@dbyron0 thanks for reporting this. Unfortunately I am not sure how to reproduce this. Can you share a complete reproducible example that includes the build script(s)? |
|
@jjohannes Is there a good way to share it not quite so publicly? Email perhaps? |
|
@dbyron0 we have used shared Google Drive or Dropbox links in the past for this. You're welcome to also email me eric at gradle dot com if you'd prefer. |
|
Great. I'm getting something together. Thanks. |
|
@dbyron0 I was able to reproduce and debug the issue now. Thanks for your input. It looks like some We probably introduced this in Good news is that the issue was already fixed with 45d311d, which is in 4.1 RC1. Can you confirm that your project works as expected with 4.1 RC1? |
|
@dbyron0 Looking at the stacktrace you posted again... I actually did not reproduce that exactly. If 4.1 RC1 still fails for you, can you confirm that you get the same issue or send a new trace. Thanks. |
|
Yup, still fails with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
Build initialization should complete successfully when configured properly
Current Behavior
Some projects encounter this frequently:
Context
Discussion at https://discuss.gradle.org/t/gradle-4-unexpected-initialization-error/22851
Stacktrace
java.lang.IllegalStateException: This operation (org.gradle.internal.progress.BuildProgressLogger - Initializing build) has already been completed. at org.gradle.internal.logging.progress.DefaultProgressLoggerFactory$ProgressLoggerImpl.assertRunning(DefaultProgressLoggerFactory.java:183) at org.gradle.internal.logging.progress.DefaultProgressLoggerFactory$ProgressLoggerImpl.completed(DefaultProgressLoggerFactory.java:159) at org.gradle.internal.progress.BuildProgressLogger.beforeComplete(BuildProgressLogger.java:87) at org.gradle.internal.progress.BuildProgressFilter.beforeComplete(BuildProgressFilter.java:107)Steps to Reproduce (for bugs)
Seems to occur sometimes when invoking
gradle --stopas well.Your Environment
The text was updated successfully, but these errors were encountered: