Commit b46f1686 authored by Rob Shearman's avatar Rob Shearman Committed by Alexandre Julliard

rpcrt4: Don't test for a specific value for fBufferValid in test_client_init.

It's not consistent across different Windows versions.
parent 0025bdf6
......@@ -1196,7 +1196,7 @@ static void test_client_init(void)
stubMsg.fIsOut == -1, /* XP-SP3 */
"fIsOut should have been set to 0 or -1 instead of %d\n", stubMsg.fIsOut);
TEST_ZERO(fIsOicf, "%d");
TEST_ZERO(fBufferValid, "%d");
trace("NdrClientInitializeNew: fBufferValid = %d\n", stubMsg.fBufferValid);
ok(stubMsg.fHasMemoryValidateCallback == 0 ||
stubMsg.fHasMemoryValidateCallback == -1, /* XP-SP3 */
"fHasMemoryValidateCallback should have been set to 0 or -1 instead of %d\n", stubMsg.fHasMemoryValidateCallback);
......@@ -1313,7 +1313,7 @@ todo_wine
stubMsg.fIsOut == -1, /* XP-SP3 */
"fIsOut should have been set to 0 or -1 instead of %d\n", stubMsg.fIsOut);
TEST_ZERO(fIsOicf, "%d");
trace("fBufferValid = %d\n", stubMsg.fBufferValid);
trace("NdrServerInitializeNew: fBufferValid = %d\n", stubMsg.fBufferValid);
ok(stubMsg.fHasMemoryValidateCallback == 0 ||
stubMsg.fHasMemoryValidateCallback == -1, /* XP-SP3 */
"fHasMemoryValidateCallback should have been set to 0 or -1 instead of %d\n", stubMsg.fHasMemoryValidateCallback);
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment