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
Unexpected authentication token in command Build #12530
Comments
In very rare cases, the daemon registry will contain corrupted value:
|
This fixes #12530 Previously, when two daemons happen to allocate the same port, they will both exist in daemon registry file, and client might connect to the wrong one. By default, MultiChoiceAddress doesn't equal to each other even with same port. This PR removes the old entry by port.
This appears to be happening again or still on some internal builds (@pbielicki can share). Although, this doesn't appear to be a new problem (this is Gradle 4.6): https://ge.gradle.org/s/vwz7c42tmpgny/tests/:tooling-api:forkingIntegTest/org.gradle.integtests.tooling.ToolingApiClientCurrentJdkCompatibilityTest/tapi%20client%20can%20run%20build%20action%20with%20Gradle%204.6%20on%20Java%208?anchor=e30&focused-exception-line=0-38#1 |
This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution. |
This seems not happen for a long time (>1 year). |
Context
https://builds.gradle.org/viewLog.html?buildId=32563287&buildTypeId=Enterprise_Release_MainProject_Components_GradleCom_DotcomSiteTestBrowser&tab=buildLog&_focus=147#_state=147
The text was updated successfully, but these errors were encountered: