Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
gallio-dev
Home
+ new post
About this group
Join this group
slow debugging with TD.NET+gallio+mbunit
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   20 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Mike Nichols  
View profile  
 More options Dec 19 2008, 12:20 pm
From: Mike Nichols <nichols.mik...@gmail.com>
Date: Fri, 19 Dec 2008 09:20:23 -0800 (PST)
Local: Fri, Dec 19 2008 12:20 pm
Subject: slow debugging with TD.NET+gallio+mbunit
Print | Individual message | Show original | Report this message | Find messages by this author
When I run td.net (most recent build) with debugger on mbunit tests,
the execution is extremely slow. It eventually gets there but
something is slowing it down.
On another project I was running tests that use XUnit with debugger in
td.net and I didn't have the same problems.

I have a recent copy of Gallio.

Any ideas where I might look that is causing this? Do you think this
is a td.net issue?


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Jeff Brown  
View profile  
 More options Dec 19 2008, 6:43 pm
From: "Jeff Brown" <jeff.br...@gmail.com>
Date: Fri, 19 Dec 2008 15:43:52 -0800
Local: Fri, Dec 19 2008 6:43 pm
Subject: Re: slow debugging with TD.NET+gallio+mbunit
Print | Individual message | Show original | Report this message | Find messages by this author

Is the delay on the order of 5-10 seconds?

On Fri, Dec 19, 2008 at 9:20 AM, Mike Nichols <nichols.mik...@gmail.com>wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Corey  
View profile  
 More options Dec 20 2008, 1:25 pm
From: Corey <co...@kaylors.net>
Date: Sat, 20 Dec 2008 10:25:58 -0800 (PST)
Local: Sat, Dec 20 2008 1:25 pm
Subject: Re: slow debugging with TD.NET+gallio+mbunit
Print | Individual message | Show original | Report this message | Find messages by this author
We experience a similar slow debugging experience when debugging with
the Resharper and Gallio with MBUnit. However, running XUnit tests
there are no performance problems. On average F10 takes two seconds
per line for us.

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Mike Nichols  
View profile  
 More options Dec 23 2008, 3:17 am
From: Mike Nichols <nichols.mik...@gmail.com>
Date: Tue, 23 Dec 2008 00:17:02 -0800 (PST)
Local: Tues, Dec 23 2008 3:17 am
Subject: Re: slow debugging with TD.NET+gallio+mbunit
Print | Individual message | Show original | Report this message | Find messages by this author
Sorry, just got back
My experience is similar to Corey's. Stepping thru is painful...

On Dec 20, 11:25 am, Corey <co...@kaylors.net> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Mike Nichols  
View profile  
 More options Jan 22 2009, 12:17 am
From: Mike Nichols <nichols.mik...@gmail.com>
Date: Wed, 21 Jan 2009 21:17:33 -0800 (PST)
Local: Thurs, Jan 22 2009 12:17 am
Subject: Re: slow debugging with TD.NET+gallio+mbunit
Print | Individual message | Show original | Report this message | Find messages by this author
Sorry to revisit this but I am still not able to figure out why
debugging with MbUnit is so slow. I notice there are a slough of
SymWrapper.dll exceptions (I think that was the name of the dll) but
not sure that is related.
I am on Server 2003R2, VMWare, VS 2008 SP1, REsharper 4.1 and only the
TD.NET runner used (Resharper plugin is not installed) and VS addin is
not loaded either (that was hanging Visual Studio).
I am using a recent build (r627 I think of 3.0.6).

Is there something I should look into like an error log to track this
down? If not, how can I use MbUnit with TestDriven.NET from the latest
distro? Just add the registry key in TD.NET?

@Jeff, you asked earlier on this thread if the delay is on the order
of 5-10 seconds...yes, it is for each F10 strike.

Thanks in advance
Mike

On Dec 23 2008, 1:17 am, Mike Nichols <nichols.mik...@gmail.com>
wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Jeff Brown  
View profile  
 More options Jan 22 2009, 1:02 am
From: Jeff Brown <jeff.br...@gmail.com>
Date: Wed, 21 Jan 2009 22:02:17 -0800 (PST)
Local: Thurs, Jan 22 2009 1:02 am
Subject: Re: slow debugging with TD.NET+gallio+mbunit
Print | Individual message | Show original | Report this message | Find messages by this author
That's much worse than it should be.

You might consider disabling automatic evaluation of properties as well as the exceptuon assistant.

You can use any version of tdnet.  If it wasn't installed beforehand then just runn the Gallio installer again to install the missing components.

As for comexceptions they do slow down initial startup and are a nuisance besides.  I need to investigate whether I can work around them short of rewriting isymwrapper.

Jeff.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Mads Nissen  
View profile  
 More options Jan 22 2009, 8:00 am
