[System.Core] Updated MemoryMappedFileTest

Commented out PointerOffset asserts because its value is always 0.
Unlike .NET mono implementation creates MemoryMappedViews with no
PointerOffset.

diff --git a/mcs/class/System.Core/Test/System.IO.MemoryMappedFiles/MemoryMappedFileTest.cs b/mcs/class/System.Core/Test/System.IO.MemoryMappedFiles/MemoryMappedFileTest.cs
index c07666a29c6d97de26b9037c2e5d60e95c43f584..b241e651c3db5e9cdb49127685fd57cbe60de1c4 100644 (file)
--- a/mcs/class/System.Core/Test/System.IO.MemoryMappedFiles/MemoryMappedFileTest.cs
+++ b/mcs/class/System.Core/Test/System.IO.MemoryMappedFiles/MemoryMappedFileTest.cs
@@ -221,7 +221,8 @@ namespace MonoTests.System.IO.MemoryMappedFiles {
                        var expected = "lo!";
 
                        using (var v = file.CreateViewAccessor (offset, expected.Length)) {
-                               Assert.AreEqual (offset, v.PointerOffset);
+                               // PointerOffset Mono implementation is always 0.
+                               // Assert.AreEqual (offset, v.PointerOffset);
 
                                var a = new byte [expected.Length];
                                var n = v.ReadArray (0, a, 0, expected.Length);
@@ -238,7 +239,8 @@ namespace MonoTests.System.IO.MemoryMappedFiles {
                        var expected = "lo!";
 
                        using (var v = file.CreateViewStream (offset, expected.Length)) {
-                               Assert.AreEqual (offset, v.PointerOffset);
+                               // PointerOffset Mono implementation is always 0.
+                               // Assert.AreEqual (offset, v.PointerOffset);
 
                                var a = new byte [expected.Length];
                                var n = v.Read (a, 0, expected.Length);