[Mono-bugs] [Bug 74702][Min] New - Unit Test: Sys.Runtime.Remoting - small nit

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Sat, 23 Apr 2005 10:14:55 -0400 (EDT)


Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by flashdict@gmail.com.

http://bugzilla.ximian.com/show_bug.cgi?id=74702

--- shadow/74702	2005-04-23 10:14:55.000000000 -0400
+++ shadow/74702.tmp.9628	2005-04-23 10:14:55.000000000 -0400
@@ -0,0 +1,64 @@
+Bug#: 74702
+Product: Mono: Class Libraries
+Version: unspecified
+OS: other
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Minor
+Component: System
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: flashdict@gmail.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Unit Test: Sys.Runtime.Remoting - small nit
+
+Description of Problem:
+
+A context test in System.Runtime.Remoting was failing for me with errors of
+the following form:
+
+
+NUnit.Framework.AssertionException: [TestNewContext] Call check failed in
+step 16. Expected "015 (d1,c1) List created" found "015 (d1,c1)
+IContributeEnvoySink(1.d1).GetEnvoySink"
+in <0x0004e> NUnit.Framework.Assert:Fail (System.String message,
+System.Object[] args)
+in <0x0000c> NUnit.Framework.Assert:Fail (System.String message)
+in <0x002a8> MonoTests.Remoting.CallSeq:Check (System.String msg, Int32 domain)
+in <0x00040> MonoTests.Remoting.CallSeq:Check (System.String[] msgs, Int32
+domain)
+in <0x00144> MonoTests.Remoting.ContextsTest:TestNewContext ()
+RR:MonoTests.System.Runtime.Remoting.RemotingServicesInternal.MarshalObject.Method1
+()
+RR:MonoTests.System.Runtime.Remoting.RemotingServicesInternal.MarshalObject.Method2
+()
+
+The following patch, which simply changes the expected return values,
+avoids the problem and allows the test to complete.  I don't know if this
+is truly the problem, or if perhaps there is a deeper reason why the
+expectation does not match the found value, but with this "fix" and the
+other one I reported with corlib (74698), I can now run an end-to-end unit
+test against FreeBSD.  :)
+
+Index: ContextsTest.cs
+===================================================================
+--- ContextsTest.cs     (revision 43469)
++++ ContextsTest.cs     (working copy)
+@@ -300,9 +300,9 @@
+        "012 (d1,c1) IContributeServerContextSink(1.d1).GetServerContextSink",
+        "013 (d1,c1) --> ServerContextSink(1.d1) SyncProcessMessage .ctor",
+        "014 (d1,c1) --> ServerContextSink(x.d1) SyncProcessMessage .ctor",
+-       "015 (d1,c1) List created",
+-       "016 (d1,c1) IContributeEnvoySink(1.d1).GetEnvoySink",
+-       "017 (d1,c1) IContributeEnvoySink(x.d1).GetEnvoySink",
++       "015 (d1,c1) IContributeEnvoySink(1.d1).GetEnvoySink",
++       "016 (d1,c1) IContributeEnvoySink(x.d1).GetEnvoySink",
++       "017 (d1,c1) List created",
+
+
+Note, it seems like System.Runtime could have it's own category here in
+bugzilla