Skip to content

Conversation

@VincentDondain
Copy link
Contributor

No description provided.

Make.config Outdated
XCODE_DEVELOPER_ROOT=/Applications/Xcode11.app/Contents/Developer
XCODE_VERSION=11.1
XCODE_URL=http://xamarin-storage/bot-provisioning/xcodes/Xcode_11.1_GM_Seed.xip
XCODE_DEVELOPER_ROOT=/Applications/Xcode11.1-GM.app/Contents/Developer
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is that the location on the bots ?
it does not match https://xamarinhq.slack.com/archives/C99ER4A1M/p1569347681015300

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I think we went with this https://xamarinhq.slack.com/archives/C03CEMRFL/p1569348227198300

Xcode111-GM.app

Copy link
Contributor

@spouliot spouliot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should use the bump PR to change the reference for apidiff to point to the current stable :)

@monojenkins
Copy link
Collaborator

Build failure
Build failed or was aborted

🔥 Provisioning failed 🔥

@monojenkins
Copy link
Collaborator

Build failure
Build succeeded
API Diff (from stable)
⚠️ API Diff (from PR only) (🔥 breaking changes 🔥)
Generator Diff (no change)
🔥 Test run failed 🔥

Test results

1 tests failed, 86 tests passed.

Failed tests

  • xammac tests/Mac Modern/Release: Failed (Test run failed.)

@mandel-macaque
Copy link
Contributor

@VincentDondain CoreBluetooth is making the tests on Mac OS X fail, we did have some changes in there, we need to update the tests.

```
ObjCRuntime.RuntimeException: Failed to marshal the Objective-C object 0x7ff62ff227f0 (type: MonoTouchFixtures_CoreBluetooth_CBCentralManagerTest_ManagerDelegate). Could not find an existing managed instance for this object, nor was it possible to create a new managed instance (because the type 'MonoTouchFixtures.CoreBluetooth.CBCentralManagerTest+ManagerDelegate' does not have a constructor that takes one IntPtr argument).
```

Therefore, add the `IntPtr` `.ctor`
(Note: I cannot reproduce locally so I'm eyeballing this)
@VincentDondain
Copy link
Contributor Author

So I'm not quite sure how we end up in this situation on macOS:

ObjCRuntime.RuntimeException: Failed to marshal the Objective-C object 0x7ff62ff227f0 (type: MonoTouchFixtures_CoreBluetooth_CBCentralManagerTest_ManagerDelegate). Could not find an existing managed instance for this object, nor was it possible to create a new managed instance (because the type 'MonoTouchFixtures.CoreBluetooth.CBCentralManagerTest+ManagerDelegate' does not have a constructor that takes one IntPtr argument).

I was also thinking there could be a problem with the test Setup where the ManagerDelegate would not be initialized somehow. I cannot repro locally so it doesn't help with the investigation of the issue and I am not up to date on the CoreBluetooth-related things that happened this summer.

I'll take thoughts on this (:

public ManagerDelegate (IntPtr handle) : base (handle)
{
}

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That won't set the managed state (Event) back to a valid (non-null) value. It will likely work, just like rebuilding would have - i.e. your code change being irrelevant to the test success/failure.

My guess is that the 5sec timeout occurred on the bot and, while TearDown happened the callback occurred, throwing before the timeout assertion could occur.

You can try to duplicate this locally with a much shorter timeout.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still can't repro...

I tried playing with mgrDelegate.Event.WaitOne and the test's timeout [Timeout] and couldn't get the TearDown to happen before the Asserts...

I'm gonna ignore the test, file a bug and merge that PR so we can get going.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mmh actually it might be ScanForPeripherals failing... not RetrievePeripherals

@monojenkins
Copy link
Collaborator

Build failure
Build failed or was aborted

🔥 Build failed 🔥

@dalexsoto
Copy link
Member

build

@monojenkins
Copy link
Collaborator

Build success
Build succeeded
API Diff (from stable)
⚠️ API Diff (from PR only) (🔥 breaking changes 🔥)
Generator Diff (no change)
Test run succeeded

@VincentDondain VincentDondain merged commit 253900c into dotnet:xcode11.1 Sep 26, 2019
@VincentDondain VincentDondain deleted the xcode11.1-bump-gm branch September 26, 2019 03:13
VincentDondain added a commit to VincentDondain/xamarin-macios that referenced this pull request Oct 16, 2019
- Fixes dotnet#7045
- Fixes Xcode path and point API diff to HEAD of d16-3
- Ignore ScanForPeripherals & RetrievePeripherals tests for now (dotnet#7108)
@rolfbjarne rolfbjarne added the not-notes-worthy Ignore for release notes label Sep 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

not-notes-worthy Ignore for release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants