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_O1 in repository toolchain/ci/base-artifacts.
discards 3738714a1 2: update: binutils-gcc: 1 discards 8a55d7b9e 1: reset: gcc-9bb19e143cfe8863e2e79d4176b5d7e997b08c5f: 1 discards 52e024cf7 0: update: binutils-fcbfb25dcca625a7f999ec51d48b6fc3a32123c3: 2 new e51831490 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 (3738714a1) \ 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 1644 -> 1620 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 38216 -> 38708 bytes 05-build_abe-bootstrap_O1/console.log.xz | Bin 135868 -> 272680 bytes 06-check_regression/console.log.xz | Bin 420 -> 416 bytes 07-update_baseline/console.log | 79 +++++++++++++++---------------- 07-update_baseline/results.regressions | 2 - jenkins/manifest.sh | 16 ++++--- results | 2 + 9 files changed, 48 insertions(+), 51 deletions(-) delete mode 100644 07-update_baseline/results.regressions