diff options
| author | sukolsak@chromium.org <sukolsak@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-09-17 21:40:48 +0000 |
|---|---|---|
| committer | sukolsak@chromium.org <sukolsak@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-09-17 21:40:48 +0000 |
| commit | 7a4d58a41fd045da4d0945e1eadcdb5168d19f84 (patch) | |
| tree | 7c342d66fe510bdcaa8cb098d9efde9f6ecc6cce /media/video | |
| parent | ee9cda5acc731ec1398e964f627e850432ff9ef7 (diff) | |
| download | chromium_src-7a4d58a41fd045da4d0945e1eadcdb5168d19f84.zip chromium_src-7a4d58a41fd045da4d0945e1eadcdb5168d19f84.tar.gz chromium_src-7a4d58a41fd045da4d0945e1eadcdb5168d19f84.tar.bz2 | |
Update a property file in the mini_installer test framework to work around a bug in the installer.
There is a bug in the installer that leaves HKEY_CURRENT_USER\Software\Chromium\BrowserCrashDumpAttempts in the registry when installing/running Chromium at system level (see http://crbug.com/293660). Remove the check for HKEY_CURRENT_USER\Software\Chromium and check that HKEY_CURRENT_USER\Software\Chromium\Commands doesn't exist instead. (Ideally, we should also check that the value 'pv' of HKEY_CURRENT_USER\Software\Chromium doesn't exist. But the current property file format doesn't allow that.) This CL is a temporary workaround to get the mini_installer_tests bot in master.chromium.fyi green as soon as possible.
NOTRY=True
BUG=293660
TEST=
1) Build Chromium in Release mode and make sure that mini_installer.exe is created.
2) Go to src\chrome\test\mini_installer
3) Run "python test_installer.py config\config.config --build-dir=<build-dir> --target=Release" where <build-dir> is the path to main build directory (the parent of the Release directory). The test should pass.
Review URL: https://chromiumcodereview.appspot.com/23496064
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@223701 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'media/video')
0 files changed, 0 insertions, 0 deletions