Skip to content

chore(ci): fix flaky key mappings pagination test#753

Merged
jakedoublev merged 4 commits intomainfrom
fix/DSPX-2367
Feb 19, 2026
Merged

chore(ci): fix flaky key mappings pagination test#753
jakedoublev merged 4 commits intomainfrom
fix/DSPX-2367

Conversation

@jakedoublev
Copy link
Contributor

@jakedoublev jakedoublev commented Feb 19, 2026

Updates test to ensure pagination limit/offset flags drive resulting JSON output and are consistent.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @jakedoublev, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a persistent flakiness issue in the end-to-end tests for KAS key mappings pagination. By explicitly passing the KAS registry ID to the list-mappings commands, the tests now consistently target the intended environment, leading to more reliable CI results and preventing intermittent failures.

Highlights

  • Test Flakiness Fix: Addressed flakiness in the kas-keys-mappings: list key mappings with pagination end-to-end test by explicitly specifying the KAS registry ID.
  • Command Parameter Update: Modified run_otdfctl_key list-mappings commands within the test to include the --kas "${KAS_REGISTRY_ID}" flag, ensuring commands target the correct registry.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • e2e/kas-keys-mappings.bats
    • Added the --kas flag with the KAS_REGISTRY_ID variable to list-mappings commands in the pagination test.
    • Removed a trailing blank line at the end of the file.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

The pull request addresses a flaky key mappings pagination test by explicitly including the --kas flag with the ${KAS_REGISTRY_ID} in the list-mappings commands. This change improves the test's reliability and ensures it targets the correct KAS registry. A trailing blank line was also removed, which is a minor cleanup. The changes are clear and directly resolve the reported flakiness.

@github-actions
Copy link

@github-actions
Copy link

@github-actions
Copy link

@jakedoublev jakedoublev marked this pull request as ready for review February 19, 2026 20:30
@jakedoublev jakedoublev requested a review from a team as a code owner February 19, 2026 20:30
@github-actions
Copy link

@jakedoublev jakedoublev enabled auto-merge (squash) February 19, 2026 20:35
@jakedoublev jakedoublev merged commit 5f2acd4 into main Feb 19, 2026
21 checks passed
@jakedoublev jakedoublev deleted the fix/DSPX-2367 branch February 19, 2026 20:37
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.

2 participants