history: minor tweaks to TestThrashing

Author: tbg

pkg/kv/kvserver/asim/history/testdata/TestThrashing/initial_outlier

@@ -3,16 +3,16 @@ echo
 An initial outlier leads to a large normalization factor, 
 i.e. low thrashing percentage. This isn't necessarily good, if this becomes
 an issue we could use an inter-quantile range instead.
-input: [10250 5004 12 1 2]
+input: [10250 13 12 1 2]
  10250 ┼╮
-  9225 ┤╰─╮
-  8200 ┤  ╰─╮
-  7175 ┤    ╰─╮
-  6150 ┤      ╰─╮
-  5126 ┤        ╰─╮
-  4101 ┤          ╰─╮
-  3076 ┤            ╰─╮
-  2051 ┤              ╰─╮
-  1026 ┤                ╰─╮
-     1 ┤                  ╰────────────────────
+  9225 ┤╰╮
+  8200 ┤ ╰╮
+  7175 ┤  ╰╮
+  6150 ┤   ╰╮
+  5126 ┤    ╰╮
+  4101 ┤     ╰╮
+  3076 ┤      ╰╮
+  2051 ┤       ╰╮
+  1026 ┤        ╰╮
+     1 ┤         ╰─────────────────────────────
 tdtv=0.07% (7.3/10249.0) uptv=1.0 dntv=10249.0 runs=2

pkg/kv/kvserver/asim/history/testdata/TestThrashing/negative_crossover

@@ -1,7 +1,7 @@
 echo
 ----
 Oscillating across zero in both directions, mostly to check that
-negative numbers don't cause issues.'
+negative numbers don't cause issues.
 input: [-10 -4 -6 -1 4 5 -2 6]
    6.00 ┤                                      ╭
    4.40 ┤                      ╭─────╮        ╭╯

pkg/kv/kvserver/asim/history/trashing_test.go

@@ -76,7 +76,7 @@ func TestThrashing(t *testing.T) {
 			desc: `An initial outlier leads to a large normalization factor, 
 i.e. low thrashing percentage. This isn't necessarily good, if this becomes
 an issue we could use an inter-quantile range instead.`,
-			vs: []float64{10250, 5004, 12, 1, 2},
+			vs: []float64{10250, 13, 12, 1, 2},
 		},
 		{
 			name: "final_outlier",
@@ -94,7 +94,7 @@ beginning. The trend-aware thrashing measure (tdtv) should be small.
 		{
 			name: "negative_crossover",
 			desc: `Oscillating across zero in both directions, mostly to check that
-negative numbers don't cause issues.'`,
+negative numbers don't cause issues.`,
 			vs: []float64{-10, -4, -6, -1, 4, 5, -2, 6},
 		},
 	} {