public
/
ottertune
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix bug of finding worst result when there is no valid result

This commit is contained in:
yangdsh 2020-03-06 03:38:02 +00:00 committed by Dana Van Aken
parent 029ad0f633
commit e5e42a4ed6
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
server/website/website/views.py
View File

@ -487,8 +487,8 @@ def handle_result_files(session, files, execution_times=None):
# Find worst throughput # Find worst throughput
past_metrics = MetricData.objects.filter(session=session) past_metrics = MetricData.objects.filter(session=session)
metric_meta = target_objectives.get_instance(session.dbms.pk, session.target_objective) metric_meta = target_objectives.get_instance(session.dbms.pk, session.target_objective)
worst_target_value = None worst_metric = past_metrics.first()
worst_metric = None worst_target_value = JSONUtil.loads(worst_metric.data)[session.target_objective]
for past_metric in past_metrics: for past_metric in past_metrics:
if '*' in past_metric.name: if '*' in past_metric.name:
continue continue