Skip to content

chore: remove 3.9 samples test#1957

Closed
daniel-sanche wants to merge 1 commit intomainfrom
remove-39
Closed

chore: remove 3.9 samples test#1957
daniel-sanche wants to merge 1 commit intomainfrom
remove-39

Conversation

@daniel-sanche
Copy link
Collaborator

Python 3.9 has been removed from kookoro. This PR removes the 3.9 samples CI test

@daniel-sanche daniel-sanche requested review from a team as code owners February 13, 2026 22:03
@product-auto-label product-auto-label bot added the samples Issues that are directly related to samples. label Feb 13, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @daniel-sanche, 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 streamlines the continuous integration pipeline by removing all configurations associated with Python 3.9 sample tests. This change reflects the deprecation of Python 3.9 support within the kookoro environment, ensuring that the CI system no longer attempts to run tests against an unsupported Python version.

Highlights

  • Python 3.9 CI Test Removal: Removed all Kokoro CI configurations related to Python 3.9 sample tests, as Python 3.9 is no longer supported in the kookoro environment.
Changelog
  • .kokoro/samples/python3.9/common.cfg
    • Removed the common configuration for Python 3.9 sample tests.
  • .kokoro/samples/python3.9/continuous.cfg
    • Removed the continuous integration configuration for Python 3.9 sample tests.
  • .kokoro/samples/python3.9/periodic-head.cfg
    • Removed the periodic-head configuration for Python 3.9 sample tests.
  • .kokoro/samples/python3.9/periodic.cfg
    • Removed the periodic configuration for Python 3.9 sample tests.
  • .kokoro/samples/python3.9/presubmit.cfg
    • Removed the presubmit configuration for Python 3.9 sample tests.
Activity
  • No human activity detected in this pull request.
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
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 correctly removes the Kokoro CI configuration for Python 3.9 sample tests. Given the PR description that 'Python 3.9 has been removed from kookoro', the removal seems incomplete. To fully remove Python 3.9 support, you might also need to remove '3.9' from UNIT_TEST_PYTHON_VERSIONS in noxfile.py and delete the corresponding testing/constraints-3.9.txt file.

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

Labels

samples Issues that are directly related to samples.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant