Bug 56308 - CodeSharingLLVM tests failing with 2017-04
Summary: CodeSharingLLVM tests failing with 2017-04
Status: RESOLVED DUPLICATE of bug 56307
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: XI 10.12 (d15-3)
Hardware: PC Mac OS
: Normal normal
Target Milestone: 15.3
Assignee: Rolf Bjarne Kvinge [MSFT]
URL:
Depends on:
Blocks:
 
Reported: 2017-05-12 17:43 UTC by Andi McClure
Modified: 2017-05-17 10:19 UTC (History)
3 users (show)

Tags: 2017-04
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED DUPLICATE of bug 56307

Description Andi McClure 2017-05-12 17:43:04 UTC
On our PR to bump macios mono to 2017-04

https://github.com/xamarin/xamarin-macios/pull/1960#issuecomment-300890969

We upgraded the mono from 2017-04 commit 197c23 to 4960d5. Six tests are now failing on Jenkins:

https://jenkins.mono-project.com/job/xamarin-macios-pr-builder/3706/

Four of these tests are under the CodeSharingLLVM group. The failure, which I do not understand, is

https://jenkins.mono-project.com/job/xamarin-macios-pr-builder/3706/testReport/junit/Xamarin/MTouch/CodeSharingLLVM__code_sharing_32_bit___armv7_llvm__System_String___/
      MESSAGE:
                                                  We build at least 4, so we must have had at least 4 asserts above.
  Expected: greater than or equal to 4
  But was:  3

Although this problem seems to have been triggered by a change to the runtime, I do not believe the runtime team is in an adequate place to diagnose the problem. I do not know what the intent of this test is.

I am able to reproduce the problem on a local machine with a build of macios 60485cfd2c. I modified the test to print every line of build output. The log is attached as LINELOG.txt
Comment 1 Rolf Bjarne Kvinge [MSFT] 2017-05-17 10:19:20 UTC
This has the same underlying cause as bug #56307.

*** This bug has been marked as a duplicate of bug 56307 ***