From: Mads Nissen <mads.nis...@gmail.com>
Date: Thu, 22 Jan 2009 05:00:34 -0800 (PST)
Local: Thurs, Jan 22 2009 8:00 am
Subject: Re: slow debugging with TD.NET+gallio+mbunit
Print | Individual message | Show original | Report this message | Find messages by this author
Just as a really vague side note; I watched some TD.NET execution of
MSTest stuff in a live meeting yesterday and it did about 50 unittests
in no time compared to what I'm seeing for similar stuff with mbunit.

I'd be glad to collect any data that might be relevant to aid in this
issue..

mads

On Jan 22, 7:02 am, Jeff Brown <jeff.br...@gmail.com> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Mario  
View profile  
 More options Jan 22 2009, 9:39 am
From: Mario <pareja.ma...@gmail.com>
Date: Thu, 22 Jan 2009 06:39:57 -0800 (PST)
Local: Thurs, Jan 22 2009 9:39 am
Subject: Re: slow debugging with TD.NET+gallio+mbunit
Print | Individual message | Show original | Report this message | Find messages by this author

Hi,

I always see a 5 to 10 second  delay when launching MbUnit tests with
the debugger using TD .net.  If I look at the output window it appears
the delay is occurring while loading the plethora of DLLs that come
with Gallio.  Has anyone else noticed this?

Regards,

Mario


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Jeff Brown  
View profile  
 More options Jan 22 2009, 8:17 pm
From: Jeff Brown <jeff.br...@gmail.com>
Date: Thu, 22 Jan 2009 17:17:57 -0800
Local: Thurs, Jan 22 2009 8:17 pm
Subject: Re: slow debugging with TD.NET+gallio+mbunit
Print | Individual message | Show original | Report this message | Find messages by this author

That is correct.  Gallio is loading lots of dlls on startup and this slows
down execution in TDNet, particularly with the debugger.

The plan is to rewrite the plugin loading process so that more declarative
information is available up-front and fewer dlls are loaded until actually
required.

Jeff.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Johan Appelgren  
View profile  
 More options Jan 27 2009, 8:26 am
From: Johan Appelgren <johan.appelg...@gmail.com>
Date: Tue, 27 Jan 2009 14:26:11 +0100
Local: Tues, Jan 27 2009 8:26 am
Subject: Re: slow debugging with TD.NET+gallio+mbunit
Print | Individual message | Show original | Report this message | Find messages by this author
Using ReSharper and Gallio v3.0.5 I also get slow source stepping when
debugging tests, there's a significant delay when pressing F10.

Disabling "property evaluation and other implicit function calls" in
the VS options fixes this, stepping is as quick as when debugging
normally. Is it the gallio test-runner that somehow causes this?

/Johan


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Jeff Brown  
View profile  
 More options Jan 27 2009, 2:19 pm
From: Jeff Brown <jeff.br...@gmail.com>
Date: Tue, 27 Jan 2009 11:19:11 -0800
Local: Tues, Jan 27 2009 2:19 pm
Subject: Re: slow debugging with TD.NET+gallio+mbunit
Print | Individual message | Show original | Report this message | Find messages by this author

I don't think it's really Gallio's fault here unless there happen to be some
Gallio or MbUnit objects in local scope while you're stepping (unlikely).

As far as I can tell, Visual Studio is just trying to do too much work
between steps as it reevaluates properties each time.  Some projects are
more affected by others.  For example, WatiN projects are hopelessly slow to
step through unless property evaluation is disabled because each evaluation
can result in a COM call to IE.

Jeff.

On Tue, Jan 27, 2009 at 5:26 AM, Johan Appelgren
<johan.appelg...@gmail.com>wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Johan Appelgren  
View profile  
 More options Jan 28 2009, 3:19 am
From: Johan Appelgren <johan.appelg...@gmail.com>
Date: Wed, 28 Jan 2009 09:19:46 +0100
Local: Wed, Jan 28 2009 3:19 am
Subject: Re: slow debugging with TD.NET+gallio+mbunit
Print | Individual message | Show original | Report this message | Find messages by this author
I guess it's something with how Gallio runs tests. Because if I debug
NUnit tests with the ReSharper NUnit runner it's very fast.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Jeff Brown  
View profile  
 More options Jan 28 2009, 8:44 pm
From: Jeff Brown <jeff.br...@gmail.com>
Date: Wed, 28 Jan 2009 17:44:52 -0800
Local: Wed, Jan 28 2009 8:44 pm
Subject: Re: slow debugging with TD.NET+gallio+mbunit
Print | Individual message | Show original | Report this message | Find messages by this author

Would the same tests written with MbUnit vs. NUnit behave any differently
with respect to debugger single-stepping?  It's possible but I just don't
have an action principle to explain why besides well-known issues with
implicit function evaluation in the VS Debugger...

Are there particular lines of code that are slow to step over vs. others?

Jeff.

On Wed, Jan 28, 2009 at 12:19 AM, Johan Appelgren <johan.appelg...@gmail.com


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Johan Appelgren  
View profile  
 More options Jan 29 2009, 5:20 am
