Skip to content

test(fs/handle): fix BufferedReader resource leak timeout in file_test#4818

Merged
geertj merged 1 commit into
GoogleCloudPlatform:masterfrom
geertj:test-buffered-reader-leak
Jul 1, 2026
Merged

test(fs/handle): fix BufferedReader resource leak timeout in file_test#4818
geertj merged 1 commit into
GoogleCloudPlatform:masterfrom
geertj:test-buffered-reader-leak

Conversation

@geertj

@geertj geertj commented Jun 27, 2026

Copy link
Copy Markdown
Collaborator

In Test_ReadWithReadManager_ConcurrentReadsWithBufferedReader: Added invocation of resp.Callback() after validating each read response to correctly release outstanding data slice references held by the BufferedReader.

Without this callback, BufferedReader.Destroy would wait until a 10-second timeout expired before releasing resources, causing the test case to hang for 10.15 seconds and print a warning. With the callback, the test executes cleanly in 0.15s (a ~67x speedup).

TAG=agy
CONV=8c7b5ab6-91ae-4a84-911e-1788917d5ab8

@geertj geertj requested a review from a team as a code owner June 27, 2026 22:58
@geertj geertj requested a review from vadlakondaswetha June 27, 2026 22:58
@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 addresses a resource management issue within the file system handle tests. By ensuring the response callback is triggered after processing read responses, the test suite no longer waits for a timeout to release resources, resulting in a significant improvement in test execution performance.

Highlights

  • Resource Leak Fix: Added a callback invocation in the concurrent read test to ensure that data slice references are released promptly.
  • Performance Improvement: Eliminated a 10-second timeout in the test suite, reducing execution time from over 10 seconds to approximately 0.15 seconds.
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 the 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 counterproductive. 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.

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.

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

Copy link
Copy Markdown
Contributor

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 updates the concurrent read test Test_ReadWithReadManager_ConcurrentReadsWithBufferedReader in internal/fs/handle/file_test.go to invoke the response callback if it is present. There are no review comments, so I have no feedback to provide.

@geertj geertj requested a review from charith87 June 29, 2026 19:30
Comment thread internal/fs/handle/file_test.go Outdated
In Test_ReadWithReadManager_ConcurrentReadsWithBufferedReader:
Added invocation of resp.Callback() after validating each read response to
correctly release outstanding data slice references held by the
BufferedReader.

Without this callback, BufferedReader.Destroy would wait until a 10-second
timeout expired before releasing resources, causing the test case to hang for
10.15 seconds and print a warning. With the callback, the test executes
cleanly in 0.15s (a ~67x speedup).

TAG=agy
CONV=8c7b5ab6-91ae-4a84-911e-1788917d5ab8
@geertj geertj force-pushed the test-buffered-reader-leak branch from 76422bf to 2b52621 Compare June 30, 2026 12:06
@charith87 charith87 self-requested a review June 30, 2026 15:58
@geertj geertj merged commit 94d6668 into GoogleCloudPlatform:master Jul 1, 2026
12 checks passed
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