As evidenced by recent changes and failed attempts to fix in PR #3873 and #3890 , we have had cases where things will pass locally but fail up there.
It is clear that the AV is a canary in the coal mine. At the present when a build error, we only have most brief and generic error output to the console.
We should consider making a global handler so that whenever a test fails, more data is written out t the console using TestContext.Out object to provide the sufficient context and thus help simplify troubleshooting.
Note to myself -- create a new unit test for CreateObject in light of changes to the PR #3890 which we modified to avoid AV failing as we need to ensure that AV tests the same way we test.
As evidenced by recent changes and failed attempts to fix in PR #3873 and #3890 , we have had cases where things will pass locally but fail up there.
It is clear that the AV is a canary in the coal mine. At the present when a build error, we only have most brief and generic error output to the console.
We should consider making a global handler so that whenever a test fails, more data is written out t the console using
TestContext.Out
object to provide the sufficient context and thus help simplify troubleshooting.