{"action":"opened","issue":{"url":"https://api.github.com/repos/techtalk/SpecFlow/issues/1115","repository_url":"https://api.github.com/repos/techtalk/SpecFlow","labels_url":"https://api.github.com/repos/techtalk/SpecFlow/issues/1115/labels{/name}","comments_url":"https://api.github.com/repos/techtalk/SpecFlow/issues/1115/comments","events_url":"https://api.github.com/repos/techtalk/SpecFlow/issues/1115/events","html_url":"https://github.com/techtalk/SpecFlow/issues/1115","id":315637380,"number":1115,"title":"Getting apparent concurrency issue after upgrading from SpecFlow 1.9 MsTest v1 to SpecFlow 2.3.2 MsTest v2","user":{"login":"renatoch","id":6089803,"avatar_url":"https://avatars0.githubusercontent.com/u/6089803?v=4","gravatar_id":"","url":"https://api.github.com/users/renatoch","html_url":"https://github.com/renatoch","followers_url":"https://api.github.com/users/renatoch/followers","following_url":"https://api.github.com/users/renatoch/following{/other_user}","gists_url":"https://api.github.com/users/renatoch/gists{/gist_id}","starred_url":"https://api.github.com/users/renatoch/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/renatoch/subscriptions","organizations_url":"https://api.github.com/users/renatoch/orgs","repos_url":"https://api.github.com/users/renatoch/repos","events_url":"https://api.github.com/users/renatoch/events{/privacy}","received_events_url":"https://api.github.com/users/renatoch/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-04-18T20:50:08Z","updated_at":"2018-04-18T20:50:08Z","closed_at":null,"author_association":"NONE","body":"<!-- PLEASE CHECK THE OPTIONS THAT APPLY TO YOU BY ADDING AN 'x' TO THE CORRESPONDING CHECKBOX ('[ ]') -->\r\n### SpecFlow Version:\r\n- [X] 2.3\r\n- [ ]\t2.2\r\n- [ ]\t2.1\r\n- [ ]\t2.0\r\n- [ ]\t1.9\r\n \r\n### Used Test Runner \r\n- [ ] SpecFlow+Runner\r\n- [X]\tMSTest \r\n- [ ]\tNUnit\r\n- [ ]\tXunit\r\n\r\n<!-- PLEASE INCLUDE THE VERSION NUMBER OF YOUR TEST RUNNER -->\r\nVersion number: 15.6.1\r\n\r\n### Visual Studio Version\r\n- [ ]\tVS 2017\r\n- [X]\tVS 2015\r\n- [ ]\tVS 2013\r\n\r\n### Are the latest Visual Studio updates installed?\r\n- [X]\tYes\r\n- [ ]\tNo\r\n \r\n### .NET Framework:\r\n- [X]\t>= .NET 4\r\n- [ ]\tbefore .NET 4\r\n\r\n### Test Execution Method:\r\n- [ ]\tVisual Studio Test Explorer\r\n- [ ]\tTFS/VSTS – Task – PLEASE SPECIFY THE NAME OF THE TASK\r\n- [X]\tCommand line – PLEASE SPECIFY THE FULL COMMAND LINE\r\n \r\n```\r\n\"C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Enterprise\\Common7\\IDE\\CommonExtensions\\Microsoft\\TestWindow\\vstest.console.exe\" \"TestFile.dll\" /TestCaseFilter:\"TestCategory=PreCondition\" /InIsolation /UseVsixExtensions:false /Logger:trx\r\n```\r\n\r\n### &lt;SpecFlow> Section in app.config\r\n<!-- PLEASE COPY THE ENTRIE <SpecFlow> SECTION IN YOUR .config FILE AND PASTE IT BETWEEN THE TWO CODE MARKERS (```) BELOW -->\r\n```\r\n  <specFlow>\r\n    <unitTestProvider name=\"MsTest\" />\r\n    <runtime missingOrPendingStepsOutcome=\"Error\" />\r\n    <trace traceSuccessfulSteps=\"false\" />\r\n  </specFlow>\r\n```\r\n\r\n### Repro Project\r\n<!-- PLEASE INCLUDE A LINK TO A PROJECT THAT DEMONSTRATES THE ISSUE YOU ARE REPORTING, IF POSSIBLE \r\nFor information on how to include a useful repro, refer to https://stackoverflow.com/help/mcve\r\n-->\r\n\r\n### Issue Description\r\nI have some tests that copies a file to a temp directory, overwriting it if already present. I'm not using parallel execution of tests.\r\n\r\nI had no issues for years with this approach, however after upgrading SpecFlow and MsTest (not sure if correlation or cause), I started getting intermittent error:\r\n\r\n> System.IO.IOException: The process cannot access the file 'C:\\temp\\file_test101.pdf' because it is being used by another process.\r\n\r\nSome additional info:\r\n\r\n - I've restarted the computer and ran tests, and still getting the error. \r\n - Each test uses a different file related to its name, so no possibility of interference between tests\r\n - No other test runners were running while the test ran and I got error.\r\n - The test never opens the file for writing, so I don't see a chance of file handle being left open\r\n - I've logged the locks on the file when the error happens, and the process locking it is the same running the tests, same PID.\r\n\r\nAny ideas on how to troubleshoot this issue further, or on what might be causing the issue?\r\n\r\nI'm suspecting some issue with the implementation of parallel execution in SpecFlow/MsTest might be interfering, even though I'm not using parallel execution.\r\n\r\nObs: Opened [StackOverflow question](https://stackoverflow.com/questions/49908739/getting-apparent-concurrency-issue-after-upgrading-from-specflow-1-9-mstest-v1-t)\r\n\r\n### Steps to Reproduce\r\n<!-- PLEASE DESCRIBE THE STEPS REQUIRED TO REPRODUCE THIS ISSUE, IF POSSIBLE -->\r\n"}}
{"actor":{"display_login":"renatoch"}}