ci: temporarily disable bigquery integration tests#2688
Conversation
Summary of ChangesHello, 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
Changelog
Activity
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
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.
No description provided.