Skip to content

ci: temporarily disable bigquery integration tests#2688

Merged
Yuan325 merged 1 commit intomainfrom
bq-int-test
Mar 9, 2026
Merged

ci: temporarily disable bigquery integration tests#2688
Yuan325 merged 1 commit intomainfrom
bq-int-test

Conversation

@Yuan325
Copy link
Copy Markdown
Contributor

@Yuan325 Yuan325 commented Mar 9, 2026

No description provided.

@Yuan325 Yuan325 requested a review from a team as a code owner March 9, 2026 21:49
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, 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 adjusts the continuous integration configuration to enhance build stability. It modifies the BigQuery integration tests to be non-blocking, preventing their potential flakiness from halting the CI pipeline. Additionally, it updates the comment for the Spanner integration tests to specifically reference an open issue for addressing their known flakiness.

Highlights

  • BigQuery Integration Tests: The BigQuery integration tests in the CI pipeline were modified to be non-blocking, meaning their failures will no longer prevent the overall build from passing. A TODO comment was added, linking to issue bigquery CA integration test response mismatch #2687 to track fixing their flakiness.
  • Spanner Integration Tests: The existing non-blocking Spanner integration tests had their comment updated to reference issue Spanner Integration Test re-enable #2420, which tracks fixing their flakiness.
Changelog
  • .ci/integration.cloudbuild.yaml
    • Configured BigQuery integration tests to report failures without stopping the build.
    • Updated the comment for Spanner integration tests to reference a specific issue for flakiness.
Activity
  • No specific activity has been recorded for this pull request yet.
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
Copy Markdown
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

This pull request temporarily disables the BigQuery integration tests in the CI pipeline to mitigate flakiness. This is achieved by allowing the test step to succeed even if the tests fail. A TODO comment with a link to a tracking issue has been added to ensure this is addressed later. A similar change updates the comment for the already-disabled Spanner tests to include a tracking issue as well.

@Yuan325 Yuan325 enabled auto-merge (squash) March 9, 2026 22:10
@Yuan325 Yuan325 merged commit cd8e467 into main Mar 9, 2026
19 checks passed
@Yuan325 Yuan325 deleted the bq-int-test branch March 9, 2026 22:11
dumians pushed a commit to dumians/genai-toolbox that referenced this pull request Mar 12, 2026
NirajNandre pushed a commit to NirajNandre/genai-toolbox-fork that referenced this pull request Mar 24, 2026
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.

3 participants