runbook: add ubuntu_azure_kernel_validate.yml with correct tier filtering

[Copilot]

When tier=0 was passed to the Ubuntu Azure kernel validation runbook, 300+ test cases were selected instead of the expected tier-0 subset, because the runbook lacked the ./tiers/tier.yml include that drives priority-based test selection.

Changes

• New file lisa/microsoft/runbook/ubuntu_azure_kernel_validate.yml: runbook for Ubuntu Azure kernel validation that correctly chains the tier mechanism
  • Includes ./tiers/tier.yml first — this dynamically loads t$(tier).yml, which sets the testcase.criteria.priority filter
  • Defines tier: 0 as the default (line 9); pass tier:N on the CLI to override
  • No standalone testcase section — avoids overriding the tier-resolved criteria

How tier filtering works

# ubuntu_azure_kernel_validate.yml
include:
  - path: ./tiers/tier.yml   # loads t0.yml when tier=0
  - path: ./azure.yml

variable:
  - name: tier
    value: 0                 # tier=0 → priority: 0 | tier=1 → priority: [0,1]

tiers/tier.yml → t$(tier).yml → testcase: criteria: priority: <N>. Without the tier.yml include, no testcase criteria is applied and the selector falls back to the full test catalogue.

Original prompt

fix it

[Chronological Review: The conversation began with the user questioning the selection of 300+ test cases when tier 0 is passed. The user then requested to continue iterating on a previous task. The conversation included attachments related to the repository "lisa" and a YAML configuration file. The user subsequently requested a fix for an unspecified issue in the YAML file, indicating a focus on the configuration settings for kernel validation.]

[Intent Mapping:

1. User requested clarification on the selection of test cases: "why a300+ testcases are selected when tier0 is passed."
2. User asked to continue iterating on a task: "Continue to iterate?"
3. User requested a fix for an issue in the YAML file: "fix it."]

[Technical Inventory:

• Repository: "lisa" owned by Microsoft, current branch is "20260521.1," default branch is "main."
• File: "ubuntu_azure_kernel_validate.yml" which includes various configurations for Azure kernel validation, including variables for test parameters and paths to included YAML files.]

[Code Archaeology:

• File: "ubuntu_azure_kernel_validate.yml"
  • Purpose: Configures the Azure kernel validation process.
  • Current State: User is focused on line 9, which contains the keyword "tier."
  • Key Code Segments: The file includes variables for test name, project, pass, and paths to other YAML files.
  • Dependencies: Relies on other YAML files for common tests and platform-specific configurations.]

[Progress Assessment:

• Completed Tasks: User has provided context and attachments related to the repository and YAML file.
• Partially Complete Work: User is currently addressing an issue in the YAML file and seeking clarification on test case selection.]

[Context Validation: All necessary context for continuing work on the YAML file and understanding the repository structure is captured.]

[Recent Commands Analysis:

• Last Agent Commands: The user requested a fix for the YAML file.
• Tool Results Summary: The most recent context included the user's active selection in the YAML file and the repository information.
• Pre-Summary State: The agent was actively working on the user's request to fix the YAML file when the token budget was exceeded.
• Operation Context: The user's commands were aimed at clarifying and fixing the configuration for kernel validation, which is crucial for their testing process.]

1. Conversation Overview: - Primary Objectives: 1. "why a300+ testcases are selected when tier0 is passed." 2. "Continue to iterate?" 3. "fix it." - Session Context: The conversation has revolved around understanding test case selection criteria and making adjustments to a YAML configuration file for Azure kernel validation. - User Intent Evolution: The user initially sought clarification on test cases, then moved to iterating on a task, and finally requested a fix for the YAML file.

2. Technical Foundation:

• Repository: "lisa" (Microsoft), current branch: "20260521.1," default branch: "main."
• File: "ubuntu_azure_kernel_validate.yml" - Configures Azure kernel validation with various test parameters.

3. Codebase Status:

• File Name: "ubuntu_azure_kernel_validate.yml"
  • Purpose: Configures the Azure kernel validation process.
  • Current State: User is focused on line 9, which contains the keyword "tier."
  • Key Code Segments: Includes variables for test name, project, pass, and paths to other YAML files.
  • Dependencies: Relies on other YAML files for common tests and platform-specific configurations.

4. Problem Resolution:

• Issues Encountered: User has identified a need for a fix in the YAML file.
• Solutions Implemented: None yet; the user has requested a fix.
• Debugging Context: The user is actively working on the YAML file to ensure proper configuration for kernel validation.

5. Progress Tracking:

• Completed Tasks: Context and attachments related to the repository and YAML file have been provided.
• Partially Complete Work: User is addressing an issue in the YAML file.
• Validated Outcomes: None yet; the user is still in the process of fixing the configuration.

6. Active Work State:

• Current Focus: The user is working on fixing the YAML file, specifically line 9.
• Recent Context: The user has provided context about the repository and the YAML file, indicating a focus on kernel validation.
• Working Code: The user is examining the "tier" configuration in the YAML file.
• Immediate Context: The user is seeking a fix for the YAML file to ensure proper kernel validation.

7. Recent Operations:

• Last Agent Commands: User requested a fix for the YAML file.
• Tool Results Summary: The user provided context about the repository and the YAML file, focusing on line 9.
• Pre-Summary State: The agent was actively addressing the user's request to fix the YAML file.
• Operation Context: The user's commands were aimed at clarifying and fixing the configuration for kernel validation.

8. Continuation Plan:

• Pending Task 1...

Created from VS Code.