Jakub Jareš
Jakub Jareš
This is now on list of work for msbuild team, and me to fix. We still don't know where it is happening though. So if you have any additional info,...
Looks to be connected to capturing process output: This change adds an option to fully disable capturing standard output. Setting it unblocked my run: https://github.com/microsoft/vstest/pull/4998 `VSTEST_DISABLE_STANDARD_OUTPUT_CAPTURING=1` env variable BUT we've...
Actually no matter what I do I cannot repro the hang when running on 9.0.100, so I am not sure if the option above did anything.
OP confirmed this is working for them now. @Sebazzz do you have a repro of your problem please? If it still does repro, please start a new issue.
Yeah I guess figuring out the most intuitive way to represent null is the hardest thing here. It should also survive easily being provided on command line to a child...
Our proposal here is to simply leave the value empty, such as `testcategory=` This has some edge cases regarding quotes and spaces. ## for `--filter` The current implementation already seems...
Adding to 3.10 to keep it on our radar, but design needs to be fiinalized first.
Yeah that is one disadvantage, I agree. Advantage of just = is that it is literally no value, so there is no chance that this conflicts with existing user identifiers,...
Probably the most reasonable thing would be to make it `None`, and warn / fail on tests that use that category / property / whatever else? After all the main...
^^^ @Youssef1313 @Evangelink any opinions on simply using `None`?