-
Notifications
You must be signed in to change notification settings - Fork 513
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:2018-06 #4277
Bump to mono:2018-06 #4277
Conversation
Build failure
|
PR failed while building mono
|
Build failure 🔥 Build failed 🔥 |
Build failure 🔥 Build failed 🔥 |
Build failure |
Build failure ✅ Build succeeded |
Build failure ✅ Build succeeded |
Build failure ✅ Build succeeded |
Build failure ✅ Build succeeded |
Build success Test results# Test run in progress: InProgress, Waiting: 1, Building: 4, BuildQueued: 85, Built: 62, RunQueued: 50, Succeeded: 22, Failed: 1, Ignored: 1124Failed tests
|
✅ Jenkins job (on internal Jenkins) succeeded ✅ Build succeeded |
* [mtouch] add --interp-mixed option When enabling this option, mtouch will AOT compile `mscorlib.dll`. At runtime that means every method that wasn't AOT'd will be executed by the runtime interpreter. * [mtouch] Add support to --interpreter to list the assemblies to (not) interpret. * [msbuild] Simplify interpreter code to use a single variable. * Fix whitespace. * [mtouch] Move mtouch-specific code to mtouch-specific file. * [msbuild] An empty string is a valid value for 'Interpreter', so make it a non-required property. * [mtouch] Add sanity check for aot-compiling interpreted assemblies.
✅ Jenkins job (on internal Jenkins) succeeded ✅ Build succeeded |
Build success |
…framework list The collision resolver task reads them from here https://github.com/dotnet/sdk/blob/master/src/Tasks/Common/ConflictResolution/FrameworkListReader.cs
✅ Jenkins job (on internal Jenkins) succeeded ✅ Build succeeded |
Build failure Test results2 tests failed, 0 tests skipped, 223 tests passed.Failed tests
|
@spouliot could we get this in now when you have separate 15.9 branch to unblock us on PRs which depend on this one? |
✅ Jenkins job (on internal Jenkins) succeeded ✅ Build succeeded |
Build success |
@marek-safar yeah, I don't like long-running PR either. However that would break master must be releasable and SDK must ship identical mono. Also we are close to branch for the next milestone and I'd rather not run into the same 15.9 situation again. How close are we wrt XA and 2018-06 ? |
Unfortunately, I don't know how long before the code is in XA, we have only about 13 tests failures (not serious) but I have no idea when @jonpryor is going to merge it. |
✅ Jenkins job (on internal Jenkins) succeeded ✅ Build succeeded |
Build success |
❌ Build was (probably) aborted 🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Running XM tests on '10.11'' 🔥 : hudson.AbortException: Xamarin.Mac tests on macOS 10.11 failed (xammac_tests) ✅ Build succeeded |
@chamons have you seen the |
Build success |
I have not, but it completely looks like a "random failure". Filed as https://github.com/xamarin/maccore/issues/1084 The last test listed is a CloudKit test, so I could see some async \ network causing wonky test behavior. |
When might we see this in VS / VS4M? |
@taikodragon Since this has just landed in master, it wouldn't be until the 16.x timeframe. You can read about the VS release schedule here, and there are no announced dates currently, but thinking on the order of months would be reasonable. |
No description provided.