These tests occasionally time out:
Test Case Failures:
1) MonoTests.System.ServiceModel.PeerResolvers.CustomPeerResolverServiceTest.CloseTest : System.TimeoutException : The operation has timed-out.
at System.ServiceModel.Channels.HttpRequestChannel+HttpChannelRequestAsyncResult.WaitEnd () [0x00000] in <filename unknown>:0
at System.ServiceModel.Channels.HttpRequestChannel.EndRequest (IAsyncResult result) [0x00000] in <filename unknown>:0
at System.ServiceModel.Channels.HttpRequestChannel.Request (System.ServiceModel.Channels.Message message, TimeSpan timeout) [0x00000] in <filename unknown>:0
at System.ServiceModel.MonoInternal.ClientRuntimeChannel.Request (System.ServiceModel.Channels.Message msg, TimeSpan timeout) [0x00000] in <filename unknown>:0
at System.ServiceModel.MonoInternal.ClientRuntimeChannel.Request (System.ServiceModel.Description.OperationDescription od, System.Object[] parameters) [0x00000] in <filename unknown>:0
at System.ServiceModel.MonoInternal.ClientRuntimeChannel.DoProcess (System.Reflection.MethodBase method, System.String operationName, System.Object[] parameters) [0x00000] in <filename unknown>:0
at System.ServiceModel.MonoInternal.ClientRuntimeChannel.Process (System.Reflection.MethodBase method, System.String operationName, System.Object[] parameters) [0x00000] in <filename unknown>:0
I.e. we're timing out waiting for the async wait handle here: https://github.com/mono/mono/blob/master/mcs/class/System.ServiceModel/System.ServiceModel.Channels/HttpRequestChannel.cs#L495
Since we have no current WCF maintainer and this is deep, deep within
WCF land and causes unstable builds on Jenkins, disable these tests
for now.
Bug: https://bugzilla.xamarin.com/show_bug.cgi?id=21069
Previously, many tests just had a return statement when the test shouldn't
be executed (e.g. Unix-only). This made it look like the test was successful
when in fact it wasn't executed at all.
Assert.Ignore() is now used instead to correctly exclude those tests.
* We now export simple <wsp:Policy>, currently supporting only
those elements that WsdlImporter can import.
WsdlImporter:
https://github.com/mono/mono/commit/cdc98dba1b83341c25a1daab4ae7c217d4961ad1
* Implement `MetadataExporter.Errors' and use it for error
reporting.
* Fixed WsdlExporter's caching to correclty deal with duplicate
ExportContract() and ExportEndpoint() calls.
* Emit <soap12:operation> depending on the binding's MessageVersion.
(FIXME: I didn't implement soap faults yet).
* MetadataTests: Check whether the policy elements are correct.
* MetadataTests: Add test containing simple [OperationContract] method
for http and net.tcp; checks the <soap:operation> / <soap12:operation>
elements.
* New test to check WsdlExporter's behavior regarding duplicate
contracts and endpoints.
* ConnectionOrientedTransportBindingElement.cs, CustomBindingTests.cs,
HttpTransportBindingElementTest.cs: Added test for custom message
encodings.
Only check whether 'System.Web.Services.Binding.Extensions' contains
the policy XmlElement when importing metadata, not when creating it
programmatically.
We now run the same tests from ImportTests.cs three times
using the following profiles:
* We load the metadata from an XML file.
* We create the metadata programmatically.
* We create the metadata programmatically, export it into
XML, then import it back (round-trip).
The WsdlImporter can now import Bindings and Endpoints
from the WSDL, currently supporting BasicHttpBinding,
BasicHttpsBinding and NetTcpBinding.
There is also - limited and still experimental - support
for WS-Policy 1.5. I only did the very basic pieces so
far, for instance things like TransportWithMessageCredentials
are not supported yet.
The policy importer will emit lots of warnings via
`MetadataImporter.Errors` (as warnings, not errors) whenever
it encounters something that it doesn't understand and
is also forgiving towards unknown and/or mal-formed
policy assertions.
This behavior is different from the MS runtime, which is
very strict, but there are simply too many missing pieces
to be more pedentic here. Check whether Errors.Count == 0
to see whether all policy assertions have been correctly
imported.
There are also a few metadata samples, which are part of the
new nunit tests. These are currently working:
BasicHttp.xml, BasicHttp_Mtom.xml, BasicHttp_NtlmAuth.xml,
BasicHttp_TransportSecurity.xml, BasicHttps.xml,
BasicHttps_NtlmAuth.xml, NetTcp.xml, NetTcp_TransferMode.xml,
NetTcp_TransportSecurity.xml
There are a few more in the Tests/MetadataTests/Resources/
directory which demonstrate missing pieces.
There is no bug report, the problem has been reported here:
http://stackoverflow.com/questions/12551090/monotouch-wcf-service-reference-cs-errors/12669880
DataContractSerializerMessageContractImporter.IsOperationImported()
did not check the method's return value, so it failed to recognize
methods such as
[OperationContract]
DateTime GetDate ();
as already being imported. This caused the method to be imported with
both the DataContractMessageContractImporterInternal and the
XmlSerializerMessageContractImporterInternal, but the latter does not
resolve type references, see the FIXME in that class.
I also added a new test case for this.
For instance:
ServiceHost host = new ServiceHost (typeof (Foo), new Uri ("http://localhost/echo"));
var b = host.AddServiceEndpoint (typeof (Foo), new BasicHttpBinding (), "/b");
should resolve into 'http://localhost/echo/b'.
Fixes: http://bugzilla.xamarin.com/show_bug.cgi?id=1164
The breakage reported in #1164 was caused by commit 106fdeb4, which
fixed bxc206. The problem is that in fixing bxc206, response messages
of a type having a MessageContractAttribute custom attribute were
changed to have a `void` return type, according to the
MessageDescription's Body.ReturnValue.Type property.
This fix is correct, in that it's what .NET does, but it broke XML
deserialization which expected the "actual" return type to exist, not
`void`.
Case in point: the added IService1.EndJSMGetDatabases() method will
have a MessageDescription with a Body.ReturnValue.Type=typeof(void).
The problem is that deserializing this message will fail:
System.Runtime.Serialization.SerializationException: Deserializing
type 'System.Void'. Expecting state 'EndElement'. Encountered state
'Text' with name '' with namespace ''.
Obviously this is not good. ;-)
The fix is simple: don't use the MessageDescription's ReturnValue if
it's `typeof(void)`.
There are two added wrinkles:
1. Writing a test case for the above.
2. The test case broke with another error: a NRE within
BaseMessagesFormatter.MessageObjectToParts(). This is because
when ContractDescriptionGenerator.GetMessage() sets the
ReturnValue for a response message, it doesn't set
MessagePartDescription.MemberInfo.
BaseMessagesFormatter.MessageObjectToParts(), meanwhile, was
checking the ReturnValue's MemberInfo...which was null.
Add a null check here so that the actual bug can be tested.
For reasons I currently can't explain, the Service1Client test type
appears to support having only one async operation "in flight" at a
time. As a result of this, calling multiple Async methods on the
Service1Client instance, as was done previously, would result in not
all of the event handlers being invoked, and the test timing out
after 60s instead of exiting quickly because all event handlers had
been raised.
I don't understand enough of WCF & this code to say why Service1Client
can have only one async operation in progress at once, but making this
change so that each async operation operates on a separate instance
speeds up the Bug652331_2Test execution from 60s to 5s.
* System.ServiceModel_test.dll.sources: Add new files to the tests
* Test/NUnitMoonHelper.cs: Helper to re-use Moonlight unit tests on NUnit
* Test/System.ServiceModel.Channels/CommunicationObjectSyncTest.cs: New.