How to fix Mono errors during Travis CI build?

[mbernier]

Issue Summary

We are seeing

The command "mono ./testrunner/NUnit.Runners.2.6.4/tools/nunit-console.exe UnitTest/bin/Release/UnitTest.dll -domain:None" exited with 3.

On every build. Can you help with this?

[phongphan]

It's likely a bug in corefx #59302

[mbernier]

@phongphan I noticed that the same error happened after a huge stack trace, after #56 #57 failures. I am wondering if there is something wrong with the way that the unittests are asserting issues and reporting them out to the log? or is mono failing totally normal when a unittest doesn't pass?

Here's where I saw those issues: https://travis-ci.org/sendgrid/csharp-http-client/builds/294260033?utm_source=github_status&utm_medium=notification

[mbernier]

@adlan are the csharp unittest errors always so verbose / disorganized? I noticed the same error and stacktracing was happening here (the build from #53)

[phongphan]

Even if I commented out the test in #53. Both of them are still failing under mono. Not sure what exactly triggered the failure though.

[adlan]

@mbernier, uncaught exceptions will be displayed verbosely. In this case those exceptions are not what the unittest runner expected.

For the remaining exceptions, I can only guess (based on the commit log) that the cause of failing has todo with the test environment and is likely as what @phongphan mentioned earlier. I've yet to dig those errors deeply though.