nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

This could be related to the problem identified by bug #993247 - If you
build from source, you'll have the fix now, otherwise let's wait for the
first release of 2.6.1 to see if it helps. I haven't replicated it in my
environment.

** Changed in: nunitv2
       Status: New => In Progress

** Changed in: nunitv2
   Importance: Undecided => High

** Changed in: nunitv2
     Assignee: (unassigned) => Charlie Poole (charlie.poole)

** Changed in: nunitv2
    Milestone: None => 2.6.1

** Changed in: nunitv2
       Status: In Progress => Incomplete

-- 
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/985861

Title:
  Test assemblies are locked

Status in NUnit V2 Test Framework:
  Incomplete

Bug description:
  NUnit GUI 2.6.0.12051
  FW 4.0

  After a test run, the test assemblies are locked by NUnit process
  though "Enable Shadow Copy" option is on.

  I was experiencing this issue in both of the following cases:
    (a) FW runtime 4.0 is forced in NUnit config file and test assemblies are for FW 4.0
    (b) default runtime settings are used and test assemblies are for FW 4.0

  I ran Sysinternals' ProcessExplorer and ensured that NUnit process was
  holding a handle to the referenced test assembly (not a shadow copy
  instance).

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunitv2/+bug/985861/+subscriptions