Skip to content

feat(leaderboard): publish result bundles#23645

Open
BrianCLong wants to merge 1 commit intomainfrom
feat-leaderboard-publish-bundles-14535706538936990234
Open

feat(leaderboard): publish result bundles#23645
BrianCLong wants to merge 1 commit intomainfrom
feat-leaderboard-publish-bundles-14535706538936990234

Conversation

@BrianCLong
Copy link
Copy Markdown
Owner

This PR enhances the deterministic sorting functionality of the Summit Bench leaderboard result builder to resolve ties based on alphabetical ordering of model strings. It conforms to the repository's deterministic array sorting policy via explicit < and > operator comparisons on standard arrays.


PR created automatically by Jules for task 14535706538936990234 started by @BrianCLong

…stic tie-breaking logic based on model strings when building the publishable leaderboard.

Co-authored-by: BrianCLong <6404035+BrianCLong@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 9, 2026

Warning

Rate limit exceeded

@BrianCLong has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 5 minutes and 51 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 5 minutes and 51 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a51b8905-df1d-47db-80f6-5778270dcc69

📥 Commits

Reviewing files that changed from the base of the PR and between 56b074b and 4a00293.

📒 Files selected for processing (1)
  • evaluation/leaderboard/aggregate.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat-leaderboard-publish-bundles-14535706538936990234

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

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 updates the leaderboard aggregation logic to implement a stable sort by model name when scores are identical. A review comment suggests optimizing the sorting process by removing an unnecessary shallow copy of the array, as the source array is already a fresh result from a map operation.

Comment on lines +35 to +40
const sorted = [...aggregated].sort((a, b) => {
if (a.score !== b.score) return b.score - a.score;
if (a.model < b.model) return -1;
if (a.model > b.model) return 1;
return 0;
});
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.

medium

The use of the spread operator [...aggregated] creates an unnecessary shallow copy of the aggregated array. Since aggregated is a new array returned from the .map() operation and is not used again after this sort, you can sort it in-place to improve performance and simplify the code.

Suggested change
const sorted = [...aggregated].sort((a, b) => {
if (a.score !== b.score) return b.score - a.score;
if (a.model < b.model) return -1;
if (a.model > b.model) return 1;
return 0;
});
const sorted = aggregated.sort((a, b) => {
if (a.score !== b.score) return b.score - a.score;
if (a.model < b.model) return -1;
if (a.model > b.model) return 1;
return 0;
});

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.

1 participant