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

[Alexandre Julliard]

Module: wine
Branch: master
Commit: b46f1686505c26145ab5f81df432cc83fefee862
URL:    http://source.winehq.org/git/wine.git/?a=commit;h=b46f1686505c26145ab5f81df4...

Author: Rob Shearman 
Date:   Wed Jan 28 12:48:58 2009 +0000

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

It's not consistent across different Windows versions.

---

dlls/rpcrt4/tests/ndr_marshall.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/dlls/rpcrt4/tests/ndr_marshall.c b/dlls/rpcrt4/tests/ndr_marshall.c
index 83a80d9..5356c43 100644
--- a/dlls/rpcrt4/tests/ndr_marshall.c
+++ b/dlls/rpcrt4/tests/ndr_marshall.c
@@ -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);