Skip to content

Comments

ci: automate high-risk suite validation for beta sign-off#796

Open
adolago wants to merge 1 commit intomainfrom
issue-792-high-risk-suites
Open

ci: automate high-risk suite validation for beta sign-off#796
adolago wants to merge 1 commit intomainfrom
issue-792-high-risk-suites

Conversation

@adolago
Copy link
Owner

@adolago adolago commented Feb 23, 2026

Summary

  • add a dedicated high-risk CI workflow that automates SSH, WinRM, HPC, and fuzz suites
  • provide profile-based execution (scheduled-smoke and beta-signoff) with explicit smoke/full reporting
  • enforce full SSH/WinRM coverage in beta sign-off mode and publish aggregate suite status
  • document required suites and CI vars/secrets for beta sign-off

Closes #792

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a305733217

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +87 to +88
if ! [[ "$proptest_cases" =~ ^[0-9]+$ ]]; then
echo "::error::proptest_cases must be a positive integer, got '$proptest_cases'"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Disallow zero PROPTEST_CASES in profile validation

The input validation accepts proptest_cases=0 because it only checks for digits, but that value is later forwarded to PROPTEST_CASES in the fuzz job, which lets proptest run zero generated cases and still report success. In a workflow_dispatch or workflow_call run, this can let beta sign-off pass with effectively no fuzz coverage, which defeats the purpose of this workflow; require a strictly positive value (e.g., ^[1-9][0-9]*$) before writing the output.

Useful? React with 👍 / 👎.

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.

Automate currently manual high-risk test suites before beta

1 participant