This is an automated email from the git hooks/post-receive script.
bernie.ogden pushed a change to branch benchmarking-sync-harden in repository toolchain/abe.
discards e9eae28 Terminate target if host isn't ready in 1 hour discards 719c1c0 Terminate target on host exit discards c102dc8 Shut down host and target on error discards bf6f8e6 Simplify exit code tests discards ad435fc Harden synchronization adds 5d202ac Remove triple mismatch check adds 509f04e Find Coremark-Pro binaries with arbitrary triple new e502081 Harden synchronization new 3441be8 Simplify exit code tests new 5a03cf6 Shut down host and target on error new ebf73ce Terminate target on host exit new db9cc37 Terminate target if host isn't ready in 1 hour
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 (e9eae28) \ N -- N -- N refs/heads/benchmarking-sync-harden (db9cc37)
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 5 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/Coremark-Pro.conf | 10 +++++----- config/bench/lava/target-session | 6 +++--- scripts/Benchmark.sh | 20 -------------------- 3 files changed, 8 insertions(+), 28 deletions(-)