emrg: installer old-python health check before stop_all (rant 2026-08-19T00:44:52) - #857
Merged
Merged
Conversation
argszero
commented
Aug 18, 2026
argszero
left a comment
OwnerAuthor
There was a problem hiding this comment.
✅ LGTM — cycle 786 (Committer). CI test + test-windows (incl. iscc compile smoke test) both PASS on head 781614f. Health-check pattern verified: skip-on-broken-python preserves the clean-install path, healthy-python path unchanged.
argszero
commented
Aug 18, 2026
argszero
left a comment
OwnerAuthor
There was a problem hiding this comment.
✅ LGTM — cycle 787 (Committer). Independent re-verify: head unchanged (781614f), CI test + test-windows PASS. Diff re-inspected — health-check command pattern, skip-on-failure path (Result stays '' → install continues), and preserved stop_all path all correct. 2/3.
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 freeto 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.
Summary
Windows upgrade installs could hard-abort when the old runtime python in the previous install directory was corrupted. Per host rant 2026-08-19T00:44:52 (reproduced on v0.2.51 upgrade):
ModuleNotFoundError: No module named 'encodings'at startup — the old python-dist was broken by the earlier v0.2.49/v0.2.50-Iincident, so runningstop_all.pywith it always failed and aborted the install. Deleting the oldinstall\bin(clean-install path) made the same v0.2.51 package install successfully — the package itself is fine, the upgrade path was the fragile point.Change
In
PrepareToInstall(generated.issviamake-installer.sh), before running stop_all with the old runtime python:python.exe -c "import encodings, sys"(redirected to the log via{cmd}, same pattern as stop_all per R125).The health-check failure details go into the log file + the Setup log (
Log(...)).Verification
bash -n packaging/make-installer.sh✓.issheredoc rendered exactly as CI does (stub payload) — generatedPrepareToInstallinspected ✓test_make_installer_iss_old_python_health_check+ existingtest_make_installer_iss_has_prepare_to_install/test_build_runtime_copies_stop_all_not_stop_emrg/test_stop_emrg_cmd_deletedpass (pure text assertions, no iscc/cmd/python execution) ✓Agent.mdtest count 958 → 959 (new test function; guarded bytest_doc_counts.py)iscccompile smoke test) will validate the Inno Pascal syntax