Comment 27 for bug 582051

Revision history for this message
Rami Abughazaleh (rami-abughazaleh) wrote :

I am experiencing this issue with NUnit v2.5.9.10348.

Windows Server 2008 R2 Enterprise (64-bit)

C:\nunit\net-2.0\nunit-console-x86.exe c:\unittests\MyTest\MyTest.nunit /config=my-config-test /framework=4.0 /run=MyTest.Tests.Test /noshadow /xml:c:\unittests\MyTest.xml
NUnit version 2.5.9.10348
Copyright (C) 2002-2009 Charlie Poole.
Copyright (C) 2002-2004 James W. Newkirk, Michael C. Two, Alexei A. Vorontsov.
Copyright (C) 2000-2002 Philip Craig.
All Rights Reserved.

Runtime Environment -
   OS Version: Microsoft Windows NT 6.1.7600.0
  CLR Version: 2.0.50727.4927 ( Net 2.0 )

ProcessModel: Default DomainUsage: Default
Execution Runtime: v4.0
Unable to locate fixture

However, if I immediately run it again, it works as expected.

I have this consistently reproducible from a vmware snapshot.

The vmware snapshot has the following components installed\settings configured in order:
.net 3.5.1
sql server 2008 r2 express with management studio
.net 4.0 full
logged in as a domain user
iis
disabled uac
enabled interactive service detection service

But I'm not sure if all of them are relevant.

Is there anything else I can do to produce a more verbose output\log for diagnostics?

Should I create a new bug or should this one be re-opened?

Thank you.