Skip to content

Conversation

@chang-wenbin
Copy link
Collaborator

@chang-wenbin chang-wenbin commented Feb 11, 2026

Motivation

为兼容不同的包结构环境,将依赖从“父包属性”迁移到“完整模块路径”,使导入逻辑在各种环境下都能稳定工作。
‘fp8_gemm_nt = fastdeploy.model_executor.layers.quantization.fp8_utils.deep_gemm.fp8_gemm_nt’
is not import,this PR add ’from fastdeploy.model_executor.layers.quantization.fp8_utils import deep_gemm‘

💡 If this PR is a Cherry Pick, the PR title needs to follow the format by adding the [Cherry-Pick] label at the very beginning and appending the original PR ID at the end. For example, [Cherry-Pick][CI] Add check trigger and logic(#5191)

💡 如若此PR是Cherry Pick,PR标题需遵循格式,在最开始加上[Cherry-Pick]标签,以及最后面加上原PR ID,例如[Cherry-Pick][CI] Add check trigger and logic(#5191)

Modifications

fix RL bug about blockwisefp8

Usage or Command

Accuracy Tests

Checklist

  • Add at least a tag in the PR title.
    • Tag list: [[FDConfig],[APIServer],[Engine], [Scheduler], [PD Disaggregation], [Executor], [Graph Optimization], [Speculative Decoding], [RL], [Models], [Quantization], [Loader], [OP], [KVCache], [DataProcessor], [BugFix], [Docs], [CI], [Optimization], [Feature], [Benchmark], [Others], [XPU], [HPU], [GCU], [DCU], [Iluvatar], [Metax]]
    • You can add new tags based on the PR content, but the semantics must be clear.
  • Format your code, run pre-commit before commit.
  • Add unit tests. Please write the reason in this PR if no unit tests.
  • Provide accuracy results.
  • If the current PR is submitting to the release branch, make sure the PR has been submitted to the develop branch, then cherry-pick it to the release branch with the [Cherry-Pick] PR tag.

@paddle-bot
Copy link

paddle-bot bot commented Feb 11, 2026

Thanks for your contribution!

Copy link
Collaborator

@zoooo0820 zoooo0820 left a comment

Choose a reason for hiding this comment

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

fastdeploy/model_executor/layers/moe/fused_moe_deepgemm_backend.py 中的groupgemm 也一起改下吧

zoooo0820
zoooo0820 previously approved these changes Feb 11, 2026
@codecov-commenter
Copy link

codecov-commenter commented Feb 11, 2026

Codecov Report

❌ Patch coverage is 70.00000% with 3 lines in your changes missing coverage. Please review.
⚠️ Please upload report for BASE (develop@e40fb16). Learn more about missing BASE report.

Files with missing lines Patch % Lines
...oy/model_executor/layers/quantization/fp8_utils.py 33.33% 2 Missing ⚠️
..._executor/layers/moe/fused_moe_deepgemm_backend.py 80.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             develop    #6466   +/-   ##
==========================================
  Coverage           ?   69.36%           
==========================================
  Files              ?      391           
  Lines              ?    52797           
  Branches           ?     8222           
==========================================
  Hits               ?    36622           
  Misses             ?    13511           
  Partials           ?     2664           
Flag Coverage Δ
GPU 69.36% <70.00%> (?)

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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

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.

4 participants