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_lto in repository toolchain/ci/base-artifacts.
discards ad5c3651 2: update: binutils-gcc: 1 discards b0d64b1d 1: reset: binutils-90b7a5df152a64d2bea20beb438e8b81049a5c30: 1 discards b1ed45c8 0: update: gcc-445d8deffb6c9bc1f4a5ed0a8e02d7f31d3caec7: 2 new 1000d6e0 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 (ad5c3651) \ 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 1712 -> 1560 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2716 bytes 04-build_abe-binutils/console.log.xz | Bin 38164 -> 38676 bytes 05-build_abe-bootstrap_lto/console.log.xz | Bin 100316 -> 274720 bytes 06-check_regression/console.log.xz | Bin 416 -> 416 bytes 07-update_baseline/console.log | 79 ++++++++++++++---------------- 07-update_baseline/results.regressions | 2 - jenkins/manifest.sh | 12 ++--- results | 2 + 9 files changed, 45 insertions(+), 50 deletions(-) delete mode 100644 07-update_baseline/results.regressions