Skip to content

Bugfix: deepseek benchmark names conflict#725

Merged
polarG merged 1 commit into
release/0.12from
hongtaozhang/fix-deepseek-name-conflict
Jul 31, 2025
Merged

Bugfix: deepseek benchmark names conflict#725
polarG merged 1 commit into
release/0.12from
hongtaozhang/fix-deepseek-name-conflict

Conversation

@polarG

@polarG polarG commented Jul 31, 2025

Copy link
Copy Markdown
Contributor

Summary
Deepseek currently registers two benchmarks using the same identifier, causing a naming conflict.

Change
Rename each benchmark so that both have unique, descriptive names.

@polarG polarG requested a review from a team as a code owner July 31, 2025 00:07
@codecov

codecov Bot commented Jul 31, 2025

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.47%. Comparing base (44e35cd) to head (b1d60db).
⚠️ Report is 1 commits behind head on release/0.12.

Additional details and impacted files
@@              Coverage Diff              @@
##           release/0.12     #725   +/-   ##
=============================================
  Coverage         86.47%   86.47%           
=============================================
  Files               102      102           
  Lines              7541     7541           
=============================================
  Hits               6521     6521           
  Misses             1020     1020           
Flag Coverage Δ
cpu-python3.10-unit-test 71.59% <ø> (ø)
cpu-python3.12-unit-test 71.59% <ø> (ø)
cpu-python3.7-unit-test 70.65% <ø> (ø)
cuda-unit-test 83.98% <ø> (ø)

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.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@polarG polarG merged commit d724546 into release/0.12 Jul 31, 2025
23 of 32 checks passed
@polarG polarG deleted the hongtaozhang/fix-deepseek-name-conflict branch July 31, 2025 20:16
polarG added a commit that referenced this pull request Aug 12, 2025
Summary
Deepseek currently registers two benchmarks using the same identifier,
causing a naming conflict.

Change
Rename each benchmark so that both have unique, descriptive names.

Co-authored-by: Hongtao Zhang <hongtaozhang@microsoft.com>
polarG added a commit that referenced this pull request Aug 12, 2025
**Description**

Cherry-pick bug fixes from v0.12.0 to main.

**Major Revisions**

* #725
* #727
* #728

Co-authored-by: Hongtao Zhang <hongtaozhang@microsoft.com>
Co-authored-by: Yifan Xiong <yixio@microsoft.com>
Co-authored-by: Guoshuai Zhao <guzhao@microsoft.com>

---------

Co-authored-by: Hongtao Zhang <hongtaozhang@microsoft.com>
Aishwarya-Tonpe pushed a commit that referenced this pull request Aug 16, 2025
**Description**

Cherry-pick bug fixes from v0.12.0 to main.

**Major Revisions**

* #725
* #727
* #728

Co-authored-by: Hongtao Zhang <hongtaozhang@microsoft.com>
Co-authored-by: Yifan Xiong <yixio@microsoft.com>
Co-authored-by: Guoshuai Zhao <guzhao@microsoft.com>

---------

Co-authored-by: Hongtao Zhang <hongtaozhang@microsoft.com>
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.

3 participants