enough-analyst-54434
12/12/2022, 9:38 PM...
>> Verifying PANTS_SHA is respected
Bootstrapping Pants 2.16.0.dev1+git298409b3 using cpython 3.9.15
Installing pantsbuild.pants==2.16.0.dev1+git298409b3 into a virtual environment at /home/runner/.cache/nce/638e71475c6feb8228292d052407a5cf6b7813caf3630e80d42711d1081e8c1d/bindings/venvs/2.16.0.dev1+git298409b3
New virtual environment successfully created at /home/runner/.cache/nce/638e71475c6feb8228292d052407a5cf6b7813caf3630e80d42711d1081e8c1d/bindings/venvs/2.16.0.dev1+git298409b3.
21:30:47.58 [INFO] Initializing scheduler...
21:30:48.17 [INFO] Scheduler initialized.
2.16.0.dev1+git298409b3
Fatal Python error: PyGILState_Release: thread state 0x7f156c0010d0 must be current when releasing
Python runtime state: finalizing (tstate=0x14a06a0)
Thread 0x00007f1585b0ac00 (most recent call first):
<no Python frame>
Error: Command "dist/scie-pants-linux-x86_64" "--no-verify-config" "-V" failed with exit code: None
Error: Process completed with exit code 1.
bitter-ability-32190
12/12/2022, 9:40 PMenough-analyst-54434
12/12/2022, 9:40 PM./pants -V
witty-crayon-22786
12/12/2022, 9:55 PMpantsd
exiting? IIRC, this is related to teardown of the interpreter (the “finalizing” bit)./build-support/bin/release.sh build-universal-pex
), in a similar spot.enough-analyst-54434
12/12/2022, 10:11 PM./pants -V
and it prints out the version successfully and then the CPython thread state error.witty-crayon-22786
12/12/2022, 10:59 PMIt is during teardown from the looks of the output I included above.withand it prints out the version successfully and then the CPython thread state error../pants -V
pantsd
enabled, ./pants -V
shouldn’t actually exit pantsd
. so unless it is the client crashing…?enough-analyst-54434
12/12/2022, 11:02 PMwitty-crayon-22786
12/12/2022, 11:03 PMenough-analyst-54434
12/12/2022, 11:03 PMwitty-crayon-22786
12/12/2022, 11:05 PMenough-analyst-54434
12/12/2022, 11:06 PMwitty-crayon-22786
12/12/2022, 11:06 PMscie
but … i believe that i have also seen this on macOS for the PEX building command from the release process (this was unrelated, (un)fortunately. but is fixed here at least: https://github.com/pantsbuild/pants/pull/17785), in a similar spot../build-support/bin/release.sh build-universal-pex
enough-analyst-54434
12/12/2022, 11:21 PMwitty-crayon-22786
12/12/2022, 11:34 PMBut it’s an ongoing issue in not the client.what do you mean by “not the client”?
enough-analyst-54434
12/12/2022, 11:36 PMwitty-crayon-22786
12/12/2022, 11:38 PMenough-analyst-54434
12/12/2022, 11:40 PMwitty-crayon-22786
12/12/2022, 11:42 PMbut pantsd will not so investment in me tracking down what why how for this should be non-throwaway effortmaybe. i think that the
pantsd
side of things is relatively well understood: we absolutely spawn tasks into the background there which run python code, and so there is a teardown question.
how that might be happening on the client side is more mysterious to meenough-analyst-54434
12/12/2022, 11:43 PM