-
Notifications
You must be signed in to change notification settings - Fork 554
Bump to mono:2019-08 #6723
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump to mono:2019-08 #6723
Conversation
This comment has been minimized.
This comment has been minimized.
|
This is my first iOS rodeo, and I have no idea how to get started from here. |
This comment has been minimized.
This comment has been minimized.
|
The build failed:
We're using a Mono.Cecil.dll from the mono archive, so that probably has to be updated. |
|
Yeah, I need to update the Mono in the PR to one with the new Cecil, but I don't want to waste time doing that if I'm about to merge an important PR I need to point to |
|
PROGRESS. We have:
|
|
Regarding the mono_fconv_u8 issue that sounds like it was introduced by @filipnavara's recent PR: mono/mono#15930 Probably missing |
|
To what extent is 32-bit iOS (i.e. devices considered out of support & unserviceable by Apple as of 2 years ago) still a target? |
|
I know the iPhone 5C is 32-bit, but isn't some of the Apple watches also 32-bit @rolfbjarne / @spouliot ? |
|
WatchOS is a different thing to iOS isn't it? |
|
@directhex developers still target iOS 32 bits devices - it's fully supported on the app store (and it's even hard to remove architectures from apps until Apple removes them from the store). |
|
Huh. TIL. |
|
@directhex we are not to worry, I noticed that some tests are allocating TOO much memory on an iOS 32 device. I reported that to mono already and did a cherry-pick of a fix we have in master. We should be ok. This is not the first time that corefx has tests that are memory hungry and cannot be ran on a 32b devices (some File.IO tests were moving gbs from one side to another). Mono should either fix the tests or add them to the categories that are ignored in mobile. I'm surprised that android did not run on this (unless they do not have 32b devices). |
|
❌ Build was (probably) aborted 🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Test run, Test run' 🔥 ✅ Build succeeded Test results3 tests failed, 168 tests passed.Failed tests
|
|
Since they are now largely fixed I'll be running the submission tests with the |
|
Build failure Test results3 tests failed, 877 tests' device not found, 167 tests passed.Failed tests
|
|
Submission tests results (and emails to |
|
@mandel-macaque looks like that latest change caused a conflict |
|
@directhex fixed ;) |
|
Build failure ✅ Build succeeded |
|
❌ Build was (probably) aborted 🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Test run' 🔥 : org.jenkinsci.plugins.workflow.steps.FlowInterruptedException ✅ Build succeeded |
|
Build failure Test results5 tests failed, 877 tests' device not found, 165 tests passed.Failed tests
|
|
❌ Build was (probably) aborted 🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Test run, Test run' 🔥 ✅ Build succeeded Test results3 tests failed, 168 tests passed.Failed tests
|
|
@spouliot @directhex looking at https://jenkins.mono-project.com/job/xamarin-macios-pr-builder/11194/Test_20Report/ the 32b issues are solved. I'll investigate why the internal build gave an error. |
|
❌ Build was (probably) aborted 🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Test run, Test run' 🔥 ✅ Build succeeded Test results4 tests failed, 167 tests passed.Failed tests
|
|
Build failure Test results2 tests failed, 877 tests' device not found, 168 tests passed.Failed tests
|
|
MMP tests are expected to fail. Rest are HE003 or a flaky test related to sockets. We are good to go. |
No description provided.