From: Victor Rodriguez <victor.rodriguez.bahena@intel.com>
To: libc-alpha@sourceware.org
Cc: Victor Rodriguez <victor.rodriguez.bahena@intel.com>
Subject: [PATCH 2/3] benchtests: Adjust valid and accepted properties
Date: Thu, 16 Nov 2017 22:54:00 -0000 [thread overview]
Message-ID: <20171116225233.2697-2-victor.rodriguez.bahena@intel.com> (raw)
In-Reply-To: <20171116225233.2697-1-victor.rodriguez.bahena@intel.com>
Benchmark workload-spec2006.wrf does not produce max, min or mean
results but instead produce throughput. This is represented in
benchtests/bench-skeleton.c. This patch adjust benchout.schema.json to consider
bench.out from bench-math benchmarks as valid
2017-11-15 Victor Rodriguez <victor.rodriguez.bahena@intel.com>
(VERSION): Set to 2.27
* benchtests/scripts/benchout.schema.json: Add throughput as accepted
result from property and remove "max", min" and "mean" from required
properties based on benchtests/bench-skeleton.c.
Signed-off-by: Victor Rodriguez <victor.rodriguez.bahena@intel.com>
---
ChangeLog | 7 +++++++
benchtests/scripts/benchout.schema.json | 3 ++-
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/ChangeLog b/ChangeLog
index 7d0fd63..6a6bb62 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,10 @@
+2017-11-15 Victor Rodriguez <victor.rodriguez.bahena@intel.com>
+
+ (VERSION): Set to 2.27
+ * benchtests/scripts/benchout.schema.json: Add throughput as accepted
+ result from property and remove "max", min" and "mean" from required
+ properties based on benchtests/bench-skeleton.c.
+
2017-11-15 Victor Rodriguez <victor.rodriguez.bahena@intel.com>
(VERSION): Set to 2.27
diff --git a/benchtests/scripts/benchout.schema.json b/benchtests/scripts/benchout.schema.json
index 814c633..7edd2a7 100644
--- a/benchtests/scripts/benchout.schema.json
+++ b/benchtests/scripts/benchout.schema.json
@@ -19,6 +19,7 @@
"properties": {
"duration": {"type": "number"},
"iterations": {"type": "number"},
+ "throughput": {"type": "number"},
"max": {"type": "number"},
"min": {"type": "number"},
"mean": {"type": "number"},
@@ -27,7 +28,7 @@
"items": {"type": "number"}
}
},
- "required": ["duration", "iterations", "max", "min", "mean"],
+ "required": ["duration", "iterations"],
"additionalProperties": false
}
},
--
2.15.0
next prev parent reply other threads:[~2017-11-16 22:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 22:54 [PATCH 1/3] benchtests: Wide range of tests names in schema.json Victor Rodriguez
2017-11-16 22:54 ` Victor Rodriguez [this message]
2017-11-22 10:25 ` [PATCH 2/3] benchtests: Adjust valid and accepted properties Siddhesh Poyarekar
2017-11-16 22:54 ` [PATCH 3/3] benchtests:Enable BENCHSET to run subset of tests Victor Rodriguez
2017-11-22 10:34 ` Siddhesh Poyarekar
2017-11-17 1:12 ` [PATCH 1/3] benchtests: Wide range of tests names in schema.json Paul Clarke
2017-11-18 14:24 ` Rodriguez Bahena, Victor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171116225233.2697-2-victor.rodriguez.bahena@intel.com \
--to=victor.rodriguez.bahena@intel.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).