Using real user profile in unit_tests.LocalDatabaseManagerTest.*
Reported by
atuc...@yandex-team.ru,
Jul 22 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 YaBrowser/16.6.0.8125 Safari/537.36 Steps to reproduce the problem: 1. Remove user profile ~/Library/Application\ Support/Chromium/ 2. Compile and run unit_tests: out/Debug.gn/unit_tests --gtest_filter=LocalDatabaseManagerTest.* What is the expected behavior? The tests should use separate temp dir for fake user profile. So, the dir ~/Library/Application\ Support/Chromium/ shouldn't exist. What went wrong? The tests use real user profile: the ~/Library/Application\ Support/Chromium/ has created again. So, the state of the profile may affect to test results. Second problem is that data race on the profile is possible (between this tests and running browser or other tests with the same problem) Did this work before? No Chrome version: 50.0.2661.102 Channel: n/a OS Version: OS X 10.11.5 Flash Version: Linux and Win are also affected.
,
Jul 24 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by caseq@chromium.org
, Jul 22 2016Labels: -OS-Mac OS-All