FAIL_ReactiveCocoa_3.0_BuildXcodeWorkspaceScheme_ReactiveCocoa-iOS_generic-platform-iOS.log FAIL_ReactiveCocoa_3.0_BuildXcodeWorkspaceScheme_ReactiveCocoa-tvOS_generic-platform-tvOS.log FAIL_ReactiveCocoa_3.2_BuildXcodeWorkspaceScheme_ReactiveCocoa-iOS_generic-platform-iOS.log FAIL_ReactiveCocoa_3.2_BuildXcodeWorkspaceScheme_ReactiveCocoa-tvOS_generic-platform-tvOS.log FAIL_ReactiveCocoa_4.0_BuildXcodeWorkspaceScheme_ReactiveCocoa-iOS_generic-platform-iOS.log FAIL_ReactiveCocoa_4.0_BuildXcodeWorkspaceScheme_ReactiveCocoa-tvOS_generic-platform-tvOS.log

I have a PR to add xfails for these failing configurations.

apple/swift-source-compat-suite#172

This was exposed by #15412

cc @belkadan @DougGregor who are on the thread of the PR

@swift-ci create

Doug and I are leaning towards asking the ReactiveCocoa folks for an update, since previously they were basically getting an arbitrarily-chosen numberOfArguments overload. Since the types of the two possibilities were Int and UInt this wasn't too harmful, but it could have been much worse (imagine Int and CGFloat for some other property).

@clackary, what do you think?

@belkadan, I'd echo the concerns that aschwaighofer@apple.com (JIRA User) mentioned on https://github.com/apple/swift/pull/15412. There's a risk in keeping xfails on a sizable chunk of ReactiveCocoa configurations. It could create a window for introducing bugs.

That being said, if this ambiguity error isn't the result of a new compiler bug, reaching out to the ReactiveCocoa maintainer for an update is probably the right thing to do.

PR for ReactiveCocoa's fix: ReactiveCocoa/ReactiveCocoa#3580

Comment by Anders Ha (JIRA)

Compatibility Suite Update: apple/swift-source-compat-suite#174

Resolved by the above linked pull requests.

Closing this out, but this did uncover another issue, tracked here: https://bugs.swift.org/browse/SR-7346