[advapi32/tests #2] Don't set last error to 0 so we can check if it has changed

[Alexandre Julliard]

Paul Vriens <paul.vriens.wine at gmail.com> writes:

> We test for a last error of 0, so we shouldn't set it to 0 before the
> function is called. This however introduces a todo_wine.

Is there any reason to believe that last error should be 0 on success?
This looks more like a broken test to me.

-- 
Alexandre Julliard
julliard at winehq.org