Status Update
No update yet.
Comments
ki...@google.com
Hey, sorry for coming back to this so late. We've never seen this. Without any repro steps it's going to be hard to do anything about it.
We've some cases where the Gradle daemon gets started but Studio cannot connect to it and the Studio side Gradle code handling connection to the daemon will keep spawning new ones if the connection does not get established. In this instance though the fact that the build window shows all these daemon running means that this is a different problem.
ak...@google.com
Hello, I had the issue reproduce on first project open after upgrading Android Studio from JetBrains Toolbox. Note that the project has a buildSrc.
I think you can reproduce it with the same steps if nothing changed since Arctic Fox alpha 08.
za...@google.com
When you upgraded from the toolbox, can you indicate which version you started from and what you upgraded to?
Description
The network_WiFi_DisconnectReason test only looks at error reasons returned from supplicant. Since the test code simply goes through net.log anyways, it makes sense to also keep track of the failure reasons returned by shill, especially as we try to improve the quality of the failure reasons shill provides to users.