-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
"Unable to make progress running work" redux #21325
Comments
Do you have a few more details on how to do this? Do we have access to your source code? Which tasks does the Jenkins pipeline run? etc. |
The tasks are listed above in the error messages. You don't have access to the source code, and I can't provide you with a cut-down reproducible test case. But I assure you, it happens. There's no reason to make something like this up. You'll probably get other reports. |
It will be very difficult to fix this without a reproducer. Any details you can give us would be very helpful. Would you be willing to try out a nightly with some additional diagnostics added? This will give us some clues to help us reproduce (and fix) the problem. |
@jimshowalter could you give You can upgrade via: |
Unfortunately we see the same error with 7.5.1-20220729132837+0000. |
I am having the same problem. Console output on Gradle 7.5: https://ci.plex.us.org/job/Plex/job/master/314/console Rolling back to 7.4.2 fixed it |
@jimshowalter @Telesphoreo could you give If this doesn't fix it, could you provide the "Queued nodes" output again for this version? it has some more diagnostics. |
Unfortunately still not working for me
Edit: After a long time debugging and commenting lines of code out, I found out where it's getting hung up. Commenting this line out will make it publish successfully: https://github.com/plexusorg/Plex/blob/517b8294207cd292ee22f644ef197bf84e3f4a6f/server/build.gradle#L106 |
We get the same error with the latest snapshot. We don't use shadow. |
Moving this out of Gradle 7.5.1, as we have other fixes for the patch release that we want published and are unable to provide a fix here for now. Those affected will have to stay with Gradle 7.4.2 for now. |
Should be fixed via #21643 |
When will this fix be released? |
I upgraded to |
I mean released formally, in https://gradle.org/releases/. |
@jimshowalter the fix will be included in Gradle 7.6, which is due to be released soon. @Telesphoreo thanks for trying out the fix and letting us know the result. |
I'm getting this same error in a teamcity pipeline run by gradle 7.6.
made it less frequent, but I dunno neither how to get rid of it entirely nor how to reproduce it well. UPD: downgrade to gradle 7.4.2 didn't help either |
So I think I'm seeing this error when using Android Studio Hedgehog Canary 11. My gradle wrapper is set to 8.1.1. Even if I change gradle to 7.6 then it still doesn't work in AS canary 11. If I use AS Giraffe, then I can use gradle 8.1.1. |
Same issue for me with Android Studio Hedgehog Canary 11. |
Same issue for me with Android Studio Hedgehog Canary 12. |
An issue was created on Google IssueTracker but the status changed to Won't fix (Infeasible) yesterday...
|
Same issue for me with Android Studio Hedgehog Canary 13. |
Can confirm this is indeed a problem also in Android Studio Hedgehog Canary 14. |
We're experiencing similar issue with same warning when rebuilding our project in Android Studio Hedgehog | 2023.1.1 Canary 13. Strange thing is that running on mobile device works, but only rebuild option fails. |
Hey folks, What you observe is a different issue than the one confirmed fixed here. Please open another issue and provide as much detail as you can. We don't have a reproducer yet that demonstrates what you observe and without a reproducer this is very difficult to track down. |
Android Studio Hedgehog Canary 16 也这13样 |
@javakam 大佬也遇到这问题了么 我还在用你的 |
客气了兄弟, 我也是捣鼓了半天
稳定, 这个是前半年的配置一直很稳定。 |
我换回 |
Same problem with Android Studio Preview (Iguana Canary 3) |
We are seeing this problem in Gradle 7.6.2 |
might be related. The wierd thing is when I switch to Android studio stable version (here) the project works fine without problem. Your Environment
|
I am using Android studio Iguana RC2 and I see this issue. Any potential changes that would make 'Rebuild' work? I have the same issue as described by @sebastienrussell |
Seeing this on AS Iguana stable version. |
I started to see this after upgrading to Iguana as well, but managed to work around it. This issue appears to manifest in more than one way, but I think the root cause is the addition of "testClasses" target to modules where it previously wasn't. |
I left comment 19 on that google issue. I was getting errors saying "Cannot locate tasks that match as task ':moduleA:testClasses'" for a couple of modules. I found a SO saying a work around to this was to add |
same
|
+1 same. Android Studio Iguana | 2023.2.1 Patch 2 |
same error: happens only with checked on:
|
You closed #21125 as fixed, but the same problem is in 7.5.
Expected Behavior
The build should complete normally.
Current Behavior
`Unable to make progress running work. The following items are queued for execution but none of them can be started:
Context
It prevents all work from proceeding, so we had to roll back to 7.4.2.
Steps to Reproduce
Upgrade to 7.5 and then try to run our Jenkins pipeline.
Your Environment
Linux, Jenkins, Gradle 7.5, Java 17.
The text was updated successfully, but these errors were encountered: