Devops pipelines are failing due to an unhandled return code coming back from pytest

[scbedd]

The difficulty here, is why. Pull request 4255 is hitting this issue, but I believe that master should see it tonight 2/6 as well.

I have established the following facts.

The unhandled return code is coming because azure-cognitiveservices-vision-face\tests\test_face.py is not being discovered by pytest. If there are no tests run for a discovered folder, pytest exits with return code 5. Since this is a non-zero return code, our current test infrastructure treats that as a CallExceptionError and dies.

There have been no config changes that I can tell between the latest passing commit SHA a3ce7df21dfc4c7cd37af14e790ea7c25c463ce2 and latest master.

• https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4048 is the latest scheduled build. It passed last night.
• The PR associated with the failing build has no changes to any test infrastructure
• Between the latest successful build SHA and master now, the only change is a new Kusto package added.

After 5PM, both the manually queued build and the local build stopped repro-ing the issue. However, after an additional full build was queued, I saw the error again.

I can fix the unhandled return code, but before I do that, I want to understand why the test case isn't being discovered. If this takes more than a day or so to resolve, I will submit a PR that fixes the build failure. Note that we'll still have the problem of a test simply not running.

[scbedd]

@johanste started reproing again. Wiill have a fix 2/7.