Skip to content

Diagnose Slice benchmark failure as timing-sensitive - #79909

Draft
liym27 with Copilot wants to merge 1 commit into
developfrom
copilot/fix-slice-test-failure
Draft

liym27 with Copilot wants to merge 1 commit into
developfrom
copilot/fix-slice-test-failure

Conversation

Copilot AI commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

The Slice job failed because one low-latency Ellipsis-getitem benchmark crossed its performance threshold. The PR changes FSDP code, not Slice operations.

  • Changes: No code changes; the available evidence does not justify a source or CI modification.
  • Finding: The same case passed at −8.1% and failed near −10.3% on other runs, consistent with measurement variability around the threshold.
  • Next step: Rerun the Slice job when the workflow completes.

@Paddle-Review-Bot

Paddle-Review-Bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Paddle-Bot Review Board (review完成)

序号 位置 优先级 规则来源 状态

Powered by Nyanpasu claude with Opus 5.5 默认推理级别, please check the suggestions carefully.

Copilot AI changed the title [WIP] Fix the failing GitHub Actions job Slice / Slice test Diagnose Slice benchmark failure as timing-sensitive Oct 29, 2026
Copilot AI requested a review from liym27 October 29, 2026 07:54
@paddle-bot paddle-bot Bot added the contributor External developers label Oct 29, 2026
@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

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

contributor External developers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants