-
Notifications
You must be signed in to change notification settings - Fork 515
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
monotouch-test / iOS Unified 32-bits - simulator / Debug -> multiple failures #11504
Milestone
Comments
spouliot
added
bug
If an issue is a bug or a pull request a bug fix
iOS
Issues affecting iOS
labels
May 11, 2021
@mandel-macaque is there a way to determine if the test run above occurred on a VM or if it was on real hardware? |
@rolfbjarne I could duplicate them locally (not on a VM) |
This was referenced May 26, 2021
rolfbjarne
added a commit
to rolfbjarne/xamarin-macios
that referenced
this issue
Jun 1, 2021
Sometimes they work, sometimes they don't. Just ignore them to avoid unreliable test results. Partial fix for xamarin#11504.
rolfbjarne
added a commit
to rolfbjarne/xamarin-macios
that referenced
this issue
Jun 1, 2021
…est works in the iOS 11 simulator either. Partial fix for xamarin#11504.
rolfbjarne
added a commit
to rolfbjarne/xamarin-macios
that referenced
this issue
Jun 1, 2021
… versions where it didn't exist. It was introduced with Xcode 12.5, so ignore it on earlier OS versions. Partial fix for xamarin#11504.
|
rolfbjarne
added a commit
that referenced
this issue
Jun 2, 2021
Sometimes they work, sometimes they don't. Just ignore them to avoid unreliable test results. Partial fix for #11504.
This is fixed in |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Steps to Reproduce
Sadly it seems the commit does not trigger this test suite to run (even if all of them should run, unless impossible - which is not the case here)
Expected Behavior
No errors
Actual Behavior
Environment
main
Example
#11374 (comment)
PR with
run-all-tests
andskip-device-tests
The text was updated successfully, but these errors were encountered: