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 843ade1dd 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards e598612ef 102: force: #1551: 1: Failure after gcc: 306 commits discards 31ae0291b 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 36d88a602 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] discards 145238e1d 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 1c1f6e2ea 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] discards 5df5a5a98 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 7f566e941 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 685d58cad 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2516b6d2f 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 54cc1bc7b 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards d518b390a 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 8886b4cfa 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 91e24bb13 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards d6d3f1624 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 1f3d7a396 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 67543a10e 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 107bd8e1f 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards e2b8b8c46 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards bae7741b8 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 4c56ee9a4 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 50d9dac81 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards 9aa28d780 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 9fa037ad0 80: onsuccess: 7: Successful build after linux: 44 commits discards ff29eaa89 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards e4f088123 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] discards 933fa6900 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards cd47fe659 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards aca0becd7 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards 653befc98 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 268c1cd96 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards ac5c08751 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 42e77153a 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 05946c22b 70: onsuccess: 7: Successful build after gcc: 4 commits discards 31004756a 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards e4e159e7b 68: onsuccess: 7: Successful build after linux: 6 commits discards ee53df031 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] discards b4f14fae2 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] discards 2a5a42aca 65: onsuccess: 7: Successful build after binutils: 3 commits discards bc9a64d8d 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards 2bd658056 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 280021e60 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards a77a99f46 61: onsuccess: 4: Successful build after gcc: 5 commits discards 7b63e5e1d 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards a521fd5db 59: force: 7: Successful build after gcc: 3 commits discards 98403c564 58: onsuccess: 7: Successful build after glibc: 2 commits discards 2fcea9746 57: onsuccess: 7: Successful build after gcc: 7 commits discards c76a14dc2 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 90aab2862 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 815074825 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards 59f97765c 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] discards a0b44495c 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits discards 0ae4c664a 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards e97b17499 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards fe38a05ef 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 9a7ef59e5 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 82572adf7 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 34399be61 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards e45aafb9f 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 689b38b26 44: onsuccess: 7: Successful build after linux: 34 commits discards 276a2ace6 43: onsuccess: 7: Successful build after gcc: 2 commits discards 958a04413 42: onsuccess: 7: Successful build after baseline build: no n [...] discards d0ccd30f1 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 80739eefc 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 25c9d37a3 39: onsuccess: 7: Successful build after gcc: 2 commits discards e06ddeb3a 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards abf92b020 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 6dea01ccb 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 1ea47b44a 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 0ab8c2ab5 34: onsuccess: 7: Successful build after gcc: 3 commits discards a8d547548 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 8ab292e48 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 3907a596a 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 3549d1cc6 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits discards d8c77fe5c 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 199eeea7e 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards becbceafb 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards edf20b48f 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6ce29e528 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 5da47f33d 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards be2278ed1 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 850fc8ec0 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards a4d6e3eb2 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e75875cf6 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 2b28acadb 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 5a11cbfd5 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 55b9fff51 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e4e400ab6 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 833ae1bf8 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 5b247de2c 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 292b857fe 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 716ba3878 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 3fce669ee 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 8e58ca000 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 9ea228664 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d6b16a17b 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 961ab4453 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards fd1e1cc82 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 297b5e7c8 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d61738970 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6ebf4a805 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d322302b2 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 0bad1b21d 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a9d5cb919 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 56d7e57f7 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1567e250d 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 86df744d3 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3e90b379f 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7420a7771 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 98e888841 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new f621d52cf 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e3d2f534d 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a3e876cc2 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 969089912 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a196da6e4 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d66bb82e5 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a3e1b8fb9 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a43c9fc8f 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1863b5363 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5c8de57b0 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7941f67ff 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new f2885003e 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 259aa7378 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d3af495c7 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 93d25ffd4 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 345dc96eb 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new afb9fa6ca 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new e5f776f8c 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new c8d876bb3 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits new 753dbebdb 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new b97dd51d3 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 8afd44c81 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 9074aa380 34: onsuccess: 7: Successful build after gcc: 3 commits new 12ae2ce9f 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 12ed13987 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 93654f6c0 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new d085117b3 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 942fea842 39: onsuccess: 7: Successful build after gcc: 2 commits new 64a00f38c 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a653fe250 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 5897046d3 42: onsuccess: 7: Successful build after baseline build: no n [...] new 5cea3edfc 43: onsuccess: 7: Successful build after gcc: 2 commits new c3e7e7a51 44: onsuccess: 7: Successful build after linux: 34 commits new 2487f54a9 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 31d6362a7 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new dfa196164 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new de0ac06b8 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new c1052ed47 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 43434caae 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new ca46c697a 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 18f11173f 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits new cf4400274 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] new 90e3b13c4 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 1367dcd0e 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new daea09555 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 91bdabea7 57: onsuccess: 7: Successful build after gcc: 7 commits new b539ec3b2 58: onsuccess: 7: Successful build after glibc: 2 commits new 985e3c23e 59: force: 7: Successful build after gcc: 3 commits new 2244b062c 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new f2382b1a1 61: onsuccess: 4: Successful build after gcc: 5 commits new 664e3f3e2 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new c19975518 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 1c3020e27 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new 2bcff586e 65: onsuccess: 7: Successful build after binutils: 3 commits new 17f9e6cbf 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] new e5f582638 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] new e4dd58b7c 68: onsuccess: 7: Successful build after linux: 6 commits new b300509d0 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 9fd2f8e2d 70: onsuccess: 7: Successful build after gcc: 4 commits new c64b387de 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 00e6742c8 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 9cafb757c 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 6e2f8c1cd 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new dcd544e46 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new 602aba6c2 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 3f933eacc 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new df78fc0b1 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] new ce03d14c6 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 2dab7eb31 80: onsuccess: 7: Successful build after linux: 44 commits new e94842331 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 875e0363c 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new 4ed9a17f1 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new b8e1e4771 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new cfe53c97c 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new 6f8a9e4bb 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 1d68b78db 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 66d2fa7bb 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 3aac75dbd 89: onsuccess: 7: Success after gcc/glibc: 8 commits new b6dccf672 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 54886ca5f 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 57410ae1a 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 8dc4eb400 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 7c40ec1ba 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new e45200e7e 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new b86587ecd 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new f091bd94a 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 85d1d6f94 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] new fbcf70635 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new b2159501d 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] new c8eddcb5a 101: onsuccess: #1547: 7: Success after binutils: 82 commits new c234e8e72 102: force: #1551: 1: Failure after gcc: 306 commits new 8d83e0591 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 392f03b2a 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/gl [...]
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 (843ade1dd) \ 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 1612 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30388 -> 30080 bytes 05-build_abe-stage1/console.log.xz | Bin 60304 -> 72464 bytes 06-clean_sysroot/console.log.xz | Bin 0 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 0 -> 8580 bytes 08-build_abe-glibc/console.log.xz | Bin 0 -> 240112 bytes 09-build_abe-stage2/console.log.xz | Bin 0 -> 202304 bytes 10-build_abe-gdb/console.log.xz | Bin 0 -> 37360 bytes 11-build_abe-qemu/console.log.xz | Bin 0 -> 31840 bytes 12-check_regression/console.log.xz | Bin 1768 -> 3936 bytes 12-check_regression/mail-body.txt | 23 +++++----- 13-update_baseline/console.log | 58 +++++++++++++------------- dashboard/dashboard-generate.sh | 2 +- dashboard/squad/score/results-functional.json | 1 + git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 25 ++++++----- mail/mail-subject.txt | 2 +- manifest.sh | 36 ++++++++++++---- results | 12 +++++- 26 files changed, 101 insertions(+), 72 deletions(-) create mode 100644 06-clean_sysroot/console.log.xz create mode 100644 07-build_abe-linux/console.log.xz create mode 100644 08-build_abe-glibc/console.log.xz create mode 100644 09-build_abe-stage2/console.log.xz create mode 100644 10-build_abe-gdb/console.log.xz create mode 100644 11-build_abe-qemu/console.log.xz create mode 100644 dashboard/squad/score/results-functional.json