On Mon, May 13, 2013 at 12:58 PM, Sergey Cheban wrote:

On 12.05.2013 17:25, Andrey Semashev wrote:

2. There are a few testers that fail the util_dynamic_type_dispatcher and

...

util_static_type_dispatcher tests, namely Qt5 jc-bell.com, teeks99-01a- win7-32on64 and DrWeb_x86. The test report says this is a runtime failure but it has no output or just has an exit status. The same tests run successfully for other testers, as well as in my local runs.

The problem is related to the fact that MS Windows (at least, Windows Server 2012) requires elevation for the execulables with names that match the *patch*.exe mask. So, util_dynamic_type_disPATCHer and util_static_type_disPATCHer require elevation.

lol, what a wonderful and obvious security policy on MS part, isn't it? :)

I think that the easiest way to work around this problem is to rename the tests. Or, you may put the manifest into the executables to explicitly specify that they don't require elevation.

Thanks a lot, Sergey. I renamed the tests.

On Mon, May 13, 2013 at 1:23 PM, Andrey Semashev wrote:

On Mon, May 13, 2013 at 12:58 PM, Sergey Cheban wrote:

...

I think that the easiest way to work around this problem is to rename the tests. Or, you may put the manifest into the executables to explicitly specify that they don't require elevation.

Thanks a lot, Sergey. I renamed the tests.

The renamed tests passed for teeks99-01a-win7-32on64, so the workaround helped. However, the old-named tests are still present in the table. I assume this is because the tester runs incremental builds, so the old test results are not deleted. Is there a way to request to clear the cached results?