Skip to content

Conversation

@stankiewicz
Copy link
Contributor

bigquery_file_loads_test.py::TestBigQueryFileLoads::test_multiple_identical_destinations_on_write_truncate was flaky due to reshuffle inside BQ IO and assumption that input row will get always same job id from mock. Once order changed, asserts fail.

Please add a meaningful description for your change here


Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

  • Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
  • Update CHANGES.md with noteworthy changes.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

Build python source distribution and wheels
Python tests
Java tests
Go tests

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

…t specific job id based on which we have assert.
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @stankiewicz, 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 aims to stabilize the test_multiple_identical_destinations_on_write_truncate test in the BigQuery file loads module. The test was intermittently failing due to an assumption about job ID assignment within its mock implementation, which was susceptible to changes in processing order. By making the mock's job ID generation deterministic, the change ensures reliable test execution and prevents future flakiness.

Highlights

  • Flaky Test Fix: The pull request resolves a flakiness issue in the test_multiple_identical_destinations_on_write_truncate test by addressing non-deterministic behavior in its mock setup.
  • Mock Job ID Consistency: The mock jobId generation within the test has been modified to consistently return job_name1, removing the previous variation (job_name2, job_name3) that led to flakiness.
  • Assertion Alignment: Corresponding assertions for TableReference objects have been updated to expect job_name1, aligning with the new deterministic mock behavior.
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.

@stankiewicz
Copy link
Contributor Author

R: @portikCoder

@github-actions
Copy link
Contributor

github-actions bot commented Oct 6, 2025

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment assign set of reviewers

@liferoad liferoad merged commit 25f6552 into apache:master Oct 6, 2025
103 of 114 checks passed
mock_jobs = [
Mock(jobReference=bigquery_api.JobReference(jobId=f'job_name{i}'))
# Order matters in a sense to prove that jobs with different ids
# (`2` & `3`) are run with `WRITE_APPEND` without this current fix.
Copy link
Contributor

Choose a reason for hiding this comment

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

Minor but now my comments became a hunter for inattentive devs 😅

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants