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

monotouch-test / iOS Unified 32-bits - simulator / Debug -> multiple failures #11504

Closed
spouliot opened this issue May 11, 2021 · 4 comments
Closed
Assignees
Labels
bug If an issue is a bug or a pull request a bug fix iOS Issues affecting iOS
Milestone

Comments

@spouliot
Copy link
Contributor

spouliot commented May 11, 2021

Steps to Reproduce

  1. Start xharness
  2. Run "monotouch-test / iOS Unified 32-bits - simulator / Debug"

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

	[FAIL] TestCallbackPlayAlert :   TestCallbackPlayAlert
	[FAIL] TestCallbackPlaySystem :   TestCallbackPlaySystem
	[FAIL] EnumValues_22351 : AppleMoveTime could not be created: System.ArgumentNullException: Value cannot be null.
	[FAIL] ReturnReleaseTest : System.NullReferenceException : Object reference not set to an instance of an object
	[FAIL] TryCopyCurrentNetworkInfo :   Dictionary
Tests run: 2460 Passed: 2410 Inconclusive: 45 Failed: 5 Ignored: 342

Environment

main

Example

#11374 (comment)

PR with run-all-tests and skip-device-tests

@spouliot spouliot added bug If an issue is a bug or a pull request a bug fix iOS Issues affecting iOS labels May 11, 2021
@spouliot spouliot added this to the Future milestone May 11, 2021
@rolfbjarne
Copy link
Member

@mandel-macaque is there a way to determine if the test run above occurred on a VM or if it was on real hardware?

@spouliot
Copy link
Contributor Author

@rolfbjarne I could duplicate them locally (not on a VM)

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 rolfbjarne self-assigned this Jun 1, 2021
rolfbjarne added a commit that referenced this issue Jun 2, 2021
… versions where it didn't exist. (#11765)

It was introduced with Xcode 12.5, so ignore it on earlier OS versions.

Partial fix for #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.
rolfbjarne added a commit that referenced this issue Jun 2, 2021
…est works in the iOS 11 simulator either. (#11764)

* [monotouch-test] It doesn't look like the TryCopyCurrentNetworkInfo test works in the iOS 11 simulator either.

Partial fix for #11504.

* Always assert null.
@rolfbjarne
Copy link
Member

This is fixed in main now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug If an issue is a bug or a pull request a bug fix iOS Issues affecting iOS
Projects
None yet
Development

No branches or pull requests

2 participants