-
Notifications
You must be signed in to change notification settings - Fork 282
Write warnings outside of appdomain #5371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
src/Adapter/MSTest.TestAdapter/Discovery/AssemblyEnumeratorWrapper.cs
Outdated
Show resolved
Hide resolved
I am finally happy with the test, I had to change how project assets are emitted, to put them to the same folder (but different subfolders, like if we had a solution). I don't expect anything to break because 90% of the fixture usages are for 1 project only, and where 2 projects are used, they don't reference each other, because it was not possible till now (they emit to different temp directories). But let's see what breaks. Maybe I will need to go back to writing the code files to disk first, and then building, instead of doing all that in parallel right now. |
test/IntegrationTests/MSTest.Acceptance.IntegrationTests/ThreadingTests.cs
Show resolved
Hide resolved
I've re-run it on the merge, and not here. AAARGh! |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Related #5176
Figuring out a reliable way to test this, will follow up with other PR. Ensured manually that it works.