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.
instead of Debug (or both) as most IL tests will behave quite differently.
Note: Most linker .csproj files have wrong Release configuration as well (disabled Optimize)
I'm not sure I understand your request.
You're talking about the linker tests right so "link all", "link sdk"?
You can run those in release mode with the test solution though.
So are you talking about running them in release mode on wrench/jenkins?
Yes, I am talking about running right configuration on Jenkins/Wrench
Ok seems legit, marking this bug as confirmed.
Let's make the linker tests run in release mode on the bots.
@sebastien any thoughts on that?
The linker tests builds on release on the bots with devices since some of the optimizations can only be verified while running on device.
We might revisit that soon it's now cheaper (tests builds/execute in parallel) and we're both updating the optimizations and the bot setup (for device testing), c.c. Rolf
Running linker tests in both debug & release for the simulator should be trivial to implement now, I'll have a look.