Bug 44650 - DispatchOperationTest.FaultContractInfos fails with wrong exception
Summary: DispatchOperationTest.FaultContractInfos fails with wrong exception
Alias: None
Product: Class Libraries
Classification: Mono
Component: WCF assemblies ()
Version: master
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Marek Safar
Depends on:
Reported: 2016-09-22 22:01 UTC by Andi McClure
Modified: 2017-09-06 16:55 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Andi McClure 2016-09-22 22:01:30 UTC
One of the ServiceModel tests intentionally fails a contract, and expects to see a contract-related exception.

Occasionally (in automated tests we've seen this happen about four times over a week, on random Linux platforms, always Linux) it will instead fail with an ObjectDisposedException.



Stack looks like 

  Expected: <System.ServiceModel.FaultException`1[MonoTests.System.ServiceModel.Dispatcher.DispatchOperationTest+PrivateAffairError]>
  But was:  <System.ObjectDisposedException>

                                                STACK TRACE:
                                                at MonoTests.System.ServiceModel.Dispatcher.DispatchOperationTest.FaultContractInfos () [0x00136] in /media/ssd/jenkins/workspace/test-mono-mainline-linux/label/debian-8-armel/mcs/class/System.ServiceModel/Test/System.ServiceModel.Dispatcher/DispatchOperationTest.cs:124
at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&)
at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00038] in /media/ssd/jenkins/workspace/test-mono-mainline-linux/label/debian-8-armel/mcs/class/corlib/System.Reflection/MonoMethod.cs:305
Comment 1 Marek Safar 2016-10-11 14:59:15 UTC
Updated the tests, so closing for now. If the issue reappears there it should have more info