test(integration_tests): add only_dir configuration to test_config.yaml

[PranjalC100]

Description

This PR updates tools/integration_tests/test_config.yaml to explicitly include the only_dir: "${ONLY_DIR}" field for several integration test suites. As noted in recent test framework discussions, the test framework automatically enables the only_dir execution mode if the test package contains this field.

This change ensures the following test suites include the only_dir mount configurations int test_config.yaml:

• inactive_stream_timeout
• flag_optimizations
• kernel_list_cache
• negative_stat_cache
• managed_folders

With this configuration update, we will now be running the only_dir tests for all 10 of the test packages that implement only_dir_mounting including :

• local_file
  *operations
  *read_cache
  *rename_dir_limit
  *requester_pays_bucket

Link to the issue in case of a bug fix.

Related to http://b/496966414

Testing details

1. Manual - NA
2. Unit tests - NA
3. Integration tests - NA

Any backward incompatible change? If so, please explain.

No.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 updates the integration test configuration to explicitly enable the 'only_dir' mounting mode for several test suites. By standardizing this configuration, the project ensures consistent test execution behavior across all relevant test packages, aligning with recent framework updates.

Highlights

• Configuration Update: Added the 'only_dir' field to five specific integration test suites in the test configuration file.
• Test Coverage: Ensures that 'only_dir' execution mode is enabled for these suites, bringing the total number of test packages supporting this configuration to 10.

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.

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]

Code Review

This pull request updates the integration test configuration in tools/integration_tests/test_config.yaml by adding the only_dir: "${ONLY_DIR}" parameter to several test suites, including inactive_stream_timeout, flag_optimizations, kernel_list_cache, negative_stat_cache, and managed_folders. I have no feedback to provide.