Closed acv111 closed 1 year ago
Sorry for the delayed response. Have you looked at the specific run id when the issue occurs? The behavior you describe could be caused by a failure that returns a stack that the client can't deserialize. The next release will contain a fix for this. To get further details on the issue, you can enable debugging (--debug flag).
Closing the issue for lack of response and repro details.
While running a build in Azure DevOps, nutter is occassionally returning a result of: "No test cases were returned." and a lengthy encrypted string as the notebook output. This generally can be resolved by rerunning the build, and seems to be inconsistent in its behavior. The notebook output in the build step is similar to the output if you execute a test locally without commenting out result.exit(dbutils), except it is roughly 5x the length.
I can not consistently reproduce this behavior, and cannot reproduce when running the test notebook locally. When running locally, the test cases within the notbook succeed without issue.