summaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2025-03-28 22:11:07 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2025-03-28 22:14:14 +0000
commit6d1366214863065674676dd16354e9fff54408e8 (patch)
treec4e23c655832c862117f038b0ed2aecc2e1cfb2c /scripts
parentfd85dd43e841c85a1730c602a651998bb247c5e0 (diff)
downloadpoky-6d1366214863065674676dd16354e9fff54408e8.tar.gz
buildperf: Avoid step usage in performance line graphs
When using steps in the line chart, you have to look long and hard to understand if the data is the lower or upper point on the step. Whilst not as pretty, the sloped line charts are more accurate so switch to those as the transition points are important and the main reason for the charts. (From OE-Core rev: 60cc8cf421c0b04f774fd42a415f275ad457bcdf) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts')
-rw-r--r--scripts/lib/build_perf/html/measurement_chart.html2
1 files changed, 0 insertions, 2 deletions
diff --git a/scripts/lib/build_perf/html/measurement_chart.html b/scripts/lib/build_perf/html/measurement_chart.html
index 3cd713a2ee..5e4f4be336 100644
--- a/scripts/lib/build_perf/html/measurement_chart.html
+++ b/scripts/lib/build_perf/html/measurement_chart.html
@@ -82,7 +82,6 @@
82 { 82 {
83 name: '{{ measurement.value_type.quantity }}', 83 name: '{{ measurement.value_type.quantity }}',
84 type: 'line', 84 type: 'line',
85 step: 'start',
86 symbol: 'none', 85 symbol: 'none',
87 data: data 86 data: data
88 } 87 }
@@ -137,7 +136,6 @@
137 { 136 {
138 name: '{{ measurement.value_type.quantity }}', 137 name: '{{ measurement.value_type.quantity }}',
139 type: 'line', 138 type: 'line',
140 step: 'start',
141 symbol: 'none', 139 symbol: 'none',
142 data: commitCountData 140 data: commitCountData
143 } 141 }