This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 in repository toolchain/ci/base-artifacts.

discards e849e16ae 102: force: #1551: 1: Failure after gcc: 306 commits discards ab1644445 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards ce58142bc 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] discards da94e36e1 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 09e0c54f1 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] discards c7534e3eb 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 076d37717 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards b627fa260 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 21cc129b2 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards de176f04c 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 9401a67c0 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards fa1ca1810 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards c6dc9db35 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 3d4da7e3b 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards f3c9edd0a 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards c77e5eae9 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards b172126f2 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 785f9f136 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards 9d727f46c 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards d8f8d1c2a 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 2fcd13414 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards 5775692ce 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards b20e0e044 80: onsuccess: 7: Successful build after linux: 44 commits discards 9003d6fd2 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards c835a8928 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] discards 72b265373 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 34c7b6e3c 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 754f5a938 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards f24174693 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards ac3767f04 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 36a28e784 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 4ee871233 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 859215e11 70: onsuccess: 7: Successful build after gcc: 4 commits discards 5e7482e2e 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards b6348958e 68: onsuccess: 7: Successful build after linux: 6 commits discards 599e06338 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] discards a77463f66 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] discards 265fbd45b 65: onsuccess: 7: Successful build after binutils: 3 commits discards d0e86f10c 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards cd4dbfb15 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 2df8ec586 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 219342c6e 61: onsuccess: 4: Successful build after gcc: 5 commits discards c90351ce9 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards c665f90af 59: force: 7: Successful build after gcc: 3 commits discards fe9125b87 58: onsuccess: 7: Successful build after glibc: 2 commits discards 0b4bffcdc 57: onsuccess: 7: Successful build after gcc: 7 commits discards b44f81650 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 2c47790cf 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 608288179 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards 4fd6b46de 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] discards 441097021 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits discards 0a4f434cc 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards df66f38b8 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 1241cb8b8 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 510547ef6 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 5086f230f 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 5224f0f6e 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 5e19c6e0a 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 73b4b267f 44: onsuccess: 7: Successful build after linux: 34 commits discards 74e600f61 43: onsuccess: 7: Successful build after gcc: 2 commits discards ab8b495be 42: onsuccess: 7: Successful build after baseline build: no n [...] discards cad2f66c5 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards ea6b7426c 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 4228952c8 39: onsuccess: 7: Successful build after gcc: 2 commits discards 7928a25f3 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 73a87549d 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards b89bde259 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards cf86c009f 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards a857e1b92 34: onsuccess: 7: Successful build after gcc: 3 commits discards 1704cb75a 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards f8c477cb3 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards cd9cf37b5 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards f69aa3399 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits discards 95f36e42a 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards d86a7a1d1 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 7f8bc8c49 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 63398e3de 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards fc9521de6 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 801234963 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 20fce03e0 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 8f5051d01 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 05dc3688e 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1d73d2546 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 0736570c2 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 835cdc5c2 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1fb8b34ed 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards a7b1e9922 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards f88d8a1e4 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 7482a4dd6 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards c279706ed 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 2b2d1a0ee 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 81d7bab95 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards f430852a6 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b0bf39b9e 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 4e74ac8ce 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 450143c48 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards c828d6f83 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 01ed85d9b 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 66bf3b5e8 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards ff3db2771 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards bd1d10ee2 2: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e9da8fea3 2: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 6ebf4a805 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d61738970 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 297b5e7c8 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new fd1e1cc82 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 961ab4453 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d6b16a17b 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9ea228664 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 8e58ca000 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3fce669ee 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 716ba3878 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 292b857fe 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5b247de2c 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 833ae1bf8 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e4e400ab6 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 55b9fff51 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5a11cbfd5 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2b28acadb 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e75875cf6 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a4d6e3eb2 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 850fc8ec0 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new be2278ed1 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5da47f33d 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 6ce29e528 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new edf20b48f 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new becbceafb 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 199eeea7e 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new d8c77fe5c 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 3549d1cc6 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits new 3907a596a 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 8ab292e48 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new a8d547548 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 0ab8c2ab5 34: onsuccess: 7: Successful build after gcc: 3 commits new 1ea47b44a 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 6dea01ccb 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new abf92b020 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new e06ddeb3a 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 25c9d37a3 39: onsuccess: 7: Successful build after gcc: 2 commits new 80739eefc 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new d0ccd30f1 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 958a04413 42: onsuccess: 7: Successful build after baseline build: no n [...] new 276a2ace6 43: onsuccess: 7: Successful build after gcc: 2 commits new 689b38b26 44: onsuccess: 7: Successful build after linux: 34 commits new e45aafb9f 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 34399be61 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 82572adf7 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 9a7ef59e5 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new fe38a05ef 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new e97b17499 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 0ae4c664a 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new a0b44495c 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits new 59f97765c 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] new 815074825 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 90aab2862 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new c76a14dc2 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 2fcea9746 57: onsuccess: 7: Successful build after gcc: 7 commits new 98403c564 58: onsuccess: 7: Successful build after glibc: 2 commits new a521fd5db 59: force: 7: Successful build after gcc: 3 commits new 7b63e5e1d 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new a77a99f46 61: onsuccess: 4: Successful build after gcc: 5 commits new 280021e60 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 2bd658056 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new bc9a64d8d 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new 2a5a42aca 65: onsuccess: 7: Successful build after binutils: 3 commits new b4f14fae2 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] new ee53df031 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] new e4e159e7b 68: onsuccess: 7: Successful build after linux: 6 commits new 31004756a 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 05946c22b 70: onsuccess: 7: Successful build after gcc: 4 commits new 42e77153a 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new ac5c08751 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 268c1cd96 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 653befc98 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new aca0becd7 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new cd47fe659 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 933fa6900 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new e4f088123 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] new ff29eaa89 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 9fa037ad0 80: onsuccess: 7: Successful build after linux: 44 commits new 9aa28d780 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 50d9dac81 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new 4c56ee9a4 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new bae7741b8 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new e2b8b8c46 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new 107bd8e1f 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 67543a10e 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 1f3d7a396 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new d6d3f1624 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 91e24bb13 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 8886b4cfa 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new d518b390a 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 54cc1bc7b 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 2516b6d2f 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 685d58cad 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 7f566e941 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 5df5a5a98 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 1c1f6e2ea 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] new 145238e1d 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 36d88a602 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] new 31ae0291b 101: onsuccess: #1547: 7: Success after binutils: 82 commits new e598612ef 102: force: #1551: 1: Failure after gcc: 306 commits new 843ade1dd 103: onsuccess: #1552: 1: Success after gcc: 5 commits

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 (e849e16ae) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...]

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 102 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 1636 -> 1612 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 30744 -> 30388 bytes 05-build_abe-stage1/console.log.xz | Bin 60672 -> 60304 bytes 12-check_regression/console.log.xz | Bin 2172 -> 1768 bytes 12-check_regression/jira-body.txt | 2 +- 12-check_regression/mail-body.txt | 30 ++++++------------ 12-check_regression/mail-subject.txt | 2 +- 12-check_regression/results.regressions | 11 ------- 12-check_regression/trigger-bisect | 2 -- 13-update_baseline/console.log | 54 ++++++++++++++++---------------- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 30 ++++++------------ mail/mail-subject.txt | 2 +- manifest.sh | 14 ++++----- results | 11 ------- 18 files changed, 60 insertions(+), 104 deletions(-) delete mode 100644 12-check_regression/results.regressions delete mode 100644 12-check_regression/trigger-bisect