From: Johan Appelgren <johan.appelg...@gmail.com>
Date: Thu, 29 Jan 2009 11:20:21 +0100
Local: Thurs, Jan 29 2009 5:20 am
Subject: Re: slow debugging with TD.NET+gallio+mbunit
Print | Individual message | Show original | Report this message | Find messages by this author
I created two test projects, one that uses MbUnit and one that uses NUnit.

Stepping through the test method in the MbUnit version is slow but not
in the NUnit version. I used the Gallio ReSharper plugin to debug the
MbUnit test, and the NUnit ReSharper plugin to debug the NUnit test.
Not sure what VS could be doing different in the Gallio case.

namespace MbUnit
{
    using MbUnit.Framework;

    [TestFixture]
    public class Fixture
    {
        [Test]
        public void Test()
        {
            int i = 1 + 1;
            Assert.AreEqual(2, i);
        }
    }

}

namespace NUnit
{
    using NUnit.Framework;

    [TestFixture]
    public class Fixture
    {
        [Test]
        public void Test()
        {
            int i = 1 + 1;
            Assert.AreEqual(2, i);
        }
    }


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Corey  
View profile  
 More options Feb 16 2009, 3:01 pm
From: Corey <co...@kaylors.net>
Date: Mon, 16 Feb 2009 12:01:40 -0800 (PST)
Local: Mon, Feb 16 2009 3:01 pm
Subject: Re: slow debugging with TD.NET+gallio+mbunit
Print | Individual message | Show original | Report this message | Find messages by this author
I've tried debugging MbUnit tests in 3.0.6.683 and the performance is
still really slow. It doesn't appear to be Gallio related. It seems
more specific to MbUnit. I can use Gallio to debug MbUnit vs. xUnit
and the performance for the xUnit is significantly faster even against
the exact same tests.

//using MbUnit.Framework;
using Xunit;

namespace UnitTest
{
        //[TestFixture]
        public class TestCase
        {
                [Fact]
                //[Test]
                public void Debug_Performance_Test()
                {
                        string test = "";
                        string stepInto = "slow on mbunit";
                        string thirdStep = "nothing crazy going on here.";
                }
        }


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Jeff Brown  
View profile  
 More options Feb 16 2009, 3:25 pm
From: Jeff Brown <jeff.br...@gmail.com>
Date: Mon, 16 Feb 2009 12:25:20 -0800
Local: Mon, Feb 16 2009 3:25 pm
Subject: Re: slow debugging with TD.NET+gallio+mbunit
Print | Individual message | Show original | Report this message | Find messages by this author
Hmm it just occurred to me.  Does it run much faster if you close the  
stack trace view (temporarily)?

On Feb 16, 2009, at 12:01 PM, Corey <co...@kaylors.net> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Corey  
View profile  
 More options Feb 16 2009, 3:59 pm
From: Corey <co...@kaylors.net>
Date: Mon, 16 Feb 2009 12:59:47 -0800 (PST)
Local: Mon, Feb 16 2009 3:59 pm
Subject: Re: slow debugging with TD.NET+gallio+mbunit
Print | Individual message | Show original | Report this message | Find messages by this author
No, it seems about the same. I tried closing other windows too just in
case.

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Jeff Brown  
View profile  
 More options Feb 16 2009, 4:17 pm
From: Jeff Brown <jeff.br...@gmail.com>
Date: Mon, 16 Feb 2009 13:17:13 -0800
Local: Mon, Feb 16 2009 4:17 pm
Subject: Re: slow debugging with TD.NET+gallio+mbunit
Print | Individual message | Show original | Report this message | Find messages by this author
So what occurred to me today is that MbUnit's stack depth is  
significantly greater than it used to be (using lots of anonymous  
delegates to compose behaviours).  It probably uses more ram too.  
Xunit's would still be quite light under Gallio.  Anyways I expect  
Visual Studio is doing a lot of work updating its views.  The trick is  
isolating which update is the hotspot is and then figuring out if we  
can even do anything about it.

I should point out that my own personal debugging experience is  
acceptably fast even on a relatively underpowered laptop.

On Feb 16, 2009, at 12:59 PM, Corey <co...@kaylors.net> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Corey  
View profile  
 More options Feb 16 2009, 5:16 pm
From: Corey <co...@kaylors.net>
Date: Mon, 16 Feb 2009 14:16:10 -0800 (PST)
Local: Mon, Feb 16 2009 5:16 pm
Subject: Re: slow debugging with TD.NET+gallio+mbunit
Print | Individual message | Show original | Report this message | Find messages by this author
The top section is the stack from xUnit, and the bottom is MbUnit. I'm
wondering if you notice something significantly different in the
MbUnit stack that would explain why you're getting better performance?

>    UnitTest.DLL!UnitTest.TestCase.Debug_Performance_Test() Line 13 C#

