This is an automated email from the git hooks/post-receive script.
bernie.ogden pushed a change to branch benchmarking-fixes in repository toolchain/abe.
discards 93cacfd Run full cpufreq-info when recording target state discards afeb54e gather scripts: Prune attachments discards e875a8c Rework quoting in buildonly run of benchmark.sh adds 37630b9 Make downloadable check permit local paths adds 2badf77 Correct host-session testdefs for unusual hosts adds 18c3dd1 Fail if testdef is unavailable for host or target adds 0e14a4a Generate session stanzas in functions adds f93e2c6 Pedantically remove last bit of global namespace pollution adds a812efe Rework quoting in buildonly run of benchmark.sh adds 3d903c4 gather scripts: Prune attachments adds 181aa1e Run full cpufreq-info when recording target state
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:
* -- * -- B -- O -- O -- O (93cacfd) \ N -- N -- N refs/heads/benchmarking-fixes (181aa1e)
You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.
Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.
No new revisions were added by this update.
Summary of changes: scripts/Benchmark.sh | 105 ++++++++++++++++++++++++++++++--------------------- 1 file changed, 61 insertions(+), 44 deletions(-)