Skip to content

Fix Hashing test ID to match repo standards - #6261

Open
RishabhAgarwal-2001 wants to merge 2 commits into
mainfrom
rishabh/fix-hashing-test-id
Open

RishabhAgarwal-2001 wants to merge 2 commits into
mainfrom
rishabh/fix-hashing-test-id

Conversation

@RishabhAgarwal-2001

Copy link
Copy Markdown
Contributor

No description provided.

@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 performs a minor update to the test identifier for the Dataplane Hashing test suite. By renaming the ID to 'Hashing-1.0', the change ensures consistency with the repository's established naming conventions for test plans and documentation.

Highlights

  • Test ID Standardization: Updated the test identifier for the Dataplane Hashing test from 'Hashing' to 'Hashing-1.0' across documentation and configuration files to align with repository standards.
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 test identifier and plan ID for the dataplane hashing test from 'Hashing' to 'Hashing-1.0' across the README, metadata, and test registry files. There are no review comments, and I have no feedback to provide.

@OpenConfigBot

OpenConfigBot commented Nov 9, 2026 •

Copy link
Copy Markdown

Pull Request Functional Test Report for #6261 / 4cfdd24

Virtual Devices

Device Test Status Test Documentation Job Raw Log
Arista cEOS status
Hashing-1.0: failure
Hashing-1.0: Dataplane Hashing with Physical Loopbacks
ae1a96d4 Log
Cisco 8000E status
Hashing-1.0: failure
Hashing-1.0: Dataplane Hashing with Physical Loopbacks
5446956b Log
Cisco XRd status
Hashing-1.0: failure
Hashing-1.0: Dataplane Hashing with Physical Loopbacks
76105d4f Log
Juniper ncPTX status
Hashing-1.0: failure
Hashing-1.0: Dataplane Hashing with Physical Loopbacks
8d27a4d7 Log
Nokia SR Linux status
Hashing-1.0: failure
Hashing-1.0: Dataplane Hashing with Physical Loopbacks
aed6da3a Log
Openconfig Lemming status
Hashing-1.0: failure
Hashing-1.0: Dataplane Hashing with Physical Loopbacks
c99b8f1f Log

Hardware Devices

Device Test Status Test Documentation Raw Log
Arista status
Hashing-1.0: pending authorization
Hashing-1.0: Dataplane Hashing with Physical Loopbacks
Cisco status
Hashing-1.0: pending authorization
Hashing-1.0: Dataplane Hashing with Physical Loopbacks
Juniper status
Hashing-1.0: pending authorization
Hashing-1.0: Dataplane Hashing with Physical Loopbacks
Nokia status
Hashing-1.0: pending authorization
Hashing-1.0: Dataplane Hashing with Physical Loopbacks

Help

This branch has not been deployed

No deployments
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