Repository navigation
Conversation
A plain `python -c "from grass.pygrass import utils"` run before the
"Install additional python packages" step succeeds (see
ci-diag/standalone-import-test), but pytest/python -m pytest collecting
the same import after that step crashes with "Windows fatal exception:
code 0xc0000139" (see ci-diag/no-xdist-single-process and
ci-diag/python-m-pytest-vs-exe). None of pytest/pytest-xdist/execnet/
pytest-timeout/pytest-randomly/colorama declare a pywin32 dependency
(checked via PyPI metadata), so this isn't a duplicate pywin32 install
conflict, a scenario pywin32's own README explicitly blames for this
same generic Windows error text ("The specified procedure could not
be found").
This repeats the plain standalone import again, but now after pip has
installed pytest and friends, to isolate whether the crash is tied to
something the pip install changes in the environment, or specifically
to pytest's own import/collection machinery.
Temporary, for CI investigation only.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Eighth diagnostic. Ruled out with hard binary/metadata evidence so far:
_DISABLE_CONSTEXPR_MUTEX_CONSTRUCTORmutex-hack -- checkeddirectly in the binaries (not relying on git commit timestamps,
since OSGeo4W's build server may apply changes to production before
committing them): both old and new gdal313.dll import
_Mtx_init_in_situ/_Cnd_init_in_situfrom MSVCP140.dll at theidentical hint values, so the hack's effect is identical in both
builds.
none declare a pywin32 dependency (checked via PyPI metadata), ruling
out a duplicate-pywin32-install DLL conflict (the scenario pywin32's
own README blames for this exact generic Windows error text).
The crash reproduces identically via bare
pytestand viapython -m pytest, with or without-n/xdist -- but not via aplain
python -c "from grass.pygrass import utils"import, nor asequential import of all grass.lib.* submodules, both run before the
"Install additional python packages" pip-install step.
What this PR does
Repeats the same plain standalone import, but now placed after the
pip-install step (right before "Run pytest with multiple workers in
parallel"), to cleanly separate two remaining explanations:
import/collection machinery (not xdist, not the exe launcher stub --
both already ruled out), not anything the pip install itself changes
in the environment.
environment is the actual trigger, independent of pytest's import
mechanics.
This PR is for CI investigation only and is not meant to be merged.
🤖 Generated with Claude Code