I'd love to hear about other options. Can you suggest something better?

On 21/05/2010, at 11:59, Graham Hay wrote:

You'd need to use userdump, or I think in the newer versions of Windows you can force a dump from the task manager. Do you really need the runner/host to be alive all that time? Wouldn't it make more sense to have something else orchestrating?

On 20 May 2010 18:58, Mark Kharitonov <[email protected]> wrote: Our QA stopped using Icarus for these long runs, in case they do it again can you provide the way to run it so that a dump is created?

That is the point, we are not sure where is the problem - in the runner or in the Host.

The test runs for a long time, because it performs scenario based testing of a distributed product, involving the client (i.e. the unit test), the server and multiple agents. The duration of a test is determined by the specific scenario. First we tried short runs, now we are trying longer runs to see that all the agents work well with the server. The client does nothing while the agents are working and reporting stuff to the server. When a certain timeout expires (a few days or even weeks) the client may need to instruct the agents to stop. Or it can start new runs, or it can cause an agent to fall, testing failure recovery. In short, it is very useful to be able to run long tests.



On 19/05/2010, at 13:40, Graham Hay wrote:

Icarus was never really intended for that purpose. On the other hand, I'm sure improvements could be made. Could you provide a dump file from one of the crashes? Echo should be better (I've never tried it), unless it's the Host process that's getting too big. Why do you need to have tests running that long?

On 17 May 2010 13:10, Mark Kharitonov <[email protected]> wrote:
Hi.
We developed a framework on top of Gallio MbUnit to run scenario based
tests. Right now our QA team has problems leaving Gallio.Icarus open
for a long time - they claim it takes too much CPU and memory and
eventually crashes.

My question is whether using Gallio.Echo will solve this problem of
high resource utilization and eventual crashes? Or is there another
way to run long tests. By long I mean days and even weeks.

BTW, I am not sure whether the problem is in the runner or in the host process - Gallio.Host. My hope is that someone has already encountered these issues and can spare me the time of checking all of this myself.

Thanks.

--
You received this message because you are subscribed to the Google Groups "MbUnit.User" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to mbunituser [email protected]. For more options, visit this group at http://groups.google.com/ group/mbunituser?hl=en.



--
You received this message because you are subscribed to the Google Groups "MbUnit.User" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to mbunituser [email protected]. For more options, visit this group at http://groups.google.com/ group/mbunituser?hl=en.

====================================================================== ==== There are two kinds of people. Those whose guns are loaded and those who dig.
                                                                                
                                (The good, the bad and the ugly).
So let us raise our cups for our guns always be loaded.



--
You received this message because you are subscribed to the Google Groups "MbUnit.User" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to mbunituser [email protected]. For more options, visit this group at http://groups.google.com/ group/mbunituser?hl=en.


--
You received this message because you are subscribed to the Google Groups "MbUnit.User" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to mbunituser [email protected]. For more options, visit this group at http://groups.google.com/ group/mbunituser?hl=en.

======================================================================== == There are two kinds of people. Those whose guns are loaded and those who dig.
                                                                                
                                (The good, the bad and the ugly).
So let us raise our cups for our guns always be loaded.


--
You received this message because you are subscribed to the Google Groups 
"MbUnit.User" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/mbunituser?hl=en.

Reply via email to