Bug 59953 - [llvm][bitcode] test_0_float_return_spill failed: got 1, expected 0
Summary: [llvm][bitcode] test_0_float_return_spill failed: got 1, expected 0
Status: CONFIRMED
Alias: None
Product: iOS
Classification: Xamarin
Component: Mono runtime / AOT compiler (show other bugs)
Version: master
Hardware: PC Mac OS
: --- normal
Target Milestone: Future Cycle (TBD)
Assignee: Zoltan Varga
URL:
Depends on:
Blocks:
 
Reported: 2017-10-04 11:52 UTC by Rolf Bjarne Kvinge [MSFT]
Modified: 2017-11-23 16:42 UTC (History)
4 users (show)

See Also:
Tags:
Is this bug a regression?: No
Last known good build:


Attachments

Description Rolf Bjarne Kvinge [MSFT] 2017-10-04 11:52:36 UTC
Repro:

* Run "make run-watchos-dev-mini CONFIG=Release" in xamarin-macios/tests

Result:

> test_0_float_return_spill failed: got 1, expected 0
> ...
> 	[FAIL] JitTests.Objects :   Expected: 0

Full log: https://gist.github.com/rolfbjarne/bb7cff9eaf77e1e1acba2caa8f05e741
Built log: https://gist.github.com/rolfbjarne/3b3e71a3a5c6f274d191c59d45015422

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.
Comment 1 Rolf Bjarne Kvinge [MSFT] 2017-10-04 11:53:20 UTC
I've tested master, d15-5, d15-4 and d15-3, and it fails everywhere, so if it's a regression, it's not a recent one.
Comment 2 Rolf Bjarne Kvinge [MSFT] 2017-11-22 12:01:13 UTC
PR to ignore this test to make the test run green:

    mono/master: https://github.com/mono/mono/pull/6073
    mono/2017-10: https://github.com/mono/mono/pull/6074

This will not fix this bug, only make the tests green until the bug is fixed.
Comment 3 Rolf Bjarne Kvinge [MSFT] 2017-11-23 16:42:59 UTC
The latest mono bump (https://github.com/xamarin/xamarin-macios/pull/3030) brought the commit that ignores this test, so this failure should not occur anymore.

This also means that to reproduce the issue, the test first has to be unignored.

Note You need to log in before you can comment on or make changes to this bug.