This is an automated email from the git hooks/post-receive script.

bernie.ogden pushed a change to branch bernie/benchmarking-uinstance-arbitrary in repository toolchain/abe.

discards 5bb8938 WIP: Disable netctl so I can see what is going on discards 43ddb80 Match tcpdump output even if user gave username discards cc3d3ee Match tcpdump output even if user gave hostnames discards 0ef8822 Do not report names in tcpdump discards f2a3532 Revert "Enquote sysroot" discards d34938c WIP: Install less packages discards 5cdf5cb Add missing tcpdump dependency discards dae9301 Permit host machine to be of any type discards 04fb77c Enquote sysroot omits 790d41c benchmark.sh: Rename GCC to something more generic omits 966db2e Clean up toolchain usage omits 0794458 Ensure that unset params get value None omits 6a64030 Gather script for Coremark Pro omits bf7a56e dispatch-benchmark.py: Support Coremark Pro omits 5597d02 CoremarkPro support omits b1d5fbc Add some (commented-out) debugging output omits 6508886 Always read configs with target context omits f9cd693 Apply target context when looking for binaries omits 4234e4f Support external sysroot new 839c59f dispatch-benchmark.py: More detail on keyring fail new 58b1f00 Support external sysroot new 1150d0f Apply target context when looking for binaries new 901bef2 Always read configs with target context new 4344b17 Add some (commented-out) debugging output new 0775c67 CoremarkPro support new 45361bf dispatch-benchmark.py: Support Coremark Pro new 7ba290d Gather script for Coremark Pro new 9c01d92 Ensure that unset params get value None new 99e0bf8 Clean up toolchain usage new f480e0c benchmark.sh: Rename GCC to something more generic new dced53d Do not report names in tcpdump new dab37b5 Match tcpdump output even if user gave hostnames new bff7bc9 Match tcpdump output even if user gave username new 4099076 Permit host machine to be of any type new 9ac253b Add missing tcpdump dependency new 5a7c10e Remove *-multilib from host packages

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 (5bb8938) \ N -- N -- N refs/heads/bernie/benchmarking-uinstance-arbitrary (5a7c10e)

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.

The 17 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.

Summary of changes: config/bench/boards/juno-a53.conf | 2 +- config/bench/boards/juno-a57.conf | 2 +- scripts/dispatch-benchmark.py | 2 ++ 3 files changed, 4 insertions(+), 2 deletions(-)