        [Native to Managed Transition]
        [Managed to Native Transition]
        xunit.dll!Xunit.Sdk.TestCommand.Execute(object testClass =
{UnitTest.TestCase}) + 0x4d bytes
        xunit.dll!Xunit.Sdk.FixtureCommand.Execute(object testClass =
{UnitTest.TestCase}) + 0x155 bytes
        xunit.dll!Xunit.Sdk.BeforeAfterCommand.Execute(object testClass =
{UnitTest.TestCase}) + 0x14c bytes
        xunit.dll!Xunit.Sdk.LifetimeCommand.Execute(object testClass =
{UnitTest.TestCase}) + 0x73 bytes
        xunit.dll!Xunit.Sdk.ExceptionWrapperCommand.Execute.AnonymousMethod
() + 0x34 bytes
        xunit.dll!Xunit.Sdk.ExceptionWrapperCommand.RunAndCatch
(Xunit.Sdk.ExceptionWrapperCommand.ExecutionDelegate delegate =
{Method = {Xunit.Sdk.MethodResult <Execute>b__0()}}) + 0x45 bytes
        xunit.dll!Xunit.Sdk.ExceptionWrapperCommand.Execute(object testClass
= null) + 0x81 bytes
        xunit.dll!Xunit.Sdk.TimedCommand.Execute(object testClass = null) +
0x62 bytes
        xunit.dll!Xunit.Sdk.TraceAssertCommand.Execute(object testClass =
null) + 0x174 bytes
        Gallio.XunitAdapter.dll!
Gallio.XunitAdapter.Model.XunitTestController.RunTestCommandAndFinishStep
(Gallio.Model.Execution.ITestContext testContext =
{Gallio.Model.Execution.ObservableTestContext},
Xunit.Sdk.ITestClassCommand testClassCommand =
{Xunit.Sdk.TestClassCommand}, Xunit.Sdk.ITestCommand testCommand =
{Xunit.Sdk.TraceAssertCommand}) + 0x70 bytes
        Gallio.XunitAdapter.dll!
Gallio.XunitAdapter.Model.XunitTestController.RunTestCommands
(Gallio.Model.Execution.ITestCommand testCommand =
{Debug_Performance_Test}, Xunit.Sdk.ITestClassCommand testClassCommand
= {Xunit.Sdk.TestClassCommand},
System.Collections.Generic.IEnumerable<Xunit.Sdk.ITestCommand>
xunitTestCommands = Count = 1, Gallio.Model.ITestStep parentTestStep =
{[Step] TestCase}, bool isPrimary = true) + 0x15f bytes
        Gallio.XunitAdapter.dll!
Gallio.XunitAdapter.Model.XunitTestController.RunTestMethod
(Gallio.Model.Execution.ITestCommand testCommand =
{Debug_Performance_Test}, System.Reflection.MethodInfo methodInfo =
{Void Debug_Performance_Test()}, Xunit.Sdk.ITestClassCommand
testClassCommand = {Xunit.Sdk.TestClassCommand},
Gallio.Model.ITestStep parentTestStep = {[Step] TestCase}) + 0x1b2
bytes
        Gallio.XunitAdapter.dll!
Gallio.XunitAdapter.Model.XunitTestController.RunTestClassCommandAndFinishS tep
(Gallio.Model.Execution.ITestCommand testCommand = {TestCase},
Gallio.Model.Execution.ITestContext testContext =
{Gallio.Model.Execution.ObservableTestContext},
Xunit.Sdk.ITestClassCommand testClassCommand =
{Xunit.Sdk.TestClassCommand}) + 0x344 bytes
        Gallio.XunitAdapter.dll!
Gallio.XunitAdapter.Model.XunitTestController.RunTestFixture
(Gallio.Model.Execution.ITestCommand testCommand = {TestCase},
Gallio.XunitAdapter.Model.XunitTypeInfoAdapter typeInfo =
{UnitTest.TestCase}, Gallio.Model.ITestStep parentTestStep = {[Step]
UnitTest}) + 0x10e bytes
        Gallio.XunitAdapter.dll!
Gallio.XunitAdapter.Model.XunitTestController.RunTest
(Gallio.Model.Execution.ITestCommand testCommand = {TestCase},
Gallio.Model.ITestStep parentTestStep = {[Step] UnitTest},
Gallio.Runtime.ProgressMonitoring.IProgressMonitor progressMonitor =
{Gallio.Runtime.ProgressMonitoring.RemoteProgressMonitor}) + 0xb0
bytes
        Gallio.XunitAdapter.dll!
Gallio.XunitAdapter.Model.XunitTestController.RunTestsImpl
(Gallio.Model.Execution.ITestCommand rootTestCommand = {TestCase},
Gallio.Model.ITestStep parentTestStep = {[Step] UnitTest},
Gallio.Model.Execution.TestExecutionOptions options =
{Gallio.Model.Execution.TestExecutionOptions},
Gallio.Runtime.ProgressMonitoring.IProgressMonitor progressMonitor =
{Gallio.Runtime.ProgressMonitoring.RemoteProgressMonitor}) + 0xd1
bytes
        Gallio.dll!Gallio.Model.Execution.BaseTestController.RunTests
(Gallio.Model.Execution.ITestCommand rootTestCommand = {TestCase},
Gallio.Model.ITestStep parentTestStep = {[Step] UnitTest},
Gallio.Model.Execution.TestExecutionOptions options =
{Gallio.Model.Execution.TestExecutionOptions},
Gallio.Runtime.ProgressMonitoring.IProgressMonitor progressMonitor =
{Gallio.Runtime.ProgressMonitoring.RemoteProgressMonitor}) Line 42 +
0x17 bytes      C#
        Gallio.dll!Gallio.Model.Execution.RecursiveTestController.RunTest
(Gallio.Model.Execution.ITestCommand testCommand = {TestCase},
Gallio.Model.ITestStep parentTestStep = {[Step] UnitTest},
Gallio.Model.Execution.TestExecutionOptions options =
{Gallio.Model.Execution.TestExecutionOptions},
Gallio.Runtime.ProgressMonitoring.IProgressMonitor progressMonitor =
{Gallio.Runtime.ProgressMonitoring.RemoteProgressMonitor}) Line 53 +
0x18 bytes      C#
        Gallio.dll!
Gallio.Model.Execution.RecursiveTestController.RunNonMasterTest
(Gallio.Model.Execution.ITestCommand testCommand = {UnitTest},
Gallio.Model.ITestStep parentTestStep = {[Step] xUnit.net
v1.1.0.1323}, Gallio.Model.Execution.TestExecutionOptions options =
{Gallio.Model.Execution.TestExecutionOptions},
Gallio.Runtime.ProgressMonitoring.IProgressMonitor progressMonitor =
{Gallio.Runtime.ProgressMonitoring.RemoteProgressMonitor}) Line 85 +
0x42 bytes      C#
        Gallio.dll!Gallio.Model.Execution.RecursiveTestController.RunTest
(Gallio.Model.Execution.ITestCommand testCommand = {UnitTest},
Gallio.Model.ITestStep parentTestStep = {[Step] xUnit.net
v1.1.0.1323}, Gallio.Model.Execution.TestExecutionOptions options =
{Gallio.Model.Execution.TestExecutionOptions},
Gallio.Runtime.ProgressMonitoring.IProgressMonitor progressMonitor =
{Gallio.Runtime.ProgressMonitoring.RemoteProgressMonitor}) Line 67 +
0x14 bytes      C#
        Gallio.dll!
Gallio.Model.Execution.RecursiveTestController.RunNonMasterTest
(Gallio.Model.Execution.ITestCommand testCommand = {xUnit.net
v1.1.0.1323}, Gallio.Model.ITestStep parentTestStep = {[Step] Root},
Gallio.Model.Execution.TestExecutionOptions options =
{Gallio.Model.Execution.TestExecutionOptions},
Gallio.Runtime.ProgressMonitoring.IProgressMonitor progressMonitor =
{Gallio.Runtime.ProgressMonitoring.RemoteProgressMonitor}) Line 85 +
0x42 bytes      C#
        Gallio.dll!Gallio.Model.Execution.RecursiveTestController.RunTest
(Gallio.Model.Execution.ITestCommand testCommand = {xUnit.net
v1.1.0.1323}, Gallio.Model.ITestStep parentTestStep = {[Step] Root},
Gallio.Model.Execution.TestExecutionOptions options =
{Gallio.Model.Execution.TestExecutionOptions},
Gallio.Runtime.ProgressMonitoring.IProgressMonitor progressMonitor =
{Gallio.Runtime.ProgressMonitoring.RemoteProgressMonitor}) Line 67 +
0x14 bytes      C#
        Gallio.dll!
Gallio.Model.Execution.RecursiveTestController.RunNonMasterTest
(Gallio.Model.Execution.ITestCommand testCommand = {Root (explicit)},
Gallio.Model.ITestStep parentTestStep = null,
Gallio.Model.Execution.TestExecutionOptions options =
{Gallio.Model.Execution.TestExecutionOptions},
Gallio.Runtime.ProgressMonitoring.IProgressMonitor progressMonitor =
{Gallio.Runtime.ProgressMonitoring.RemoteProgressMonitor}) Line 85 +
0x42 bytes      C#
        Gallio.dll!
Gallio.Model.Execution.RecursiveTestController.RunTestsImpl
(Gallio.Model.Execution.ITestCommand rootTestCommand = {Root
(explicit)}, Gallio.Model.ITestStep parentTestStep = null,
Gallio.Model.Execution.TestExecutionOptions options =
{Gallio.Model.Execution.TestExecutionOptions},
Gallio.Runtime.ProgressMonitoring.IProgressMonitor progressMonitor =
{Gallio.Runtime.ProgressMonitoring.RemoteProgressMonitor}) Line 35 +
0x15 bytes      C#
        Gallio.dll!Gallio.Model.Execution.BaseTestController.RunTests
(Gallio.Model.Execution.ITestCommand rootTestCommand = {Root
(explicit)}, Gallio.Model.ITestStep parentTestStep = null,
Gallio.Model.Execution.TestExecutionOptions options =
{Gallio.Model.Execution.TestExecutionOptions},
Gallio.Runtime.ProgressMonitoring.IProgressMonitor progressMonitor =
{Gallio.Runtime.ProgressMonitoring.RemoteProgressMonitor}) Line 42 +
0x17 bytes      C#
        Gallio.dll!
Gallio.Runner.Harness.DefaultTestHarness.RunAllTestCommands.AnonymousMethod
() Line 291 + 0x20 bytes        C#
        mscorlib.dll!System.Threading.ThreadHelper.ThreadStart_Context
(object state) + 0x66 bytes
        mscorlib.dll!System.Threading.ExecutionContext.Run
(System.Threading.ExecutionContext executionContext,
System.Threading.ContextCallback callback, object state) + 0x6f bytes
        mscorlib.dll!System.Threading.ThreadHelper.ThreadStart() + 0x44
bytes
        [Appdomain Transition]

>    UnitTest.DLL!UnitTest.TestCase.Debug_Performance_Test() Line 13 C#

