Skip to content

CI: [diagnostic, do not merge] Confirm findings hold on latest main - #711

Closed
echoix wants to merge 1 commit into
mainfrom
ci-diag/confirm-on-latest-main
Closed

echoix wants to merge 1 commit into
mainfrom
ci-diag/confirm-on-latest-main

Conversation

@echoix

@echoix echoix commented Sep 26, 2026

Copy link
Copy Markdown
Owner

Purpose

All prior diagnostic PRs in this investigation (#701-#710) were based
on commit b0a6d77, which is 15 commits behind d24a5e0 (the
commit actually used in the originally reported passing/failing OSGeo4W
runs) and further behind current main. Checked the 15 intervening
commits directly:

  • `e39fb8c0e4` (Python 3.14 fork/forkserver pin) is explicitly a
    no-op on Windows per its own commit message.
  • `243ec7594d` (C++17 standard) only affects C++ compilation;
    `grass_gis.8.6.dll` is built entirely from `.c` files per the
    compile log.
  • None of the other 13 touch CI workflows, pytest config, or ctypes
    loading.

What this PR does

Re-runs the core comparison this whole investigation rests on --
a plain `python -c "from grass.pygrass import utils"` import (should
succeed) followed by bare `pytest` collecting the same import with no
xdist (should crash with `Windows fatal exception: code 0xc0000139`)
-- against the actual current main tip, to confirm the finding isn't
an artifact of testing a stale base.

This PR is for CI investigation only and is not meant to be merged.

🤖 Generated with Claude Code

…ot for merge)

All prior diagnostics in this investigation were run against commit
b0a6d77, which turned out to be 15 commits behind the commit
(d24a5e0) actually used in the originally reported passing/failing
runs, and further behind current main. Checked the 15 intervening
commits directly: none touch Windows CI, ctypes loading, or pytest
config (the two candidates worth a closer look -- the Python 3.14
fork/forkserver fix and the C++17 standard change -- are explicitly
Windows-inert and C++-only respectively, and grass_gis.8.6.dll is
built entirely from .c files).

This re-runs the core comparison (plain python import succeeds,
pytest collecting the same import crashes with "Windows fatal
exception: code 0xc0000139") against the actual current main tip, to
confirm the finding isn't an artifact of testing a stale base.

Temporary, for CI investigation only.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@echoix echoix closed this Sep 30, 2026
@echoix
echoix deleted the ci-diag/confirm-on-latest-main branch September 30, 2026 20:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant