Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[d16-2] [xharness] Don't use a dash in the bundle identifer for watch…
…OS projects. (#6118) * [xharness] Don't use a dash in the bundle identifer for watchOS projects. It causes problems with the mscorlib test project, which can't be launched properly. I'm not sure what's the underlying cause, but here are some of the symptoms: * The watch app actually shows up fine on the device, but: * mlaunch isn't notified about the new process, so it thinks the app didn't launch. * The new process doesn't receive any environment variables we try to give it, which for instance means that it won't auto-start the tests upon launch. * If we ask mlaunch to attach with lldb, mlaunch will ask watchOS to launch the process in a suspended state while lldb attaches. Yet the watch app shows up on the device as if not asked to be suspended upon launch. It seems that the dash (I assume, because I haven't investigated this very deeply, I just happened to find a solution that worked) makes watchOS launch the app as if tapped, instead of launched from an IDE. The strangest part is that this only happens with the mscorlib test project, not any of the other test projects we run on the watch, and they all have dashes in their bundle identifiers... yet replacing the dash with another character (underscore, letter, removing it altogether) all made things work as expected. * [monotouch-test] Adjust expected value for watchOS bundle id. The watchOS bundle ID changed in fc5067e, and the test failure wasn't caught properly.
- Loading branch information
aab104d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❌ Build was (probably) aborted
🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Running XM tests on '10.10', Running XM tests on '10.10'' 🔥
✅ Build succeeded
✅ Packages: xamarin.ios-12.14.0.85.pkg xamarin.mac-5.14.0.85.pkg
✅ API Diff (from stable)
✅ API Diff (from PR only) (no change)
✅ Generator Diff (no change)
🔥 Xamarin.Mac tests on 10.10 failed: Xamarin.Mac tests on macOS 10.10 failed (xammac_tests) 🔥
🔥 Test run failed 🔥
Test results
4 tests failed, 0 tests' device not found, 238 tests passed.
Failed tests
Failure analysis
Final verdict: 🤥
aab104d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✅ Device tests passed on TvOS on Azure DevOps(TvOS): Html Report ✅
Test results
37 tests' device not found, 193 tests passed.
aab104d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔥 Device tests completed (Failed) on iOS on Azure DevOps(iOS): Html Report 🔥
Test results
33 tests failed, 37 tests' device not found, 160 tests passed.
Failed tests
Failure analysis
All the test failures are due to not being able to connect to the iOS devices. I've requested a reboot+reconnect of all the devices connected to this bot. There were no other failures, and the corresponding tvOS tests all passed, so 🤥.
Final verdict: 🤥
aab104d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❌ Status for 'xamarin-macios - sample testing (build)': failure.
Failure analysis
Final verdict: 🤥
aab104d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Setting state to
success
for all statuses.Only 🤥 (gred) issues found.