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 in repository toolchain/ci/base-artifacts.
discards 71b43165d 0: reset: gcc-cad36f38576a6a781e3c62ab061c68f5b8dab13a: new 7cd8b49e9 0: update: gcc-d158c3f77738e1d44aa117c1674e9ec8dee38661: 1
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 (71b43165d) \ 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 1600 -> 1524 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2768 bytes 04-build_abe-binutils/console.log.xz | Bin 64532 -> 63628 bytes 05-build_abe-bootstrap/console.log.xz | Bin 63044 -> 62944 bytes 06-check_regression/console.log.xz | Bin 840 -> 456 bytes 06-check_regression/results.regressions | 2 -- 06-check_regression/trigger-bisect | 2 -- 07-update_baseline/console.log | 48 ++++++++++++++++---------------- jenkins/manifest.sh | 10 +++---- reset-baseline | 0 results | 2 -- 11 files changed, 29 insertions(+), 35 deletions(-) delete mode 100644 06-check_regression/results.regressions delete mode 100644 06-check_regression/trigger-bisect delete mode 100644 reset-baseline