Skip to content

Run only basic tests under the podman friends plan#4581

Merged
psss merged 1 commit intomainfrom
psss-podman-friends-plan
Feb 13, 2026
Merged

Run only basic tests under the podman friends plan#4581
psss merged 1 commit intomainfrom
psss-podman-friends-plan

Conversation

@psss
Copy link
Contributor

@psss psss commented Feb 13, 2026

Recent addition of the new environment test caused many failures in the podman repository as the change is not released yet. Let's keep the friends plan focused on the essential features only.

Pull Request Checklist

  • adjust the test coverage

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @psss, 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 recent failures in the podman friends plan by adjusting the test suite's execution scope. It specifically targets a new environment test that introduced instability due to its reliance on unreleased features. The change ensures that the podman friends plan focuses solely on core functionalities, thereby preventing disruptions and maintaining a stable testing environment.

Highlights

  • Test Plan Scope Adjustment: The podman tag has been removed from the tests/provision/container/environment/main.fmf test plan. This change prevents a newly added environment test from running within the podman friends plan, which was causing failures due to unreleased changes.
  • Stability Improvement: By narrowing the scope of tests executed in the podman friends plan to only essential features, the pull request aims to improve the stability and reliability of the continuous integration process for the Podman repository.
Changelog
  • tests/provision/container/environment/main.fmf
    • Removed the 'podman' tag from the test plan metadata.
Activity
  • The pull request was opened by psss with an initial description outlining the problem and proposed solution.
  • No human activity (comments, reviews, or further commits) has occurred since the pull request was created.
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.

@psss psss added step | provision Stuff related to the provision step plugin | container The podman plugin used for container provision labels Feb 13, 2026
@psss psss requested a review from thrix February 13, 2026 11:49
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 removes the podman tag from the tests/provision/container/environment/main.fmf test definition. This change will exclude the test from the podman friends plan, which discovers tests using this tag. According to the description, this is intended to resolve CI failures in the podman repository due to a dependency on an unreleased feature. The change is correct and effectively implements the desired exclusion.

@psss psss added the ci | full test Pull request is ready for the full test execution label Feb 13, 2026
Recent addition of the new environment test caused many failures
in the podman repository as the change is not released yet. Let's
keep the friends plan focused on the essential features only.
@psss psss force-pushed the psss-podman-friends-plan branch from 1ea1ebf to a9da41a Compare February 13, 2026 13:22
@psss psss added this to planning Feb 13, 2026
@github-project-automation github-project-automation bot moved this to backlog in planning Feb 13, 2026
@psss psss moved this from backlog to merge in planning Feb 13, 2026
@psss psss added this to the 1.68 milestone Feb 13, 2026
@psss psss merged commit f94ae47 into main Feb 13, 2026
30 checks passed
@psss psss deleted the psss-podman-friends-plan branch February 13, 2026 16:17
@github-project-automation github-project-automation bot moved this from merge to done in planning Feb 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci | full test Pull request is ready for the full test execution plugin | container The podman plugin used for container provision step | provision Stuff related to the provision step

Projects

Status: done

Development

Successfully merging this pull request may close these issues.

3 participants