Skip to content
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 mono to head of 2018-02 including the removal of System.Memory facade #4147

Merged
merged 1 commit into from
May 29, 2018

Conversation

spouliot
Copy link
Contributor

Commit list for mono/mono:

Diff: mono/mono@c22f532...7bdb7dd

…acade

Commit list for mono/mono:

* mono/mono@7bdb7dd7658 Bump API snapshot submodule
* mono/mono@65d719d16ed [Facades] Removes System.Memory
* mono/mono@88262b52d26 [profiler] Switch tls storage to use mono_thread_info_get/set_tools_data. Fixes xamarin#7683
* mono/mono@aaed1f77ce4 [mono-threads] Introduce mono_thread_info_get/set_tools_data so they can store data sanely.
* mono/mono@58637d0ee7c [runtime] Gracefully handle crashes before mono-state dependencies initialized (xamarin#8842)

Diff: mono/mono@c22f532...7bdb7dd
@monojenkins
Copy link
Collaborator

Build failure
Build comment file:

Provisioning succeeded
Build succeeded
API Diff (from stable)
API Diff (from PR only)
Generator Diff
🔥 Test run failed 🔥

Test results

2 tests failed, 0 tests skipped, 215 tests passed.

Failed tests

  • mini/watchOS - simulator/Debug: Failed
  • monotouch-test/watchOS - simulator/Release (all optimizations): Failed

@spouliot
Copy link
Contributor Author

spouliot commented May 29, 2018

Tests were successful but the XML could not be parsed -> https://github.com/xamarin/maccore/issues/827

@spouliot spouliot merged commit 7d28d2b into xamarin:master May 29, 2018
@spouliot spouliot deleted the mono-bump-20180529 branch May 29, 2018 15:48
@cwrea
Copy link

cwrea commented Jun 8, 2018

@spouliot Is there any ETA on an updated Xamarin.iOS release to address #4168? Thank you. FWIW, it's a blocking issue—Xamarin.iOS developers can't use Entity Framework Core 2.1 and many other updated libraries that either directly or indirectly depend on System.Memory. I've tried removing the facade, I've tried manually referencing the netstandard2.0 version of the DLL, etc. and nothing works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants