[Test] Loosen managed-job --tail invalid-int assertion

[kevinmingtarja]

Summary

test_managed_jobs_logs_tail verifies that sky jobs logs --tail <non-integer>
is rejected. The assertion grepped for the exact error string
(is not a valid integer), which is more brittle than the test intends — the
point is that the bad value is rejected, not the exact wording the integer
parser uses to report it.

This relaxes the grep to match the rejection by the integer parser without
pinning the exact wording, while staying specific enough to avoid matching
unrelated errors that merely contain "invalid" (e.g. a job-id error).

Test plan

• Test-only; no product behavior change.
• The relaxed pattern (grep -iE "invalid.*(int|num|tail)|not a valid") still
  matches the current error output, so the rejection continues to be asserted.

[gemini-code-assist]

Code Review

This pull request updates a smoke test in tests/smoke_tests/test_managed_job.py to make the validation of CLI argument parser errors more flexible by using a case-insensitive regex pattern. The reviewer noted that the new pattern "invalid|not a valid" is too broad and could cause false positives, such as matching unrelated errors like "Invalid job ID". They suggested a more specific regex pattern to target integer, numeric, or tail-related validation errors.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.