[Nearby] Use common default device name creation for Windows
We previously handled default device name creation for Windows differently than we did for other non-Chrome OS platforms. The underlying reason appears to be that the Nearby Share service unit tests were using base::RunLoop().RunUntilIdle() instead of task_environment_.RunUntilIdle(). Because the hardware info fetch takes longer on Windows than other platforms, I suspect that was the reason only Windows was having issues. The correct run loop behavior was fixed in a previous CL. Fixed: 1127603 Change-Id: I1f10027696fb47d30ccfe0aa7b2ceb7c85de1393 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2407856 Auto-Submit: Josh Nohle <nohle@chromium.org> Commit-Queue: James Vecore <vecore@google.com> Reviewed-by:James Vecore <vecore@google.com> Cr-Commit-Position: refs/heads/master@{#806466}
Showing
Please register or sign in to comment