-
Notifications
You must be signed in to change notification settings - Fork 16
Conversation
clausjoergensen
commented
Nov 18, 2020
•
edited
Loading
edited
- Removed Carthage as it's not compatible with Xcode 12
- Updated to the latest Quick&Nimble for Xcode 12 support.
- Ran the linter (for what appears to be the first time in a while)
- Fixed swiftlint errors.
- Fixed various compilation errors in the tests.
- Disabled Jazzy's check for undocumented methods, as this clearly hadn't been checked for a very long time.
- Updated CI scripts to reflect the above changes.
These tests seems to be unstable
|
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.
Much appreciated for a long overdue cleanup! 🙇
Those flaky tests pass on my local machine, so I'd opt for keeping them for now (it's not that hard verifying it's those same requests failing in future Travis builds).
@@ -261,10 +261,6 @@ class URLSessionTests: QuickSpec { | |||
SDKConfiguration.shared.refreshRetryCount = 2 | |||
doDataTask(session, url: URL(string: wantedUrl)!) { _, _, error in | |||
expect(error).to(matchError(ClientError.userRefreshFailed(kDummyError))) | |||
guard let clientError = error as? ClientError, case let ClientError.userRefreshFailed(error) = clientError else { |
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.
Why was this removed?
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.
Caused the test to always fail, and it didn't seem to actually contribute anything to the test itself. But maybe we should revert it and just let it fail on Travis for a bit
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.
It doesn't pass on local either, so let's keep it removed 🙂