** Changed in: nunit-3.0
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/904841
Title:
After exiting for timeout the teardown method is not executed
** Changed in: nunitv2
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of NUnit
Core Developers, which is the registrant for NUnit Framework.
https://bugs.launchpad.net/bugs/904841
Title:
After exiting for timeout the teardown method
** Branch linked: lp:nunit-3.0
--
You received this bug notification because you are a member of NUnit
Core Developers, which is the registrant for NUnit Framework.
https://bugs.launchpad.net/bugs/904841
Title:
After exiting for timeout the teardown method is not executed
Status in NUnit Test
** Changed in: nunit-3.0
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of NUnit
Core Developers, which is the registrant for NUnit Framework.
https://bugs.launchpad.net/bugs/904841
Title:
After exiting for timeout the teardown method is
** Also affects: nunit-3.0
Importance: Undecided
Status: New
** Changed in: nunit-3.0
Status: New => Triaged
** Changed in: nunit-3.0
Importance: Undecided => High
** Changed in: nunit-3.0
Assignee: (unassigned) => Charlie Poole (charlie.poole)
** Changed in: nunit-3.0
This turned out to be a race condition between the main test thread and
the individual test case thread. In some cases the teardown was run, in
others not at all and in still others teardown could start and then be
interupted. Inserting a Join in the logic that cancels the thread causes
it to work
I'm reactivating this. On rerunning the test I see that the problem does
in fact exist.
** Changed in: nunitv2
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/
I have verified that teardown is executed after a timeout. There was no
test for this case, so I added one.
If your own teardown is not being executed at all, it may be that the
setup is hanging and causing the timeout. If setup does not complete,
then teardown is not run.
** Changed in: nunitv2
** Branch linked: lp:nunitv2
--
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/904841
Title:
After exiting for timeout the teardown method is not executed
Status in NUnit V2 Test Framework:
Ne
9 matches
Mail list logo
