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

bindings/python: Test failed for Fatal Python error: PyGILState_Release #1723

Closed
Xuanwo opened this issue Mar 21, 2023 · 8 comments
Closed

Comments

@Xuanwo
Copy link
Member

Xuanwo commented Mar 21, 2023

https://github.com/apache/incubator-opendal/actions/runs/4480668361/jobs/7876306343

Took 0m0.004s
Fatal Python error: PyGILState_Release: thread state 0x7f44d4003280 must be current when releasing
Python runtime state: finalizing (tstate=0x00007f44db970258)

Thread 0x00007f44db0dbb80 (most recent call first):
  <no Python frame>
/home/runner/work/_temp/c6261849-b280-[41](https://github.com/apache/incubator-opendal/actions/runs/4480668361/jobs/7876306343#step:6:42)08-a933-ef0fdcb21[42](https://github.com/apache/incubator-opendal/actions/runs/4480668361/jobs/7876306343#step:6:43)4.sh: line 1:  7154 Aborted                 (core dumped) python -m behave tests
@Xuanwo
Copy link
Member Author

Xuanwo commented Mar 21, 2023

Hey @messense, would you like to take a look?

@messense
Copy link
Member

I'll have to reproduce it locally first.

@messense
Copy link
Member

Unable to reproduce it on Ubuntu 22.04 with while true; do .venv/bin/python -m behave tests || exit 1; done running for half an hour...

@Xuanwo
Copy link
Member Author

Xuanwo commented Mar 22, 2023

Does this relate to our python binding's workflow?

Seems we are not using the venv for testing.

https://github.com/apache/incubator-opendal/blob/cc8e489e76f5047b1df7e3c1240bb61ab4541caf/.github/workflows/bindings_python.yml#L42-L58

@messense
Copy link
Member

Venv just isolates packages, at runtime it's mostly the same.

@messense
Copy link
Member

The fatal error occurs when the Python interpreter was shutting down, so it maybe related to GC or even not our issue. (CPython can and does have bugs, lol)

@Xuanwo
Copy link
Member Author

Xuanwo commented Mar 22, 2023

The fatal error occurs when the Python interpreter was shutting down, so it maybe related to GC or even not our issue. (CPython can and does have bugs, lol)

Thank you for investigating. Let's close this issue until we have more information.

@Xuanwo Xuanwo closed this as not planned Won't fix, can't repro, duplicate, stale Mar 22, 2023
@Xuanwo
Copy link
Member Author

Xuanwo commented Apr 2, 2023

Another coredump:

Fatal Python error: PyGILState_Release: thread state 0x7f4b780034f0 must be current when releasing
Python runtime state: finalizing (tstate=0x00007f4b80445258)

Thread 0x00007f4b7fbb0c40 (most recent call first):
  <no Python frame>
/home/runner/work/_temp/b31de088-9046-45a5-8b43-b0427d1f2[38](https://github.com/apache/incubator-opendal/actions/runs/4587412840/jobs/8100898542#step:6:39)c.sh: line 1:  7117 Aborted                 (core dumped) python -m behave tests

https://github.com/apache/incubator-opendal/actions/runs/4587412840/jobs/8100898542

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants