Skip to content

tests: unset some envs instead of blanking them#17994

Closed
vszakats wants to merge 2 commits intocurl:masterfrom
vszakats:t-remove-env
Closed

tests: unset some envs instead of blanking them#17994
vszakats wants to merge 2 commits intocurl:masterfrom
vszakats:t-remove-env

Conversation

@vszakats
Copy link
Member

@vszakats vszakats commented Jul 22, 2025

After 7cf8414 #12862, VAR= no longer
removes the env variable, but sets it to an empty/blank value instead.
To remove an env, VAR shall be used (without the assigment operator.)

SSL_CERT_FILE, CURL_HOME, HOME, XDG_CONFIG_HOME, were added
before the change above. Make tests unset these envs again, as their
commit messages suggest, instead of blanking them. It does not change
the outcome of the tests.

Ref: 764e4f0 #8213
Ref: e992770 #6600

Folllow-up to 7cf8414 #12862
Cherry-picked from #17988

vszakats added 2 commits July 22, 2025 12:29
These were added after the `ENV=` == blank change, but meant as a removal
(unset / not set) according to the commit messages

764e4f0
e992770
@vszakats vszakats added the tests label Jul 22, 2025
@vszakats vszakats changed the title tests: unset some variables instead of blanking them tests: unset some envs instead of blanking them Jul 22, 2025
@vszakats vszakats closed this in 1074d6d Jul 23, 2025
@vszakats vszakats deleted the t-remove-env branch July 23, 2025 20:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

1 participant

Comments