Skip to content

[ci-coach] Fix failing test-unit: concurrency queue expressions and docker image spec #65868

Description

@github-actions

Tip

Your pull request is ready to create! 🎉 ✅

Everything is OK—the changes have been pushed to a branch. Please review the protected files, then create the pull request when you are ready.

Create the pull request

The original pull request description is below.


CI Optimization Proposal: fix failing test-unit

Pre-flight validation showed every step passing except test-unit (2 failing tests).

Fixes

  • TestConcurrencyQueueSchemaValidation: the embedded github-workflow.json schema only allowed queue: single|max, rejecting expressions such as ${{ ... }}. The schema now accepts the enum or expressionSyntax, as cancel-in-progress does. Invalid literals are still rejected.
  • TestSpec_Constants_DockerImages: the test and pkg/cli/README.md still documented :latest images, while the constants are version/digest-pinned. The spec test and README now match docker_images.go.

Validation

  • go test ./pkg/cli -run TestSpec_Constants_DockerImages and go test ./pkg/workflow -run Concurrency pass.
  • Full ./pkg/workflow and ./pkg/cli runs still show other failures that were not in the CI results (TestVerifyGitCredentials*, TestCloudHypervisorSetupBundle*, TestBuildDynamicEnclaveExpiry*, TestRenderScheduleCalendarCell_*, TestConfirmRunAddedWorkflow_ContextCancelled). They look environment-specific and I did not change them.

Note

Protected files

This patch modifies protected files, which may affect project dependencies, CI/CD pipelines, or agent behaviour.

Protected files
  • README.md

To route changes like this to a review issue instead of blocking, configure protected-files: fallback-to-issue in your workflow configuration.

Generated by CI Optimization Coach · copilot · auto · 28.5 AIC · ⌖ 20.4 AIC · ⊞ 16.6K · ◷

  • expires on Oct 7, 2026, 5:45 AM UTC-08:00

Activity

  1. github-actions commented on Oct 7, 2026

    @github-actions
    ContributorAuthor

    This issue was automatically closed because it expired on 2026-10-07T13:45:31.901Z.

    Closed by Workflow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions