Skip to content

XFAIL GRDB and ObjectMapper #127

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

Merged
merged 4 commits into from
Feb 4, 2018
Merged

XFAIL GRDB and ObjectMapper #127

merged 4 commits into from
Feb 4, 2018

Conversation

rudkx
Copy link
Contributor

@rudkx rudkx commented Jan 2, 2018

XFAIL GRDB
swiftlang/swift#13342 uses conditional conformance to make Range a Collection when its Bound is Strideable. For compatibility, CountableRange is still available as a type alias.

There is one source compatibility issue with this: currently if you extend a CountableRange with an identical method/property as Range, you will get a compilation error of a duplicate. This shouldn't really happen – specifying CountableRange should be similar to Range where Bound: Strideable but generic type aliases need an enhancement to make this work.

GRDB is the one project that does this (Foundation also did similar things but has been changed to use RangeExpression instead, avoiding the issue). XFAILing this in the compatibility test suite until the type alias change has been made.

XFAIL ObjectMapper now that IUOs are removed from the type system and their use of overloading functions by different kinds of optionals in the case of inout parameters is something we can no longer represent.

@rudkx
Copy link
Contributor Author

rudkx commented Jan 2, 2018

@swift-ci test

1 similar comment
@rudkx
Copy link
Contributor Author

rudkx commented Jan 2, 2018

@swift-ci test

@rudkx
Copy link
Contributor Author

rudkx commented Jan 3, 2018

Hmm, perhaps this is actually a problem with something in my JSON.

@lplarson
Copy link
Contributor

lplarson commented Jan 3, 2018

There are a few comma issues in your json:

"configuration": "Release" <-- missing trailing comma
 +        "xfail": {
 +          "compatibility": {
 +            "3.0": {
 +              "branch": {
 +                "master": "https://bugs.swift.org/browse/SR-6690" <-- missing trailing comma
 +                "swift-4.1-branch": "https://bugs.swift.org/browse/SR-6690"
 +              }
 +            }, <-- trailing comma that needs to be removed
 +	  }

@lplarson
Copy link
Contributor

lplarson commented Jan 5, 2018

@swift-ci test

1 similar comment
@lplarson
Copy link
Contributor

lplarson commented Jan 5, 2018

@swift-ci test

@lplarson
Copy link
Contributor

lplarson commented Jan 9, 2018

@rudkx Is this still needed? The compat jobs are passing.

@rudkx
Copy link
Contributor Author

rudkx commented Jan 9, 2018

It isn't needed at the moment because I backed off on emitting an error with the compiler change I made, instead emitting a warning.

However, I have other changes in the works that will make it impossible to emit the warning, so we'll be back to needing to XFAIL until the project is updated to not have inout overloads that vary only in the kind of optional involved.

@rudkx
Copy link
Contributor Author

rudkx commented Jan 9, 2018

We can close this out if you'd prefer, until that other change is ready to merge.

@rudkx rudkx changed the title XFAIL ObjectMapper as a result of the fix for SR-6685. XFAIL ObjectMapper as a result of removing IUOs from the type system. Jan 25, 2018
@rudkx
Copy link
Contributor Author

rudkx commented Feb 1, 2018

I am ready to merge swiftlang/swift#14299, so we'll need to merge this in as well as XFAIL SwiftLint until its dependencies are updated to use a newer SourceKitten.

@rudkx
Copy link
Contributor Author

rudkx commented Feb 1, 2018

/cc @lancep

@rudkx
Copy link
Contributor Author

rudkx commented Feb 2, 2018

Please test with following PR:
swiftlang/swift#14299

@swift-ci Please test

@rudkx
Copy link
Contributor Author

rudkx commented Feb 2, 2018

@swift-ci Please test

@rudkx
Copy link
Contributor Author

rudkx commented Feb 2, 2018

The failure here appears due to swiftlang/swift#13342, for which we have #131 open to XFAIL GRDB.swift, but the latter failed.

@rudkx
Copy link
Contributor Author

rudkx commented Feb 3, 2018

@swift-ci Please test with the following PR:
#131

@swift-ci Please test

@rudkx rudkx changed the title XFAIL ObjectMapper as a result of removing IUOs from the type system. XFAIL GRDB and ObjectMapper Feb 3, 2018
@rudkx
Copy link
Contributor Author

rudkx commented Feb 3, 2018

Okay, trying again, this time after merging #131 into my PR.

@rudkx
Copy link
Contributor Author

rudkx commented Feb 3, 2018

@swift-ci Please test

rudkx and others added 4 commits February 2, 2018 19:54
XFAIL ObjectMapper since the fix for
https://bugs.swift.org/browse/SR-6685 results in the project breaking.

The fix for the project is very simple - delete some 'inout T!'
overloads that should never have been allowed by the compiler.
@rudkx
Copy link
Contributor Author

rudkx commented Feb 3, 2018

@swift-ci Please test

1 similar comment
@rudkx
Copy link
Contributor Author

rudkx commented Feb 3, 2018

@swift-ci Please test

@rudkx
Copy link
Contributor Author

rudkx commented Feb 3, 2018

This is now blocked by a bunch of other failures: https://forums.swift.org/t/source-compatibility-bots-in-bad-shape/9526

@rudkx
Copy link
Contributor Author

rudkx commented Feb 3, 2018

@swift-ci Please test and merge

@rudkx
Copy link
Contributor Author

rudkx commented Feb 3, 2018

@swift-ci Please test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants