Skip to content

Fix: results sharing a task_label are dropped (show all, not just the first) - #864

Open
muralikpbhat wants to merge 1 commit into
zilliztech:mainfrom
muralikpbhat:dup-label-fix-upstream
Open

Fix: results sharing a task_label are dropped (show all, not just the first)#864
muralikpbhat wants to merge 1 commit into
zilliztech:mainfrom
muralikpbhat:dup-label-fix-upstream

Conversation

@muralikpbhat

Copy link
Copy Markdown

Problem

getshownResults (frontend/components/check_results/filters.py) maps each selected task-label back to its results with resultSelectOptions.index(option), which returns only the first TestResult carrying that label. When two or more TestResults share a task_label, every result after the first is silently dropped from all results pages (Results, Qps & Recall, Queries-Per-Dollar, Tables, …).

Repro

  1. Run any case with --task-label demoresults/<DB>/result_<date>_demo_<db>.json.
  2. Run again (same or different config/db) with the same --task-label demo → a second result file / TestResult.
  3. Open Results or Qps & Recall and select demo: only the first run is plotted; the second run's DB/points never appear, even though both files exist and load.

Fix

Iterate every (option, result) pair and include each result whose label is selected, instead of index()-ing only the first match. No behavior change when task labels are unique.

getshownResults mapped each selected label back with resultSelectOptions.index(
option), which returns only the first TestResult carrying that label. When two
or more TestResults share a task_label (e.g. the same engine re-run under one
label), every result after the first was silently dropped from all results
pages. Iterate all (option, result) pairs and include each whose label is
selected. No change when labels are unique.
@sre-ci-robot

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: muralikpbhat
To complete the pull request process, please assign xuanyang-cn after the PR has been reviewed.
You can assign the PR to them by writing /assign @xuanyang-cn in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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.

2 participants