Skip to content

FIx CI, add 910B4-1 template and fix vGPUmonitor metrics error - #1345

Merged
hami-robot[bot] merged 3 commits into
Project-HAMi:masterfrom
archlitchi:master
Sep 14, 2025
Merged

FIx CI, add 910B4-1 template and fix vGPUmonitor metrics error#1345
hami-robot[bot] merged 3 commits into
Project-HAMi:masterfrom
archlitchi:master

Conversation

@archlitchi

Copy link
Copy Markdown
Member

/kind bug

  1. Fix Ci which blocks HAMi from building
  2. add 910B4-1 template
  3. fix vGPUmonitor metrics error

Signed-off-by: limengxuan <mengxuan.li@dynamia.ai>
@hami-robot hami-robot Bot added kind/bug Something isn't working dco-signoff: yes labels Sep 12, 2025
@hami-robot hami-robot Bot added the approved label Sep 12, 2025
@github-actions github-actions Bot removed the kind/bug Something isn't working label Sep 12, 2025
@hami-robot hami-robot Bot added the size/M label Sep 12, 2025

@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.

Summary of Changes

Hello @archlitchi, 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 focuses on enhancing the stability and expanding the capabilities of the HAMi project. It resolves critical CI build failures, introduces support for a new hardware template, and corrects an error in the vGPU monitoring metrics to ensure accurate resource reporting.

Highlights

  • CI Fixes: Addressed issues that were blocking HAMi from building, ensuring the continuous integration pipeline functions correctly.
  • New Hardware Support: Integrated configuration for the Ascend910B4-1 chip, including its resource definitions and virtual GPU templates, expanding hardware compatibility.
  • vGPU Monitor Metrics Correction: Rectified an error in the vGPU monitor metrics calculation to ensure accurate reporting of resource usage.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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.

@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 introduces several changes: it fixes a CI issue by removing an unused parameter, adds a new device template for 910B4-1, and corrects an error in vGPU monitor metrics calculation. The changes look good overall. My main feedback is on the metrics fix in pkg/monitor/nvidia/v1/spec.go. While the fix is correct, it can be made more robust to prevent potential panics from out-of-bounds slicing. I've added a comment with a suggestion to add a bounds check, and also proposed a refactoring that would improve code quality by reducing duplication and centralizing the fix.

Comment thread pkg/monitor/nvidia/v1/spec.go
Signed-off-by: limengxuan <mengxuan.li@dynamia.ai>
@codecov

codecov Bot commented Sep 12, 2025

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag Coverage Δ
unittests 64.04% <100.00%> (-0.99%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
pkg/device/enflame/gcu.go 94.82% <100.00%> (ø)
pkg/monitor/nvidia/v1/spec.go 94.59% <100.00%> (ø)

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment thread pkg/device/enflame/gcu_test.go Outdated
Signed-off-by: limengxuan <mengxuan.li@dynamia.ai>
@archlitchi

Copy link
Copy Markdown
Member Author

CC @Shouren

@wawa0210

Copy link
Copy Markdown
Member

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


cc @s

@Shouren Shouren left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@hami-robot hami-robot Bot added the lgtm label Sep 14, 2025
@hami-robot

hami-robot Bot commented Sep 14, 2025

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: archlitchi, Shouren

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@hami-robot
hami-robot Bot merged commit 0fa3c8f into Project-HAMi:master Sep 14, 2025
17 checks passed
@fishman fishman mentioned this pull request Jul 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants