Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Couple of fixes with handling multiple benchmarks data #284

Merged
merged 2 commits into from
Jan 28, 2022

Conversation

punchagan
Copy link
Contributor

This PR adds a couple of fixes for handling data of benchmark runs with multiple benchmarks. We support having a list of benchmarks, when each of them should be named.

  1. Hide the benchmarks menu only when unnamed benchmarks are used.
  2. Allow having test-names repeating across different benchmarks

Previously, the benchmark menu was incorrectly hidden if there was only one
benchmark for a commit. This commit changes the UI to hide the menu only when
the benchmark is a "default" benchmark which is unnamed. When we have named
benchmarks, we don't hide the menu because the GraphQL requests and ensure that
the GraphQL request has the benchmark name in the request.
Previously, we only allowed unique test names for each benchmark run for a
commit. But, we also allow multiple named benchmarks in each commit. This
commit loosens the uniqueness restriction to allow duplicate test names in
different benchmarks
@art-w
Copy link
Contributor

art-w commented Jan 28, 2022

Good catches! Thanks :)

@art-w art-w merged commit c52c25a into ocurrent:main Jan 28, 2022
@punchagan punchagan deleted the benchmark-name-fixes branch January 28, 2022 11:50
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.

None yet

2 participants