Add Escape Valve for check test results the old way#2992
Add Escape Valve for check test results the old way#2992alexperovich merged 4 commits intodotnet:masterfrom
Conversation
tests/UnitTests.proj
Outdated
| <ItemGroup> | ||
| <AzurePipelinesExpectedTestFailure Include="PizzaTests.cheese"/> | ||
| <AzurePipelinesExpectedTestFailure Include="PizzaTests.cheese2"/> | ||
| <!-- <AzurePipelinesExpectedTestFailure Include="PizzaTests.cheese"/> |
There was a problem hiding this comment.
Yea, I am gona revert this commit once I verify the change. This is to verify the thing I wrote will work in azdev.
|
@BruceForstall @echesakovMSFT |
This reverts commit 21d6295.
|
I'm not extremely familiar with this issue, but, after talking to @BruceForstall and @echesakovMSFT, this new behavior of Azure Pipelines sounds broken. Are we tracking getting the AzP team to fix it? |
|
I have a conversation ongoing with them. The problem is the api they pointed me too isn't run specific. If there isn't a run specific api then we will have to explore other options. |
|
@alexperovich I don't know much about the apis AzDO has but I am wondering whether it is possible to use the two apis:
|
|
The new api is nothing more than the counts of test results per status. There isn't any documentation for it either so I don't know if there are other apis in the same set that I can use to get results for specific runs. |
Fix bug where the first failure causes all other tests to fail. See dotnet/arcade#2992
Fix bug where the first failure causes all other tests to fail. See dotnet/arcade#2992
Fix bug where the first failure causes all other tests to fail. See dotnet/arcade#2992
Fix bug where the first failure causes all other tests to fail. See dotnet/arcade#2992
@RussKeldorph this will enable the old way to check results as an opt-in.