        [Native to Managed Transition]
        [Managed to Native Transition]
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestInstanceState.InvokeTestMethod()
Line 385 + 0x24 bytes   C#
        Gallio.dll!
Gallio.Framework.Pattern.TestMethodPatternAttribute.Execute
(Gallio.Framework.Pattern.PatternTestInstanceState state =
{Gallio.Framework.Pattern.PatternTestInstanceState}) Line 171 + 0xb
bytes   C#
        MbUnit.dll!MbUnit.Framework.TestAttribute.Execute
(Gallio.Framework.Pattern.PatternTestInstanceState state =
{Gallio.Framework.Pattern.PatternTestInstanceState}) Line 68 + 0xc
bytes   C#
        Gallio.dll!
Gallio.Framework.Pattern.TestMethodPatternAttribute.SetTestSemantics.Anonym ousMethod
(Gallio.Framework.Pattern.PatternTestInstanceState state =
{Gallio.Framework.Pattern.PatternTestInstanceState}) Line 161 + 0xb
bytes   C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestInstanceActions.ExecuteTestInstance
(Gallio.Framework.Pattern.PatternTestInstanceState testInstanceState =
{Gallio.Framework.Pattern.PatternTestInstanceState}) Line 200   C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestInstanceActions.ExecuteTestInstance
(Gallio.Framework.Pattern.PatternTestInstanceState testInstanceState =
{Gallio.Framework.Pattern.PatternTestInstanceState}) Line 200   C#
        Gallio.dll!
...

read more »


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Corey  
View profile  
 More options Feb 16 2009, 5:18 pm
From: Corey <co...@kaylors.net>
Date: Mon, 16 Feb 2009 14:18:13 -0800 (PST)
Local: Mon, Feb 16 2009 5:18 pm
Subject: Re: slow debugging with TD.NET+gallio+mbunit
Print | Individual message | Show original | Report this message | Find messages by this author
Hmm that didn't work out so well. This is the MbUnit stack only.

>    UnitTest.DLL!UnitTest.TestCase.Debug_Performance_Test() Line 13 C#

