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_ubsan in repository toolchain/ci/base-artifacts.
discards 84d6237a7 2: update: binutils-gcc: 0 discards 851c67dae 1: reset: binutils-bb368aad297fe3ad40cf397e6fc85aa471429a28: 0 discards db6527ae8 0: update: gcc-1375e2b62332351a8f9c928421cd1ea8b53c5127: 2 new 1e1975886 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 (84d6237a7) \ 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 1556 -> 1580 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 25140 -> 38224 bytes 05-build_abe-bootstrap_ubsan/console.log.xz | Bin 0 -> 327848 bytes 06-check_regression/console.log.xz | Bin 412 -> 416 bytes 07-update_baseline/console.log | 81 +++++++++++++--------------- 07-update_baseline/results.regressions | 2 - jenkins/manifest.sh | 11 ++-- results | 4 ++ 9 files changed, 48 insertions(+), 50 deletions(-) create mode 100644 05-build_abe-bootstrap_ubsan/console.log.xz delete mode 100644 07-update_baseline/results.regressions