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

"Diana Picus pushed a change to branch diana/docker-bmk%wip in repository toolchain/jenkins-scripts.

discards 40dd5040 Add benchmarking task discards 39b21ed4 Revert "Increase memory limit for test container" discards 465bc02d Increase memory limit for test container discards 7e61a665 Hack link to cpupower discards 9754a51b Install NTP, linux-tools-common, linux-tools-4.4.0-59, cpufrequtils discards 542c267d Setup /usr/local/bin/benchmark.sh discards 470039de Set -x for start-container-docker.sh discards e6ed9935 start-container-docker.sh: More dry-run friendly discards e5d067f4 Try to run the whole thing inside a container adds 518197a4 start-container-docker.sh: Fix container startup on remote target new 234245e3 RFC: Run benchmarks inside containers

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 (40dd5040) \ N -- N -- N refs/heads/diana/docker-bmk%wip (234245e3)

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 1 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: jenkins-helpers.sh | 25 +------------------------ start-container-docker.sh | 34 ++++++++++++++++++++++++++-------- tcwg-benchmark.sh | 2 -- 3 files changed, 27 insertions(+), 34 deletions(-)