        [Native to Managed Transition]
        [Managed to Native Transition]
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestInstanceState.InvokeTestMethod()
Line 385 + 0x24 bytes   C#
        Gallio.dll!
Gallio.Framework.Pattern.TestMethodPatternAttribute.Execute
(Gallio.Framework.Pattern.PatternTestInstanceState state =
{Gallio.Framework.Pattern.PatternTestInstanceState}) Line 171 + 0xb
bytes   C#
        MbUnit.dll!MbUnit.Framework.TestAttribute.Execute
(Gallio.Framework.Pattern.PatternTestInstanceState state =
{Gallio.Framework.Pattern.PatternTestInstanceState}) Line 68 + 0xc
bytes   C#
        Gallio.dll!
Gallio.Framework.Pattern.TestMethodPatternAttribute.SetTestSemantics.Anonym ousMethod
(Gallio.Framework.Pattern.PatternTestInstanceState state =
{Gallio.Framework.Pattern.PatternTestInstanceState}) Line 161 + 0xb
bytes   C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestInstanceActions.ExecuteTestInstance
(Gallio.Framework.Pattern.PatternTestInstanceState testInstanceState =
{Gallio.Framework.Pattern.PatternTestInstanceState}) Line 200   C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestInstanceActions.ExecuteTestInstance
(Gallio.Framework.Pattern.PatternTestInstanceState testInstanceState =
{Gallio.Framework.Pattern.PatternTestInstanceState}) Line 200   C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestInstanceActions.ExecuteTestInstance
(Gallio.Framework.Pattern.PatternTestInstanceState testInstanceState =
{Gallio.Framework.Pattern.PatternTestInstanceState}) Line 200   C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestExecutor.DoExecuteTestInstance.Anonymou sMethod
() Line 508 + 0x1f bytes        C#
        Gallio.dll!Gallio.Framework.Sandbox.RunWithScope
(Gallio.Model.Logging.TestLogWriter testLogWriter =
{Gallio.Model.Logging.FallbackTestLogWriter},
Gallio.Concurrency.ThreadAbortScope scope =
{Gallio.Concurrency.ThreadAbortScope}, Gallio.Action action = {Method
= {Void <DoExecuteTestInstance>b__34()}}, string description = null)
Line 361 + 0xd bytes    C#
        Gallio.dll!Gallio.Framework.Sandbox.Run
(Gallio.Model.Logging.TestLogWriter testLogWriter =
{Gallio.Model.Logging.FallbackTestLogWriter}, Gallio.Action action =
{Method = {Void <DoExecuteTestInstance>b__34()}}, string description =
null) Line 338 + 0x18 bytes     C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestExecutor.DoExecuteTestInstance
(Gallio.Framework.TestContext context =
{Gallio.Framework.TestContext},
Gallio.Framework.Pattern.PatternTestInstanceState testInstanceState =
{Gallio.Framework.Pattern.PatternTestInstanceState}) Line 506 + 0x4b
bytes   C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestExecutor.RunTestInstanceWithContext
(Gallio.Model.Execution.ITestCommand testCommand =
{Debug_Performance_Test}, Gallio.Framework.TestContext context =
{Gallio.Framework.TestContext},
Gallio.Framework.Pattern.PatternTestInstanceState testInstanceState =
{Gallio.Framework.Pattern.PatternTestInstanceState}) Line 298 + 0x21
bytes   C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestExecutor.RunTestInstance.AnonymousMetho d
() Line 228 + 0x36 bytes        C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestExecutor.RunTestInstance.AnonymousMetho d
() Line 231     C#
        Gallio.dll!Gallio.Framework.Pattern.PatternTestInstanceState.RunBody
() Line 397 + 0x11 bytes        C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestInstanceActions..ctor.AnonymousMethod
(Gallio.Framework.Pattern.PatternTestInstanceState state =
{Gallio.Framework.Pattern.PatternTestInstanceState}) Line 56 + 0xe
bytes   C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestInstanceActions.RunTestInstanceBody
(Gallio.Framework.Pattern.PatternTestInstanceState testInstanceState =
{Gallio.Framework.Pattern.PatternTestInstanceState}) Line 234 + 0x22
bytes   C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestInstanceActions.RunTestInstanceBody
(Gallio.Framework.Pattern.PatternTestInstanceState testInstanceState =
{Gallio.Framework.Pattern.PatternTestInstanceState}) Line 234 + 0x22
bytes   C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestInstanceActions.RunTestInstanceBody
(Gallio.Framework.Pattern.PatternTestInstanceState testInstanceState =
{Gallio.Framework.Pattern.PatternTestInstanceState}) Line 234 + 0x22
bytes   C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestExecutor.DoRunTestInstanceBody.Anonymou sMethod
() Line 574 + 0x2e bytes        C#
        Gallio.dll!Gallio.Framework.Sandbox.RunWithScope
(Gallio.Model.Logging.TestLogWriter testLogWriter =
{Gallio.Model.Logging.FallbackTestLogWriter},
Gallio.Concurrency.ThreadAbortScope scope =
{Gallio.Concurrency.ThreadAbortScope}, Gallio.Action action = {Method
= {Void <DoRunTestInstanceBody>b__46()}}, string description = "Body")
Line 361 + 0xd bytes    C#
        Gallio.dll!Gallio.Framework.Sandbox.Run
(Gallio.Model.Logging.TestLogWriter testLogWriter =
{Gallio.Model.Logging.FallbackTestLogWriter}, Gallio.Action action =
{Method = {Void <DoRunTestInstanceBody>b__46()}}, string description =
"Body") Line 338 + 0x18 bytes C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestExecutor.DoRunTestInstanceBody
(Gallio.Framework.TestContext context =
{Gallio.Framework.TestContext},
Gallio.Framework.Pattern.PatternTestInstanceState testInstanceState =
{Gallio.Framework.Pattern.PatternTestInstanceState}) Line 572 + 0x4c
bytes   C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestExecutor.RunTestInstance
(Gallio.Model.Execution.ITestCommand testCommand =
{Debug_Performance_Test}, Gallio.Framework.TestContext primaryContext
= {Gallio.Framework.TestContext},
Gallio.Framework.Pattern.PatternTestState testState =
{Gallio.Framework.Pattern.PatternTestState},
Gallio.Framework.Data.IDataItem bindingItem =
{Gallio.Framework.Data.NullDataItem}, bool reusePrimaryTestStep =
true) Line 248 + 0x24 bytes     C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestExecutor.RunTestInstances
(Gallio.Model.Execution.ITestCommand testCommand =
{Debug_Performance_Test}, Gallio.Framework.TestContext primaryContext
= {Gallio.Framework.TestContext},
Gallio.Framework.Pattern.PatternTestState testState =
{Gallio.Framework.Pattern.PatternTestState}, bool reusePrimaryTestStep
= true) Line 175 + 0x26 bytes   C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestExecutor.RunTestBody.AnonymousMethod
() Line 146 + 0x53 bytes        C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestExecutor.DoWithApartmentState
(System.Threading.ApartmentState apartmentState = Unknown,
Gallio.Action action = {Method = {Void <RunTestBody>b__4()}}) Line 654
C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestExecutor.RunTestBody.AnonymousMethod
() Line 114 + 0x3b bytes        C#
        Gallio.dll!Gallio.Framework.Sandbox.UseTimeout(System.TimeSpan?
timeout = {00:10:00}, Gallio.Action action = {Method = {Void
<RunTestBody>b__3()}}) Line 268 + 0xb bytes       C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestExecutor.RunTestBody.AnonymousMethod
() Line 112 + 0x60 bytes        C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestExecutor.DoWithProcessIsolation
(Gallio.Action action = {Method = {Void <RunTestBody>b__2()}}) Line
633 + 0xb bytes C#
        Gallio.dll!Gallio.Framework.Pattern.PatternTestExecutor.RunTestBody
(Gallio.Model.Execution.ITestCommand testCommand =
{Debug_Performance_Test}, Gallio.Model.ITestStep parentTestStep =
{[Step] TestCase}, Gallio.Framework.Sandbox sandbox =
{Gallio.Framework.Sandbox},
Gallio.Framework.Pattern.PatternTestExecutor.PatternTestHandlerDecorator
testHandlerDecorator = {Method = {Gallio.Model.TestOutcome
<RunTestChildren>b__11(Gallio.Framework.Sandbox,
Gallio.Framework.Pattern.IPatternTestHandler ByRef)}},
Gallio.Framework.Pattern.PatternTest test = {[Test]
Debug_Performance_Test}) Line 164       C#
        Gallio.dll!Gallio.Framework.Pattern.PatternTestExecutor.RunTest
(Gallio.Model.Execution.ITestCommand testCommand =
{Debug_Performance_Test}, Gallio.Model.ITestStep parentTestStep =
{[Step] TestCase}, Gallio.Framework.Sandbox parentSandbox =
{Gallio.Framework.Sandbox},
Gallio.Framework.Pattern.PatternTestExecutor.PatternTestHandlerDecorator
testHandlerDecorator = {Method = {Gallio.Model.TestOutcome
<RunTestChildren>b__11(Gallio.Framework.Sandbox,
Gallio.Framework.Pattern.IPatternTestHandler ByRef)}}) Line 83 + 0x24
bytes   C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestExecutor.RunTestChildren.AnonymousMetho d
() Line 349 + 0x2c bytes        C#
        Gallio.dll!
Gallio.Framework.Pattern.ParallelizableTestCaseScheduler.WorkSet.UnsyncRunP reparedAction
(Gallio.Action action = {Method = {Void <RunTestChildren>b__10()}})
Line 185 + 0xb bytes    C#
        Gallio.dll!
Gallio.Framework.Pattern.ParallelizableTestCaseScheduler.WorkSet.RunToCompl etion
() Line 165 + 0xc bytes C#
        Gallio.dll!
Gallio.Framework.Pattern.ParallelizableTestCaseScheduler.Run
(System.Collections.Generic.IList<Gallio.Action> actions =
{Gallio.Action[1]}) Line 53     C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestExecutor.RunTestChildren
(Gallio.Model.Execution.ITestCommand testCommand = {TestCase},
Gallio.Framework.Sandbox sandbox = {Gallio.Framework.Sandbox},
Gallio.Framework.Pattern.PatternTestInstanceState testInstanceState =
{Gallio.Framework.Pattern.PatternTestInstanceState}) Line 326 + 0xb2
bytes   C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestExecutor.RunTestInstanceWithContext
(Gallio.Model.Execution.ITestCommand testCommand = {TestCase},
Gallio.Framework.TestContext context = {Gallio.Framework.TestContext},
Gallio.Framework.Pattern.PatternTestInstanceState testInstanceState =
{Gallio.Framework.Pattern.PatternTestInstanceState}) Line 302 + 0x55
bytes   C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestExecutor.RunTestInstance.AnonymousMetho d
() Line 228 + 0x36 bytes        C#
        Gallio.dll!
Gallio.Framework.Pattern.PatternTestExecutor.RunTestInstance.AnonymousMetho d
() Line 231     C#
...

read more »


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google