-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[SR-10428] URLSession.getTasksWithCompletion method implemented #2105
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
[SR-10428] URLSession.getTasksWithCompletion method implemented #2105
Conversation
@swift-ci please test |
|
@swift-ci test |
Looks like a different failure this time. A compilation error in Dispatch
I'm not sure why this is coming up. Let's start the CI for one more time. |
@swift-ci test |
@pushkarnk Dispatch always seems to have problems building, unfortunately the underlying build errors are hidden in the logs which makes fixing them harder. |
@spevans Oh, thanks for that info. I can see other PR builds going through. Do you have some ways to work around this situation? :) |
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.
Looks good to me! We only need to fix the build issues now.
@pushkarnk Is there anything I had to update in the PR to get the build working? |
@swift-ci test |
c7f8251
to
5093191
Compare
In my last CI build successfully ran in Linux but failed in macOS X. In my local machine, the project is building successfully with Swift Developer Snapshot 2019-04-04(a). I guess the reason for the build failure has something to do with the CI setup. Anyway, I rebased my branch to have all the latest code. Please trigger the CI build one more time. |
@swift-ci test |
@karthikkeyan I don't think it has anything to do with the PR. Seems like a CI issue. |
@swift-ci test |
A different problem this time:
|
@shahmishal We're seeing the CI fail with different kinds of issues here (see comments above). Can you please help us out? |
@swift-ci clean test |
@swift-ci test |
@pushkarnk Sorry, |
@swift-ci test macOS |
Thanks @shahmishal .. the CI has passed this time! |
@karthikkeyan I realised that this pull request also fixes a bug in |
Of course Pushkar, I will added on more unit test. |
* New private property hasTriggredResume introduces to track whether the task actually move passed the suspendCount in execution * New internal property isSuspendedAfterResume introduced to find the accurate state reason for suspend state
5093191
to
1833606
Compare
@pushkarnk Thanks for reviewing the PR earlier, I have added unit test for |
@swift-ci test |
Thanks @karthikkeyan |
@swift-ci test and merge |
1 similar comment
@swift-ci test and merge |
hasTriggredResume
introduced to track whether the task actually move past thesuspendCount
in executionisSuspendedAfterResume
introduced to find the accurate state reason for.suspend
stateBug Link: https://bugs.swift.org/browse/SR-10428