-
Notifications
You must be signed in to change notification settings - Fork 516
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
[appkit] Fix introspection tests for NSAccessibility on macOS 10.9 #10016
Conversation
This reverts parts of #9993 and add a special case to the test looking for duplicate attributes between members and the type. Why ? Introspection fails because `bgen` inline the `NSAccessibility` protocol (added in 10.10) into types that existed earlier. That's normally not a problem since the type-level attribute is there. However because of the 10.9 (type) vs 10.10 (protocol) issue that was moved into the manual bindings (so `bgen` does not know it) Even if built inside `COREBUILD` the issue exists since the protocol interface does not really exists at that point (by default), so it's the type (10.9) availability that is looked up. In retrospect we should have created a new type, like Swift did (a few years later), named `NSAccessibilityProtocol` for 10.10. Fix #10009
Build success |
Still running - but results on 10.9 are green. |
❌ Build was (probably) aborted 🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Running XM tests on '10.16', Running XM tests on '10.16'' 🔥 ✅ Build succeeded ✅ API Diff (from stable) Test results61 tests failed, 95 tests passed.Failed tests
|
Failures are unrelated to PR (it fix the macOS 10.9 failure as expected) and due to #9949 |
This reverts parts of #9993
and add a special case to the test looking for duplicate attributes
between members and the type.
Why ? Introspection fails because
bgen
inline theNSAccessibility
protocol (added in 10.10) into types that existed earlier. That's
normally not a problem since the type-level attribute is there.
However because of the 10.9 (type) vs 10.10 (protocol) issue that was
moved into the manual bindings (so
bgen
does not know it)Even if built inside
COREBUILD
the issue exists since the protocolinterface does not really exists at that point (by default), so it's
the type (10.9) availability that is looked up.
In retrospect we should have created a new type, like Swift did (a
few years later), named
NSAccessibilityProtocol
for 10.10.Fix #10009