- 
          
- 
                Notifications
    You must be signed in to change notification settings 
- Fork 1.6k
Replies: 1 comment · 7 replies
-
| Nobody on the core team has a problem with running tests locally and I'm not aware of any contributor having issues. Please share a build scan of a build with failing tests by adding  | 
Beta Was this translation helpful? Give feedback.
All reactions
-
| Looks like the  Could you please try executing  | 
Beta Was this translation helpful? Give feedback.
All reactions
- 
              👍 1
-
| same same will try reboot. again chmod  | 
Beta Was this translation helpful? Give feedback.
All reactions
-
| I meant running  | 
Beta Was this translation helpful? Give feedback.
All reactions
-
| missing * wild card issue.  | 
Beta Was this translation helpful? Give feedback.
All reactions
-
| thanks this fixed my issue:  | 
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Following the reintroduction of Rewrite in PR #4708, this discussion explores its potential for automated code corrections beyond Spotless’s capabilities.
Key Findings
org.gradle.workers.max=2improves local reliability while retaining some speed benefits (vs. sequential execution).Potential Next Steps
equalsAvoidsNull) to validate stability.workers=2as a temporary compromise until root causes are resolved.This isn’t to push or force any—just sharing my ideas and progress. Thoughts on the incremental approach?
Thanks for the learnings so far. I hope we can continue collaborating on improving the code base thus developer experience like spotless is already doing a nifty job on this regard.
Intention is to give initiative, enabling JUnit to impose any recipe it demands.
Beta Was this translation helpful? Give feedback.
All reactions