summaryrefslogtreecommitdiff
path: root/testsuite/tests/callarity
diff options
context:
space:
mode:
authorJoachim Breitner <mail@joachim-breitner.de>2014-07-17 12:58:33 +0200
committerJoachim Breitner <mail@joachim-breitner.de>2014-07-17 12:58:33 +0200
commit13cb4c279da4f4511e3bb78b22420daf9915d147 (patch)
treefa22f1896d73efb6186a8b5649bebcafe865b9d3 /testsuite/tests/callarity
parent8b6cd6e5cf7c358aaa30b5b2700c09418ba22586 (diff)
downloadhaskell-13cb4c279da4f4511e3bb78b22420daf9915d147.tar.gz
Adjust a few performance numbers
These did not yet trigger a failure, but are more than 1% away from the expected value. Since I now start collecting logs to investigate deviations from the expected value, it makes sense to reset them. This way we know that every significat deviation was caused since this commit. I only updated bytes_allocated numbers, as these are (mostly) deterministic. Other depend, AFAIK, on sampling timing, so I did not bother.
Diffstat (limited to 'testsuite/tests/callarity')
-rw-r--r--testsuite/tests/callarity/perf/all.T3
1 files changed, 2 insertions, 1 deletions
diff --git a/testsuite/tests/callarity/perf/all.T b/testsuite/tests/callarity/perf/all.T
index 765a2e94a7..1c7969474c 100644
--- a/testsuite/tests/callarity/perf/all.T
+++ b/testsuite/tests/callarity/perf/all.T
@@ -1,8 +1,9 @@
test('T3924',
[stats_num_field('bytes allocated',
- [ (wordsize(64), 51480, 5),
+ [ (wordsize(64), 50760, 5),
# previously, without call-arity: 22326544
# 2014-01-18: 51480 (amd64/Linux)
+ # 2014-07-17: 50760 (amd64/Linux) (Roundabout adjustment)
(wordsize(32), 44988, 5) ]),
# 2014-04-04: 44988 (Windows, 64-bit machine)
only_ways(['normal'])