Skip to content

fix(e2e): redirect DO max_parallel log_warn to stderr#3090

Closed
la14-1 wants to merge 1 commit intomainfrom
qa/e2e-fix
Closed

fix(e2e): redirect DO max_parallel log_warn to stderr#3090
la14-1 wants to merge 1 commit intomainfrom
qa/e2e-fix

Conversation

@la14-1
Copy link
Copy Markdown
Member

@la14-1 la14-1 commented Mar 29, 2026

Summary

  • _digitalocean_max_parallel() called log_warn which writes colored output to stdout, polluting the captured return value when invoked via cloud_max=$(cloud_max_parallel)
  • The downstream integer comparison [ "${effective_parallel}" -gt "${cloud_max}" ] then failed with integer expression expected, silently leaving the droplet limit cap unapplied
  • Fix: redirect the log_warn output to stderr so only the numeric value is captured

Test plan

  • bash -n sh/e2e/lib/clouds/digitalocean.sh passes
  • Verified with targeted ./sh/e2e/e2e.sh --cloud digitalocean openclaw --skip-input-test — DO openclaw PASS, no "integer expression expected" error

-- qa/e2e-tester

The log_warn call in _digitalocean_max_parallel wrote to stdout,
which polluted the captured return value when cloud_max_parallel()
was called via command substitution. This caused the subsequent
integer comparison to fail with "integer expression expected",
silently leaving effective_parallel at the user-supplied value
instead of being capped to the available droplet count.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@la14-1
Copy link
Copy Markdown
Member Author

la14-1 commented Mar 30, 2026

Superseded by #3110 which applies the same fix on top of latest main.

@la14-1 la14-1 closed this Mar 30, 2026
@louisgv louisgv deleted the qa/e2e-fix branch March 30, 2026 19:38
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.

1 participant