Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Gallio exception with visual studio 2015 #6

Open
bobbyislam opened this issue Jul 29, 2015 · 17 comments
Open

Gallio exception with visual studio 2015 #6

bobbyislam opened this issue Jul 29, 2015 · 17 comments

Comments

@bobbyislam
Copy link

A fatal exception occurred while exploring tests. Possible causes include invalid test runner parameters.
Gallio.Model.ModelException: An exception occurred while invoking a test driver. ---> System.Runtime.Serialization.SerializationException: Type 'Microsoft.Cci.Pdb.PdbDebugException' in Assembly 'Gallio, Version=3.4.0.0, Culture=neutral, PublicKeyToken=eb9cfa67ee6ab36e' is not marked as serializable.
HResult: -2146233076

Server stack trace:
at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter, SerializationBinder binder)
at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Write(WriteObjectInfo objectInfo, NameInfo memberNameInfo, NameInfo typeNameInfo)
at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, Header[] inHeaders, __BinaryWriter serWriter, Boolean fCheck)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph, Header[] headers, Boolean fCheck)
at System.Runtime.Remoting.Channels.BinaryServerFormatterSink.SerializeResponse(IServerResponseChannelSinkStack sinkStack, IMessage msg, ITransportHeaders& headers, Stream& stream)
at System.Runtime.Remoting.Channels.BinaryServerFormatterSink.ProcessMessage(IServerChannelSinkStack sinkStack, IMessage requestMsg, ITransportHeaders requestHeaders, Stream requestStream, IMessage& responseMsg, ITransportHeaders& responseHeaders, Stream& responseStream)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Gallio.Model.Isolation.HostedTestIsolationContext.RunIsolatedTaskDelegate.EndInvoke(IAsyncResult result)
at Gallio.Model.Isolation.HostedTestIsolationContext.RunIsolatedTaskInHost[TIsolatedTask](HostSetup hostSetup, StatusReporter statusReporter, Object[] args) in c:\Server\Projects\MbUnit v3\Work\src\Gallio\Gallio\Model\Isolation\HostedTestIsolationContext.cs:line 127
at Gallio.Model.Isolation.HostedTestIsolationContext.RunIsolatedTaskImpl[TIsolatedTask](HostSetup hostSetup, StatusReporter statusReporter, Object[] args) in c:\Server\Projects\MbUnit v3\Work\src\Gallio\Gallio\Model\Isolation\HostedTestIsolationContext.cs:line 83
at Gallio.Model.DotNetTestDriver.ExploreOrRunAssembly(ITestIsolationContext testIsolationContext, TestPackage testPackage, TestExplorationOptions testExplorationOptions, TestExecutionOptions testExecutionOptions, RemoteMessageSink remoteMessageSink, IProgressMonitor progressMonitor, String taskName, FileInfo file) in c:\Server\Projects\MbUnit v3\Work\src\Gallio\Gallio\Model\DotNetTestDriver.cs:line 195
at Gallio.Model.DotNetTestDriver.ExploreOrRun(ITestIsolationContext testIsolationContext, TestPackage testPackage, TestExplorationOptions testExplorationOptions, TestExecutionOptions testExecutionOptions, IMessageSink messageSink, IProgressMonitor progressMonitor, String taskName) in c:\Server\Projects\MbUnit v3\Work\src\Gallio\Gallio\Model\DotNetTestDriver.cs:line 156
at Gallio.Model.DotNetTestDriver.ExploreImpl(ITestIsolationContext testIsolationContext, TestPackage testPackage, TestExplorationOptions testExplorationOptions, IMessageSink messageSink, IProgressMonitor progressMonitor) in c:\Server\Projects\MbUnit v3\Work\src\Gallio\Gallio\Model\DotNetTestDriver.cs:line 141
at Gallio.Model.DefaultTestFrameworkManager.FilteredTestDriver.<>c__DisplayClass1b.b__19(ITestDriver driver, IList1 items, Int32 driverCount) in c:\Server\Projects\MbUnit v3\Work\src\Gallio\Gallio\Model\DefaultTestFrameworkManager.cs:line 446 at Gallio.Model.DefaultTestFrameworkManager.FilteredTestDriver.ForEachDriver[T](MultiMap2 testFrameworkPartitions, Func4 func) in c:\Server\Projects\MbUnit v3\Work\src\Gallio\Gallio\Model\DefaultTestFrameworkManager.cs:line 528 --- End of inner exception stack trace --- HResult: -2146233088 at Gallio.Model.DefaultTestFrameworkManager.FilteredTestDriver.ForEachDriver[T](MultiMap2 testFrameworkPartitions, Func`4 func) in c:\Server\Projects\MbUnit v3\Work\src\Gallio\Gallio\Model\DefaultTestFrameworkManager.cs:line 534
at Gallio.Model.DefaultTestFrameworkManager.FilteredTestDriver.ExploreImpl(ITestIsolationContext testIsolationContext, TestPackage testPackage, TestExplorationOptions testExplorationOptions, IMessageSink messageSink, IProgressMonitor progressMonitor) in c:\Server\Projects\MbUnit v3\Work\src\Gallio\Gallio\Model\DefaultTestFrameworkManager.cs:line 439
at Gallio.Runner.DefaultTestRunner.Explore(TestPackage testPackage, TestExplorationOptions testExplorationOptions, IProgressMonitor progressMonitor) in c:\Server\Projects\MbUnit v3\Work\src\Gallio\Gallio\Runner\DefaultTestRunner.cs:line 242
@aharrim
Copy link

aharrim commented Aug 28, 2015

I got the same issue !
Is Gallio Icarus running (Supporting) on Visual Enterprise 2015 ?

Thanks,

@gas421
Copy link

gas421 commented Sep 18, 2015

Hello, actually I have the same issue with VS2015 and Gallio.
Will Gallio will support it?
Thanks

@seanamos
Copy link

Also experiencing this with our projects that use MBUnit

@gas421
Copy link

gas421 commented Oct 23, 2015

It will be supported?

@gesmaks
Copy link

gesmaks commented Nov 18, 2015

I am experiencing the same issue when running tests on Gallio Icarus 3.4 build 11. The test assembly was built using Visual Studio 2015 Professional. The tests worked fine when the test assembly was built using VS 2013.

@gas421
Copy link

gas421 commented Nov 18, 2015

This project I guess is discontinued... so sad....

@radekpribyl
Copy link

I found a workaround - I installed msbuild v12 (2013) and when I build the test project using this version of mbuild I'm able to run it from Gallio Icarus. When I built it from VS2015 using msbuild v14 I had the same error as described here

@gesmaks
Copy link

gesmaks commented Mar 14, 2016

The workaround provided by @radekpribyl works for me. Thank you very much!

@Subanki
Copy link

Subanki commented Mar 17, 2016

Hi all,
Any help with the below stuff is much appreciated.
I really need some support on How Can I run my MBunit tests in Gallio Echo. I have my MBunit tests in VS2013. I could add the test.dll in Gallio Icarus and run it manually. But I would like to do it from command line using gallio echo. I am not sure how to start with this.

I have my test.dll in this path in my local machine "C:\Users\suba\Documents\Visual Studio 2013\Projects\Links\Links\bin\Debug\Tests.dll"

I have my Gallio.Echo.Exe installed in this path "C:\Gallio\bin"

I know the command to run tests.dll is 'Gallio.Echo Tests.dll'
I don't know from which path and what command to use to run my test.dll in command line

Should we need anything else that needs to be specified within my test code. Please guide with this.

@ssg
Copy link

ssg commented Apr 17, 2016

I worked on this today. The problem was that the Microsoft.Cci.Metadata library which was used in Gallio 3.4 did not support the new PDB files generated by VS2015, (it fails with "unknown metadata code 7" exception). Because the library code was embedded in the assembly (or some other magic I'm not aware of), updating to new DLL's was not possible. I got Gallio build on VS2015, get an updated Microsoft.Cci.Metadata build (no binary distributions exist), made the build work half-assed. The final problem is that assembly versions show up as 0.0.0.0 and that causes problems with the test runner. Feel free to clone from https://github.com/ssg/mbunit-v3 and hack away. I will update this thread if I get to make it work perfectly.

@aprajitamathur
Copy link

aprajitamathur commented May 2, 2016 •
edited
Loading

The workaround by @radekpribyl worked for me as well . Thank you !

@awalsh128
Copy link

To those using the suggestion from @radekpribyl . Understand this isn't a workaround, it is just rolling back to the SDK that already works with MbUnit. You still lose the features introduced in the newer SDK that came with VS2015.

@ssg
Copy link

ssg commented Jun 3, 2016

I gave up and switched to NUnit fyi. https://gist.github.com/ssg/5329684

@awalsh128
Copy link

Same boat as you. NUnit has active dev and the easiest migration path from MbUnit. Thanks for providing the cheat sheet.

@j9brown
Copy link
Contributor

j9brown commented Jun 5, 2016

sigh

On Fri, Jun 3, 2016, 3:06 PM Andrew Walsh [email protected] wrote:

Same boat as you. NUnit has active dev and the easiest migration path from
MbUnit. Thanks for providing the cheat sheet.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#6 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AAGPhGEvu2Q9Cl1GhpzvK3CIRrcHg6PKks5qIKVdgaJpZM4FiBRw
.

@tgiphil
Copy link

tgiphil commented Jun 5, 2016

We switched to xunit:

https://github.com/xunit/xunit
http://xunit.github.io/

@Sharkhayn
Copy link

Sharkhayn commented Jun 9, 2016 •
edited
Loading

Hello I try use the @radekpribyl solution, but I don't know how.

Where do I specify the msbuild version for a local build ?

cc @gesmaks @aprajitamathur

Thanks.

@xmorera xmorera mentioned this issue May 23, 2017
Closed
@jeremy-jameson jeremy-jameson mentioned this issue Nov 21, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests