MagicStack / MagicStack/uvloop
[ALTLinux] [ppc64le] [0.18.0] `AssertionError: Didn't reach a full buffer`
Nobody has claimed this yet.
- Dominant language
- Cython
- Stars
- 11.9k
- Forks
- 616
- PR merge metrics
- No merged PRs in 30d
Description
- uvloop version: 0.18.0 (from tag
v0.18.0) - Python version: 3.11.6
- Platform: ppc64le
- Can you reproduce the bug with
PYTHONASYNCIODEBUGin env?: Will report later after try in a virtual machine. - Does uvloop behave differently from vanilla asyncio? How?: [no info]
The bug is in tests.
Fails only on ppc64le platform. More detailed log is here: https://git.altlinux.org/tasks/331829/build/100/ppc64le/log.
Another platforms (the bug doesn't reproduce on them):
- https://git.altlinux.org/tasks/331829/build/100/aarch64/log
- https://git.altlinux.org/tasks/331829/build/100/armh/log
- https://git.altlinux.org/tasks/331829/build/100/i586/log
- https://git.altlinux.org/tasks/331829/build/100/x86_64/log
Note: the bug doesn't reproduce in uvloop version 0.17.0 (from tag v0.17.0) on all of the platforms listed above.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the test failure AssertionError: Didn't reach a full buffer in the linked ppc64le build log, then compare the failing behavior between uvloop 0.18.0 and 0.17.0. Reproduce it on ppc64le and check whether it differs from the other listed platforms; done means the test passes reliably without masking the underlying failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100