fix: tools/bugreport launcher finds a Python 3.8+ itself and never starts a Store alias (#166)
CI / verify (push) Successful in 5m20s
CI / pwsh (push) Successful in 1m53s
Release / release (push) Successful in 36s

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2

Files changed:
- .gitea/workflows/ci.yml
- CHANGES.md
- INSTALL.md
- VERSION
- instructions/bug-report.md
- tools/README.md
- tools/bugreport
- tools/bugreport.ps1
- tools/bugreport.py
- tools/chemenu/tests/test_bugreport_launcher.py
- tools/chemenu/tests/test_instructions_shell.py
- tools/chemenu/tests/test_portability.py
This commit is contained in:
torben committed 2026-10-02 13:12:19 +02:00
1 parent c77bda2004
commit 5d937233b1
12 files changed
+539 -21

No files matched your search

+4 -3
View File
@@ -307,12 +307,13 @@ jobs:
- name: The bug-report collector works in the distribution
# tools/bugreport.py is the one part of the stack that must run when
# nothing else does, so it is exercised as shipped: from the export,
# on the runner's plain python3, in the instance the step above set up.
# through the tools/bugreport launcher the instructions name, which picks
# the runner's plain python3, in the instance the step above set up.
# The unit tests cover what it collects; this covers that it arrives.
run: |
set -eu
cd "$INSTANCE_DIR"
python3 tools/bugreport.py --no-trace
tools/bugreport --no-trace
bundle=$(ls -d reports/bugreport-*/ | head -n 1)
test -f "$bundle/MANIFEST.md"
test -f "$bundle/environment.json"
@@ -321,7 +322,7 @@ jobs:
# The same collector with --pseudonymise: the mapping lies beside the
# bundle, not in it or its zip, and this container's hostname is gone.
rm -rf reports/bugreport-*
python3 tools/bugreport.py --no-trace --pseudonymise
tools/bugreport --no-trace --pseudonymise
bundle=$(ls -d reports/bugreport-*/ | head -n 1)
bundle=${bundle%/}
test -f "$bundle.pseudonyms.json"