Skip to content
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

HTTPClientTests.testRaceNewRequestsVsShutdown flaky (crash in assert(self.pool.count == 0)) #371

Closed
weissi opened this issue May 27, 2021 · 3 comments
Assignees

Comments

@weissi
Copy link
Contributor

weissi commented May 27, 2021

Failed in CI on 5.0 job https://ci.swiftserver.group/job/async-http-client-swift50-prb/884/console

Test Case 'HTTPClientTests.testRaceNewRequestsVsShutdown' started at 2021-05-27 13:09:25.562
Assertion failed: file /code/Sources/AsyncHTTPClient/HTTPClient.swift, line 117
Current stack trace:
0    libswiftCore.so                    0x00007f7d115b7830 _swift_stdlib_reportFatalErrorInFile + 115
1    libswiftCore.so                    0x00007f7d114f294c <unavailable> + 3463500
2    libswiftCore.so                    0x00007f7d114f2a3e <unavailable> + 3463742
3    libswiftCore.so                    0x00007f7d112ee189 <unavailable> + 1347977
4    libswiftCore.so                    0x00007f7d114c6a32 <unavailable> + 3283506
5    libswiftCore.so                    0x00007f7d112ed569 <unavailable> + 1344873
6    async-http-clientPackageTests.xctest 0x000055a276b5bc1b <unavailable> + 838683

this is distinct but probably related to #290 . The line in question is line 117 in HTTPClient.swift.


    deinit {
        assert(self.pool.count == 0)   <<<<<< THIS ONE
        assert(self.state == .shutDown, "Client not shut down before the deinit. Please call client.syncShutdown() when no longer needed.")
    }
@weissi
Copy link
Contributor Author

weissi commented May 27, 2021

CC @artemredkin / @fabianfett

@fabianfett fabianfett self-assigned this Jun 28, 2021
@fabianfett fabianfett added this to the HTTP/2 support milestone Jun 28, 2021
@fabianfett
Copy link
Member

@fabianfett
Copy link
Member

Implementation replaced in #427. Not seen another instance of this in CI for now. If this comes up again it should be a new issue. (property count does not exist on connection pool anymore).

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

No branches or pull requests

2 participants