Paul Vriens <[EMAIL PROTECTED]> writes:
> is it OK that have the above in a patch anyway, along with some extra
> debugging output? I will try and find a key we can use, but one problem
> could be that the failures are related to security (that's why I want to
> have the extra output as well).
We
On Mon, 2005-01-17 at 13:24, Alexandre Julliard wrote:
> Paul Vriens <[EMAIL PROTECTED]> writes:
>
> > If the first CreateKey fails, there is no need to continue with the
> > testing (because the rest of the tests will fail as well). What's the
> > best way to stop there?, something like this?:
>
Paul Vriens <[EMAIL PROTECTED]> writes:
> If the first CreateKey fails, there is no need to continue with the
> testing (because the rest of the tests will fail as well). What's the
> best way to stop there?, something like this?:
>
> START_TEST(shreg)
> {
> HKEY hkey = create_test_entrie
Paul Vriens <[EMAIL PROTECTED]> writes:
> If the first CreateKey fails, there is no need to continue with the
> testing (because the rest of the tests will fail as well). What's the
> best way to stop there?, something like this?:
>
> START_TEST(shreg)
> {
> HKEY hkey = create_test_entries
Hi,
I'm currently looking into the shreg test of shlwapi. In the error-logs
on test.winehq.org I see a lot of errors.
If the first CreateKey fails, there is no need to continue with the
testing (because the rest of the tests will fail as well). What's the
best way to stop there?, something like t
