Skip to content

Treat "env changed" as a warning, not a failure #813

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
vstinner wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Treat "env changed" as a warning, not a failure #813

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a9fb054
Treat "env changed" as a warning, not a failure
vstinner Oct 10, 2026
adb7c0c
typo
vstinner Oct 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion master/custom/steps.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -122,6 +122,9 @@ class Test(BaseTest):
decodeRC = {
0: SUCCESS,

# Do not mark "env changed" as a failure, but as a warning
3: WARNINGS, # EXITCODE_ENV_CHANGED

# Treat --fail-rerun exit code (5) to WARNINGS, when a test failed but
# passed when run again in verbose mode in a fresh process (unstable
# test).
Expand All @@ -131,7 +134,6 @@ class Test(BaseTest):
# So there is no need to map each regrtest exit code to FAILURE.
#
# 2: FAILURE, # EXITCODE_BAD_TEST
# 3: FAILURE, # EXITCODE_ENV_CHANGED
# 4: FAILURE, # EXITCODE_NO_TESTS_RAN
# 130: FAILURE, # EXITCODE_INTERRUPTED
}
Expand Down
Loading