Skip to content
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: Different daemons are used between IDE and CLI builds for the same project #13069

Closed
stephanenicolas opened this issue May 8, 2020 · 2 comments
Labels
a:bug a:regression This used to work
Milestone

Comments

@stephanenicolas
Copy link

Using Gradle 6.3, we can launch gradle using

  1. first ./gradlew :help
  2. second ./gradlew -Djava.net.preferIPv4Stack=true :help

And the 2 invocations of gradle will reuse the same instance of Gradle daemon.

But in 6.4, the same operations spurs the creation of 2 different instances of daemons.

This has a direct impact on Android Studio that uses this flag. It means we cannot reuse the same instance of the daemon from CLI Gradle invocations and Android Studio syncs & builds.

@stephanenicolas
Copy link
Author

This is linked to #12582

@big-guy big-guy added the a:regression This used to work label May 12, 2020
@big-guy big-guy added this to the 6.4.1 milestone May 13, 2020
@big-guy
Copy link
Member

big-guy commented May 14, 2020

@stephanenicolas could you give this nightly a try? ./gradlew wrapper --gradle-version=6.4.1-20200514173331+0000

@big-guy big-guy closed this as completed May 15, 2020
@big-guy big-guy changed the title Regression in Gradle 6.4: New system property spurs a new daemon. Regression: Different daemons are used between IDE and CLI builds for the same project May 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:bug a:regression This used to work
Projects
None yet
Development

No branches or pull requests

3 participants