Skip to content

ci(uat): measure the full-depth conformance cost nightly and raise the step budget #3609

Closed

Description

@yuanchen8911

Part of #3601. Scope set by #3619 (CNCF bar).

Summary

Nightly UAT keeps running aicr validate --phase all with every conformance check the recipe lists, at the depth the CNCF bar requires. No weekly lane, no depth tiers, no nightly --skip-check list. This issue measures the added cost and raises the step budget.

Constraint

The "UAT - validate (all phases)" step in .github/workflows/uat-aws.yaml has a 40-minute budget. The UAT cells have two GPU nodes (AWS desired: 2, GCP a3-megagpu-8g), so capacity is not the blocker. After #3603, #3604 and #3428 land, nightly adds one CPU gang Job, one HPA cycle on 2 GPUs, one TrainJob and gateway traffic on CPU backends, estimated at 5 to 8 minutes with the HPA scale-down as the long pole. Recipes that gain checks through #3605's wiring (EKS, AKS and NVKE training bases gain gang, HPA, secure access and cluster autoscaling) see the largest delta.

Change

  • Record the per-check durations from the nightly CTRF after each parity PR lands and attach them here.
  • Raise timeout-minutes on the validate step (and the job cap it sits under) to the measured need plus headroom.
  • --skip-check remains only for lanes that cannot host a check at all (Kind and KWOK leaves) and is never set on GPU cells.
  • The conformance checks run serially on a cell so one check's GPU hold is not misread by another.

Acceptance

  • Nightly passes within the raised budget for two consecutive nights with the full check set; durations are recorded on this issue.

Activity

  1. added theissue type on Nov 3, 2026
  2. changed the title [-]ci(uat): withhold the deep conformance tier nightly and add a full-depth lane[/-] [+]ci(uat): measure the full-depth conformance cost nightly and raise the step budget[/+] on Nov 4, 2026
  3. yuanchen8911 commented on Nov 7, 2026

    @yuanchen8911
    ContributorAuthor

    Budget raised in #3699 from measured nightly and AKS durations: validate step 40 to 50 minutes on AWS, Azure and GCP; job caps AWS 350, Azure 360, GCP 360. The two consecutive green nights with the full check set are confirmation, not a gate; the per-check duration table is in the PR's Testing section, and the budget drift items that remain are in #3705. Closing.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/citheme/ci-dxCI pipelines, developer experience, and build tooling

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions