This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto_lean in repository toolchain/ci/base-artifacts.
discards aa073a99e 2: update: gcc-605b64251c78f29da32ed807413971339f27d13b: 1 discards fd6418461 1: reset: gcc-bd9837bc3ca1344c32aef7ba9f8fa1785063132e: 1 discards f1c2af2bc 0: update: binutils-13391ff8bcdbb29421528cad6d5763b31c8d9b26: 2 new fa046e5e4 0: update: binutils-gcc: 2
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 (aa073a99e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...]
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: 01-reset_artifacts/console.log.xz | Bin 1656 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 37000 -> 37852 bytes .../console.log.xz | Bin 415452 -> 520116 bytes 06-check_regression/console.log.xz | Bin 416 -> 416 bytes 07-update_baseline/console.log | 90 +++++++++++++-------- 07-update_baseline/results.regressions | 2 - jenkins/manifest.sh | 13 +-- results | 2 + 9 files changed, 66 insertions(+), 41 deletions(-) delete mode 100644 07-update_baseline/results.regressions