ReceiveTempSMS
/
Sweden-Number
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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

It's not consistent across different Windows versions.
This commit is contained in:
Rob Shearman 2009-01-28 12:48:58 +00:00 committed by Alexandre Julliard
parent 0025bdf607
commit b46f168650
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
dlls/rpcrt4/tests/ndr_marshall.c
View File

@ -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);