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-arm-bootstrap_profiled in repository toolchain/ci/base-artifacts.
discards 67b5f842f 2: update: gcc-4c334e0e4ff05d3a7ca9ebb832428c446cd0ae8d: 1 discards 963406e5b 1: reset: gcc-17f52a1c725948befcc3dd3c90d1abad77b6f6fe: 1 discards adafdf00a 0: update: binutils-2d9cf99d9a6c701de912d3e95ea3ffa134af4c62: 2 new 0e6b22510 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 (67b5f842f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...]
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 1500 -> 1556 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 50128 -> 51504 bytes 05-build_abe-bootstrap_profiled/console.log.xz | Bin 107824 -> 928656 bytes 06-check_regression/console.log.xz | Bin 416 -> 416 bytes 07-update_baseline/console.log | 82 ++++++++++++++++--------- 07-update_baseline/results.regressions | 2 - jenkins/manifest.sh | 13 ++-- results | 2 + 9 files changed, 62 insertions(+), 37 deletions(-) delete mode 100644 07-update_baseline/results.regressions