{"action":"created","issue":{"url":"https://api.github.com/repos/nunit/nunit/issues/2632","repository_url":"https://api.github.com/repos/nunit/nunit","labels_url":"https://api.github.com/repos/nunit/nunit/issues/2632/labels{/name}","comments_url":"https://api.github.com/repos/nunit/nunit/issues/2632/comments","events_url":"https://api.github.com/repos/nunit/nunit/issues/2632/events","html_url":"https://github.com/nunit/nunit/issues/2632","id":283261847,"number":2632,"title":"Parallel tests are loading 100% CPU when nested SetUpFixture exists","user":{"login":"undron","id":1076685,"avatar_url":"https://avatars2.githubusercontent.com/u/1076685?v=4","gravatar_id":"","url":"https://api.github.com/users/undron","html_url":"https://github.com/undron","followers_url":"https://api.github.com/users/undron/followers","following_url":"https://api.github.com/users/undron/following{/other_user}","gists_url":"https://api.github.com/users/undron/gists{/gist_id}","starred_url":"https://api.github.com/users/undron/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/undron/subscriptions","organizations_url":"https://api.github.com/users/undron/orgs","repos_url":"https://api.github.com/users/undron/repos","events_url":"https://api.github.com/users/undron/events{/privacy}","received_events_url":"https://api.github.com/users/undron/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2017-12-19T15:03:55Z","updated_at":"2017-12-21T18:55:54Z","closed_at":null,"author_association":"NONE","body":"Using 3.9.0.0 NUnit framework and adapter,  I have similar to https://github.com/nunit/nunit/issues/2507 issue.\r\n\r\nWe have [SetUpFixture] class in root namespace and [SetUpFixture] class in nested namespace.\r\n\r\nPlease refer code in https://github.com/undron/NUnitHangsAtNestedSetUpFixture\r\nWhen tests from namespace NUnitParallels.Some is running it is 100% CPU utilization:\r\n![image](https://user-images.githubusercontent.com/1076685/34163099-da1e98e6-e4e6-11e7-82cb-ff77df9f36bd.png)\r\n"},"comment":{"url":"https://api.github.com/repos/nunit/nunit/issues/comments/353429052","html_url":"https://github.com/nunit/nunit/issues/2632#issuecomment-353429052","issue_url":"https://api.github.com/repos/nunit/nunit/issues/2632","id":353429052,"user":{"login":"CharliePoole","id":2678661,"avatar_url":"https://avatars2.githubusercontent.com/u/2678661?v=4","gravatar_id":"","url":"https://api.github.com/users/CharliePoole","html_url":"https://github.com/CharliePoole","followers_url":"https://api.github.com/users/CharliePoole/followers","following_url":"https://api.github.com/users/CharliePoole/following{/other_user}","gists_url":"https://api.github.com/users/CharliePoole/gists{/gist_id}","starred_url":"https://api.github.com/users/CharliePoole/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/CharliePoole/subscriptions","organizations_url":"https://api.github.com/users/CharliePoole/orgs","repos_url":"https://api.github.com/users/CharliePoole/repos","events_url":"https://api.github.com/users/CharliePoole/events{/privacy}","received_events_url":"https://api.github.com/users/CharliePoole/received_events","type":"User","site_admin":false},"created_at":"2017-12-21T18:55:54Z","updated_at":"2017-12-21T18:55:54Z","author_association":"OWNER","body":"Very interesting! I commented out all the first-level tests (those in NUnitParallels namespace) but left in the nested SetUpFixtures. Problem disappears!\r\n\r\nWe know from the trace that the top-level fixtures get enqueued before the second-level fixtures execute. My working theory is that busy-waiting by the workers is using up the CPU cycles. I'll need to try this out with a debug build of the framework."}}
{"actor":{"display_login":"CharliePoole"}}