Closed mfenniak closed 11 years ago
Okay, we're green again. We were running under Mono 3.0.1. I bumped us up to 3.2.3. For future reference, just change the version under Build Parameters in the configuration. On the agent, I use mope to allow projects to target different versions of Mono on the same agent. All a project has to do is set an environment variable in their build.
Thanks @dragan. I wasn't aware of the option to change the Mono version on the build configuration, but I'll check that out if we run into Mono bugs again.
@mfenniak No worries, I need to write a blog post on how to use mope for those using the CodeBetter TeamCity service, so it's my fault, because it's not documented.
Looks like one of the recent commits began to trigger this Mono bug: https://bugzilla.xamarin.com/show_bug.cgi?id=12786 on the TeamCity build, causing the continuous integration build to crash after it has successfully completed the unit tests.
Looks like the bug is fixed in mono 3.1.1 and higher.