fix: keep the user's HOME when wrapping commands with sudo

[lvaroqui]

Pass the bare --preserve-env to sudo alongside the explicit --preserve-env=<list>, so commands wrapped with sudo keep the invoking user's HOME again.

#574 switched to the list form because sudo-rs ignores the bare flag. With only the list, classic sudo keeps env_reset on, and in that mode variables exported by PAM session modules override the preserved ones (env_merge only skips variables in env_keep). Since systemd v260, pam_systemd always exports HOME with the target user's home directory, so on distros whose /etc/pam.d/sudo loads it (Arch: session optional pam_systemd.so class=none), wrapped commands ran with HOME=/root.

One visible effect: the walltime samply re-exec inherits CODSPEED_PROFILE, reads root's CodSpeed config, and fails with CodSpeed profile `<name>` does not exist when the profile only exists in the user's config. Anything else run through wrap_with_sudo that relies on the user's HOME (toolchains, caches) was affected too.

With both flags, classic sudo disables env_reset (as before #574) and sudo-rs still honors the list. HOME, CODSPEED_PROFILE and an arbitrary variable reach the command unchanged with both flags on:

sudo	before #574 (bare)	#574 (list)	this PR (both)
sudo-rs 0.2.13, Ubuntu 26.04 hosted runner and container	all dropped, HOME=/root	kept	kept
classic sudo (sudo.ws), Ubuntu 26.04	kept	kept	kept
classic sudo 1.9.15p5, Ubuntu 24.04	kept	kept	kept
classic sudo 1.9.17p2 + systemd 261, Arch	kept	HOME=/root	kept

Refs COD-3305: that issue tracks Ubuntu 26.04 support, which this keeps working while fixing a regression it introduced elsewhere.

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The change appears safe to merge.

Summary

Updates wrap_with_sudo to pass both forms of --preserve-env.

• Commands wrapped with sudo keep the caller’s environment.

_{Reviews (1) · Last reviewed commit: "fix: keep the user's HOME when wrapping ..." · Reviewed by Greptile}

[codspeed]

Merging this PR will not alter performance

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

⚠️ 8 benchmarks spent significant time in system calls

System calls cannot be consistently instrumented, so they are not included in the measure, which understates the real cost. Please switch to the Walltime instrument to accurately measure system calls.

Measurement and system calls

• encode_events_realistic[16]
• find_module_events_with_stacks[1000000]
• encode_events_realistic[1]
• encode_events_realistic[8]
• sleep 1
• encode_events_realistic[2]
• find_module_events[1000000]
• encode_events_realistic[4]

✅ 41 untouched benchmarks
⏩ 6 skipped benchmarks¹

---

_{Comparing fix/sudo-preserve-home (f52d120) with main (9e74317)}

Footnotes

1. 6 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[GuillaumeLagrange]

lgtm