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

BUG: breaks when clicking on a case id - after searching for a benchmark by name #1537

Open
DeaMariaLeon opened this issue Nov 18, 2023 · 3 comments

Comments

@DeaMariaLeon
Copy link
Contributor

When there are not enough data for a graph, searching for a benchmark by name and then
clicking on a case id, I see this:

unexpected exception, please report this:
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/flask/app.py", line 1823, in full_dispatch_request
    rv = self.dispatch_request()
         ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/flask/app.py", line 1799, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/conbench/app/_endpoint.py", line 28, in wrapper
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/app/conbench/app/benchmarks.py", line 669, in show_benchmark_results
    y_unit_for_all_plots = maybe_longer_unit(units_seen.pop())
                                             ^^^^^^^^^^^^^^^^
KeyError: 'pop from an empty set'
@austin3dickey
Copy link
Member

Thanks for the bug report! Looks like in your setup this branch was taken every time:

if len(results) < 3:
continue

We probably should expect this and return an informative message in that case. 🙂

@DeaMariaLeon
Copy link
Contributor Author

Actually, it was not the same branch every time. The problem was that I was including the date to the context. So the date was creating a different context for every result in the benchmark. And every time I had just "one result".

@austin3dickey
Copy link
Member

Ah yes, we've struggled in the past with the correct balance of attributes that break history every time and ones that don't.

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

No branches or pull requests

2 participants