Skip to content

[Cherry-Pick][BugFix] fix rl model_weights_signal to support tp>1#5650

Merged
yuanlehome merged 1 commit intoPaddlePaddle:release/2.4from
yuanlehome:fix_2.4_rl_signal_1
Dec 19, 2025
Merged

[Cherry-Pick][BugFix] fix rl model_weights_signal to support tp>1#5650
yuanlehome merged 1 commit intoPaddlePaddle:release/2.4from
yuanlehome:fix_2.4_rl_signal_1

Conversation

@yuanlehome
Copy link
Collaborator

Motivation

💡 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

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 Dec 19, 2025

Thanks for your contribution!

@yuanlehome yuanlehome merged commit b3f7881 into PaddlePaddle:release/2.4 Dec 19, 2025
4 of 7 checks passed
@yuanlehome yuanlehome deleted the fix_2.4_rl_signal_1 branch December 19, 2025 04:04
@yuanlehome yuanlehome changed the title update rl signal [Cherry-Pick][BugFix] fix rl model_weights_signal to support tp>1 Dec 19, 2025
@codecov-commenter
Copy link

Codecov Report

❌ Patch coverage is 0% with 4 lines in your changes missing coverage. Please review.
⚠️ Please upload report for BASE (release/2.4@23bfd28). Learn more about missing BASE report.

Files with missing lines Patch % Lines
fastdeploy/worker/worker_process.py 0.00% 4 Missing ⚠️
Additional details and impacted files
@@              Coverage Diff               @@
##             release/2.4    #5650   +/-   ##
==============================================
  Coverage               ?   58.95%           
==============================================
  Files                  ?      327           
  Lines                  ?    40758           
  Branches               ?     6198           
==============================================
  Hits                   ?    24027           
  Misses                 ?    14855           
  Partials               ?     1876           
Flag Coverage Δ
GPU 58.95% <0.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.

2 participants