Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
This one is a higher priority for us here in QA, it's causing all of the indie/starter pricing restriction tests to fail with no output.
this is a known issue in mdtool whereby it does not print out build errors which are generated as part of the internal build process. It only prints out build errors coming from mcs/gmcs.
The error code for the process will still indicate failure so it will still be possible to automate tests to ensure building fails.
Hrm.. it would be good to get the right error codes here, the tests are supposed to check for the correct XX900X code being thrown for various pricing restrictions.
Right now the exit code is just 1 :-/.
I'll mark it as an enhancement for QA needs. If you can find the original mark it as a duplicate perhaps?
Fixed, we now always write all the build errors to stderr.