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.
* Run "make run-watchos-dev-mini CONFIG=Release" in xamarin-macios/tests
> [FAIL] JitTests.Exceptions : System.Reflection.TargetInvocationException : Exception has been thrown by the target of an invocation.
> ----> System.ExecutionEngineException : Attempting to JIT compile method 'ExceptionTests:test_1_basic_filter_catch ()' while running in aot-only mode. See https://developer.xamarin.com/guides/ios/advanced_topics/limitations/ for more information.
Full log: https://gist.github.com/rolfbjarne/bb7cff9eaf77e1e1acba2caa8f05e741
Built log: https://gist.github.com/rolfbjarne/3b3e71a3a5c6f274d191c59d45015422
This might be relevant:
> LLVM failed for 'test_1_basic_filter_catch': non-finally/catch/fault clause.
> LLVM failed for 'test_1234_complicated_filter_catch': non-finally/catch/fault clause.
> LLVM failed for 'test_0_filter_caller_area': non-finally/catch/fault clause.
It only happens in release builds, and only on watchOS.
An alternative repro would be to open the solution "tests/mini/mini-watchos.sln" and run the Release|Device configuration of the "mini-watchos-app" project.
This fails in 15.5 as well as master.
Probably fixed by mono 43957a4dd74d3fabe6c24edc50aa5dd16fa3fbaa.
It fails in 15.4 and 15.3 as well, and in 15.2 this particular test didn't exist, so it's not a regression.
@Zoltan, OK, I'll add that to the list of categories we exclude when running tests.
The fix will only be complete once we bump to mono 2017-08.
Keeping open for verification until we bump to mono 2017-08.
Confirmed to be fixed in master.