http://bugzilla.novell.com/show_bug.cgi?id=599488
http://bugzilla.novell.com/show_bug.cgi?id=599488#c2 Lex Li <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|[email protected] | --- Comment #2 from Lex Li <[email protected]> 2010-04-25 23:53:02 UTC --- Hi Gonzalo, Below is how to reproduce it, 1. Check out #SNMP Change Set 41774 http://sharpsnmplib.codeplex.com/SourceControl/list/changesets 2. Use xbuild to build SharpSnmpLib.sln. 3. Go to TestAgent/bin/Debug, open a prompt. 4. Use su to run mono snmpd.exe. 5. Click Disabled button so this application starts to monitor port 161 on all incoming SNMP messages. 6. Then open SharpSnmpLib.sln in MonoDevelop. 7. Open the Unit Tests panel and go to TestGetRequestMessage.TestTimeOut test case. 8. Execute this test case. The test case is simply that I send a UDP packet to a nonexisting IP address in my network and expect a SocketException for timeout. On Windows, a SocketException whose ErrorCode is 10060 is there, so #SNMP will package it up to TimeoutException. But on Mono/openSUSE, I receive a SocketException whose ErrorCode is 10035. This breaks the test case. I am not the only one who hits this issue, and you can check this StackOverflow post, http://stackoverflow.com/questions/1010708/10035-error-on-a-blocking-socket/2706837#2706837 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
