Skip to content

Conversation

@stanbrub
Copy link
Collaborator

@stanbrub stanbrub commented Jan 2, 2026

Sort adhoc dashboard benchmark sets according to when the benchmarks were run. That way they are displayed in the order the user specifies in the adhoc workflow. For all panels, we now show the sets from left to right in the order they were run. The resulting gain is more natural that way.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR modifies the sorting behavior of adhoc dashboard benchmark sets to display them in chronological order based on when benchmarks were executed, rather than by set_id in descending order.

  • Changed the get_setids() function to sort by both set_id and timestamp instead of only set_id in descending order

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@stanbrub stanbrub merged commit 19c77bd into deephaven:main Jan 2, 2026
16 checks passed
@stanbrub stanbrub deleted the adhoc-dashboard-setid-sort branch January 2, 2026 23:07
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