Repository navigation
[Tests] GetProcessTmpDir_ChildProcess_ReadsTmpdir fails with Assert.Equal() Failure #5750
Description
Activity
- added a commit that references this issue
on Mar 12, 2026 Additional data from rolling CI analysis:
This also reproduces on Alpine 3.19 x64, not just Ubuntu 22.04. Same exact failure —
Assert.Equalexpecting/custom/tmp/test, getting/tmp/. Seen in:Possible race condition: The test has no delay between
Process.Start(psi)and callingGetProcessTmpDir(child.Id, ...). On Linux,/proc/{pid}/environmay not immediately reflect the child's environment if the read happens betweenfork()andexec(). A short polling loop or delay after start may help.Note: the #5751 diagnostics have not yet triggered on these legs because the most recent builds (1332940) are dominated by the SOS DAC loading failure (#5757), which masks this test.
Extended error message:
Expected '/custom/tmp/test' but got '/tmp/'. Child PID: 16253, child exited: False, environ path: /proc/16253/environ, environ permissions: UserRead, parent TMPDIR: '(not set)', psi.Environment TMPDIR: '/custom/tmp/test', current user: cloudtest_azpcontainer, environ size: 0 bytes, env var count: 0, TMPDIR entry: '(not found)', first 200 chars of environ: ''- linked a pull request that will close this issuePoll for environment available in test process startup in GetProcessTmpDir tests #5782
on Mar 28, 2026 - locked and limited conversation to collaborators
on May 2, 2026
The
GetProcessTmpDir_ChildProcess_ReadsTmpdirunit test (introduced in #5735) fails intermittently on the Ubuntu 22.04 x64 CI leg. The test spawns a child process withTMPDIR=/custom/tmp/testviaProcessStartInfo.Environment, then verifies thatGetProcessTmpDirreadsthe custom value from
/proc/{pid}/environ.Failure
Assert.Equal() Failure: Strings differ ↓ (pos 1) Expected: "/custom/tmp/test" Actual: "/tmp/" ↑ (pos 1)
The environ file was successfully read (
environReadable = true), but the parsed TMPDIR was/tmp/(thePath.GetTempPath()fallback) instead of the custom value set viaProcessStartInfo.Environment.Possible Causes
/proc/{pid}/environmay not reflect the overridden environment if read beforeexecvecompletes/proc/{pid}/environProcessStartInfo.Environmentoverride may not propagate in certain CI environments