Skip to content

Run resolver test stubs through the shell - #631

Merged
tinder-maxwellelliott merged 1 commit into
Tinder:masterfrom
tamird:codex/resolver-test-shell-20261106
Nov 6, 2026
Merged

tinder-maxwellelliott merged 1 commit into
Tinder:masterfrom
tamird:codex/resolver-test-shell-20261106

Conversation

@tamird

@tamird tamird commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

The four Unix tests that share the resolver stub execute a newly written temporary file. Two Linux CI runs lost the initial mapping invocation. The resolver uses an empty mapping after a command failure, so the fallback query in #630 still found the requested repository. These jobs did not record the underlying errno. 1 2

Extend #568’s fix to this shared stub. Run a fixed script through the installed /bin/sh and pass the log path, mock response and Bazel arguments separately. The tests still check the full sequence of commands, including caller-supplied startup options and the empty root repository argument.

Assisted by Codex.

The shared Unix resolver stub runs from a newly written executable.
Two Linux CI failures lost its first mapping invocation. The resolver
accepts an empty mapping when the command fails, so a later successful
lookup can leave the missing log entry as the only evidence.

Apply aa005b3's shell-execution approach to the four remaining
callers of this stub. Run /bin/sh with a fixed script and pass the log
path, response and Bazel arguments separately.

Assisted by Codex.
@tinder-maxwellelliott
tinder-maxwellelliott merged commit da5120f into Tinder:master Nov 6, 2026
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants