10000 CI slow-test hypothesis fail: libcst fails to parse 𮯰 · Issue #343 · python-trio/flake8-async · GitHub
[go: up one dir, main page]
Skip to content

CI slow-test hypothesis fail: libcst fails to parse 𮯰 #343

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.

Sign up for GitHub

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

Jump to bottom
Closed
jakkdl opened this issue Jan 28, 2025 · 2 comments
Closed

CI slow-test hypothesis fail: libcst fails to parse 𮯰 #343

jakkdl opened this issue Jan 28, 2025 · 2 comments
Labels
infrastructure improvements to tests/helpers/etc

Comments

@jakkdl
Copy link
Member
jakkdl commented Jan 28, 2025

I got a failing test case in https://github.com/python-trio/flake8-async/actions/runs/13008484527/job/36280611992#step:5:68 and opened Instagram/LibCST#1288

Idk if/when libcst will get around to fixing it, versus how likely hypothesis is to re-generate examples with unicode code points that will break libcst, but given I only bumped CI to 3.13 3 days ago it might become a regular thing and warrant some logic in the test to xfail on weird unicode.
@Zac-HD
Copy link
Member
Zac-HD commented Jan 28, 2025

ah, classic. I think this is "just" a new version of Unicode, unlike the new-parser issues I found in 3.9...

@jakkdl jakkdl added the infrastructure improvements to tests/helpers/etc label Mar 5, 2025
@jakkdl
Copy link
Member Author
jakkdl commented Jun 3, 2025

this was fixed in libcst==1.8.0

@jakkdl jakkdl closed this as completed Jun 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
infrastructure improvements to tests/helpers/etc
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jakkdl @Zac-HD
0