ProfileManager doesn't depend on "--login-profile" switch.
Chrome OS doesn't treat value of "login-profile" as a name
for user's profile dir anymore, however ProfileManager used its
value to let some old tests keep working. After removal
"login-profile" from ProfileManager these tests were fixed.
The significant change is that
TestingProfileManager::CreateTestingProfile treats its
|profile_name| argument as an user's id on CrOS, and creates
profile with a correct path ("u-" +
user_id_hash(profile_name)). This makes testing environment
closer to real, so communication between ProfileManager <-->
chromeos::ProfileHelper <--> chromeos::UserManager works
without additional set up in tests.
BUG=
294628
TEST=all browser_tests and unit_tests are passing
Committed:
https://crrev.com/0298d729c605a27f041da3c709e865d1ac607ecb
Cr-Commit-Position: refs/heads/master@{#291895}