Menu
I have a build pipeline which runs unit tests (nunit) using a local agent.
Everything worked OK until I moved to a new laptop. Without any changes to my repository or build settings, the logs of builds generated now are now full of these messages:
2019-02-06T10:21:22.7514187Z [11:21:22] Exception: E0434352.CLR
There are over 7000 messages for less than 100 unit tests. Some of the tests are UI tests (with TestStack.White) and some are web tests (with Selenium).
The errors don't seem to affect the test execution, because tests are passing OK (or failing appropriately if there are issues).
The only thing that has changed is a newer version of Windows 10 build and potentially a newer version of the build agent which I had to re-download.
How can I debug that, because the error does not say anything?
Can it be related to the version of the build agent?
Does the build agent executable updates itself?
In attempt to get rid of the error I have updated the agent from v144 to v146, but no change (64bit, as my Windows)
773
A CLR Exception is a type of Exception made by . NET applications. The exception is encapsulated in a class derived from the System. Exception class. The Exception Code is 0xE0434352 (a.k.a. Error "CCR" in ASCII).
Get logs to diagnose problems Start by looking at the logs in your completed build or release. You can view logs by navigating to the pipeline run summary and selecting the job and task. If a certain task is failing, check the logs for that task.
Uncheck the "Collect advanced diagnostics in case of catastrophic failures" under the test task.
There's no need to disable the test rerun!
(This is as per @GregM's answer, however I couldn't edit his post to make this stand out a bit more in his text)
68
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
