-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Test failures on aiohttp 3.9.0 #7858
Comments
Well, it either failed to build or install the C parser. It appears you have the steps to build it. But, when I try running the tests locally, I usually need to install the package for it to be able to import the C parser, it doesn't seem to work when run from the source directory (unless maybe, |
I'm observing the exact same failures on NixOS. |
I don't think there should be a difference from 3.8 to 3.9. I don't think there's any changes related to building or testing that should be relevant. |
I ran |
**This is a backport of PR #7863 as merged into master (3a21134).** <!-- Thank you for your contribution! --> ## What do these changes do? fixes #7858 <!-- Please give a short brief about these changes. --> ## Are there changes in behavior for the user? <!-- Outline any notable behaviour for the end users. --> ## Related issue number #7858 <!-- Are there any issues opened that will be resolved by merging this change? --> ## Checklist - [ ] I think the code is well written - [ ] Unit tests for the changes exist - [ ] Documentation reflects the changes - [ ] If you provide code modification, please add yourself to `CONTRIBUTORS.txt` * The format is <Name> <Surname>. * Please keep alphabetical order, the file is sorted by names. - [ ] Add a new news fragment into the `CHANGES` folder * name it `<issue_id>.<type>` for example (588.bugfix) * if you don't have an `issue_id` change it to the pr id after creating the pr * ensure type is one of the following: * `.feature`: Signifying a new feature. * `.bugfix`: Signifying a bug fix. * `.doc`: Signifying a documentation improvement. * `.removal`: Signifying a deprecation or removal of public API. * `.misc`: A ticket has been closed, but it is not of interest to users. * Make sure to use full sentences with correct case and punctuation, for example: "Fix issue with non-ascii contents in doctest text files." Co-authored-by: Robert Schütz <[email protected]>
Describe the bug
Tests involving
HttpRequestParserC
fail or are skipped, andtest_unsupported_upgrade[pyloop]
fails.To Reproduce
Trying to package the new version for Arch Linux. The build bails after
check()
due to the test suite failures.The build script currently:
Expected behavior
Happy test suite
Logs/tracebacks
Python Version
aiohttp Version
3.9.0
multidict Version
yarl Version
OS
Arch Linux
Related component
Server, Client
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: