rpcrt4/tests: Win 8 and 10 do not correctly unmarshal a ranged enum16.

[Huw Davies]

In practice this bug is not observed since midl, unlike widl, does not
generate ranges in inline stub mode.  For interpreted stubs, where
midl does generate ranges, the [out] parameters are zero-initialised
by the runtime.

Signed-off-by: Huw Davies <huw at codeweavers.com>
---
 dlls/rpcrt4/tests/server.c | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/dlls/rpcrt4/tests/server.c b/dlls/rpcrt4/tests/server.c
index 6901f6b..f9a5a96 100644
--- a/dlls/rpcrt4/tests/server.c
+++ b/dlls/rpcrt4/tests/server.c
@@ -1006,8 +1006,11 @@ basic_tests(void)
 
   if (!old_windows_version)
   {
+      re = 0xdeadbeef;
       get_ranged_enum(&re);
-      ok(re == RE3, "get_ranged_enum() returned %d instead of RE3\n", re);
+      ok(re == RE3 ||
+         broken(re == MAKELONG(re, 0xdead)), /* Win 8, Win 10 */
+         "get_ranged_enum() returned %x instead of RE3\n", re);
   }
 }
 
-- 
2.8.2