RegistryProtectedTest Fail with GoogleUpdate

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Copy "official/" directory to "omaha/" directory
2. Run hammer.bat script
3.

What is the expected output? What do you see instead?
Build tests should all pass, instead I see the failures in the attached file.

This is a snippet of the failures I am seeing:
[ RUN      ] RegistryProtectedTest.CheckSystemRequirements_XmlParserNotPresent
client\install_self_unittest_no_xml_parser.cc(87): error: Value of: 
install_self::internal::CheckSystemRequirements()
  Actual: 0
Expected: ((HRESULT) (((unsigned long)(1)<<31) | ((unsigned long)(4)<<16) | 
((unsigned long)(0x704))) )
Which is: -2147219708
[  FAILED  ] RegistryProtectedTest.CheckSystemRequirements_XmlParserNotPresent 
(5 ms)

What version of the product are you using? On what operating system?
Unable to build - the VERSION file info is as follows:
version_major = 1    # 1-65535
version_minor = 3    # 0-65535
version_build = 23   # 1-65535
version_patch = 0    # 0-65535

oneclick_plugin_version = 9
update_plugin_version = 3

Windows 7, 64-bit

Please provide any additional information below.

Original issue reported on code.google.com by elysiums...@gmail.com on 29 Aug 2012 at 8:42

Attachments:

• install_self_no_xml_parser_unittest.out.txt

[GoogleCodeExporter]

The test that is failing is supposed to test that, in the case msxml is not 
available, the function CheckSystemRequirements() returns a specific error. The 
test environment tries to simulate this condition by redirecting the registry 
HKLM hive so that looking up the COM classes defined by msxml would fail. For 
some reason, in this case, the assumption break. It looks like the test has 
succeeded. It may be a bug in the code itself, which can be traced into the 
debugger, or may be that for some reason, msxml is activated somehow despite 
the registry redirection.

Original comment by so...@chromium.org on 29 Aug 2012 at 10:51

[GoogleCodeExporter]

My guess is that this unit test isn't being run from an account with 
administrative privileges (or from an elevated command prompt).  If you try to 
run it as a normal user, you won't have permission to redirect HKLM.

Original comment by ryanmyers@google.com on 30 Aug 2012 at 12:44

[GoogleCodeExporter]

Hammer was run from a command prompt as administrator

Original comment by elysiums...@gmail.com on 30 Aug 2012 at 1:12

[GoogleCodeExporter]

Thanks for the quick replies, by the way.
I believe I ran the script from a regular command prompt and another as 
administrator and obtained the same results.

Original comment by elysiums...@gmail.com on 30 Aug 2012 at 1:13

[GoogleCodeExporter]

Not sure if this is relevant, but when running run_unit_tests.py, there are a 
couple other tests that fail as well:
[ RUN      ] OmahaCustomizationGoopdateComInterfaceTest.TypeLib
C:\omaha/testing/omaha_customization_test.h(71): error: 
::LoadTypeLib(omaha_dll_path, &type_lib_) failed with error 0x80029c4a

[ RUN      ] OmahaCustomizationTest.IsInternalUser
common\omaha_customization_unittest.cc(379): error: Value of: 
ConfigManager::Instance()->IsInternalUser()
  Actual: false
Expected: true
[  FAILED  ] OmahaCustomizationTest.IsInternalUser (1 ms)

The full output is attached. There are failures from 5 different tests.

Original comment by elysiums...@gmail.com on 30 Aug 2012 at 4:00

Attachments:

• unit_test_out.txt

[GoogleCodeExporter]

Also, I do have a Registry Key at HKEY_LOCAL_MACHINE\Software\Google\UpdateDev.
It is called "TestSource" with value "ossdev." 

Note: I have also tried with the value "dev" and have also run this test by 
building a non GoogleUpdate version where the registry key was at 
HKML\Software\OmahaCompanyName\UpdateDev, and got the same results.

Again, not sure if this is entirely related to the previous case. 

Original comment by elysiums...@gmail.com on 30 Aug 2012 at 4:04

[GoogleCodeExporter]

I have the same problem.And build omaha with hammer as administrator would not 
solve this issue. using the omaha-src-r110.zip. any ideas? kindly help

Original comment by ji...@tagsys.org on 1 Aug 2013 at 3:27