This is an automated email from the git hooks/post-receive script.
bernie.ogden pushed a change to branch bernie/benchmarking-uinstance in repository toolchain/abe.
discards a2debc9 template.yaml: Metadata must be a string discards 693cf4e CPU2006.sh: Attach raw output to run discards dea66c4 fakebench.sh: Attach to run, not a test case discards 813c58e Gather script + tests for CPU2006 discards dec1dbc dispatch-benchmark.py: Validate input new c291aa9 dispatch-benchmark.py: Validate input new 4988f39 Gather script + tests for CPU2006 new 7b4b5d1 fakebench.sh: Attach to run, not a test case new 286946a CPU2006.sh: Attach raw output to run new 5b3d98d template.yaml: Metadata must be a string
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 (a2debc9) \ N -- N -- N refs/heads/bernie/benchmarking-uinstance (5b3d98d)
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: scripts/dispatch-benchmark.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)