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 e5c4e1ae85 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards ccdf5fc428 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards 23265f9dc8 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards bd2c1b0728 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards ac52a0007c 102: force: #1551: 1: Failure after gcc: 306 commits discards aa4d731645 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 317f229c5e 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards c07f2e50b3 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 7664c52652 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards e321bb81cb 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards c411855353 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards b4cf283eee 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2334f4674f 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 0472bd11e1 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards f3107ee463 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards a7f60a92d9 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 291862f1b3 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 66846a99e7 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards fe3c70dc5a 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards f856b77dcd 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards d81bba1fff 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 773b19b9cf 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards b4eecbace9 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards d66fc23a82 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 91a99a59f3 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 452ebdda98 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards aa37489d2b 80: onsuccess: 7: Successful build after linux: 44 commits discards fe09a2f494 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards dca52e9829 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards 81bf6f7d11 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 036040a813 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 636a351995 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 1a30858888 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 43a7a4a73c 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 54a2a148aa 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6a4b7d7b21 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 1c8059fcdb 70: onsuccess: 7: Successful build after gcc: 4 commits discards c846bc87e1 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 1b0c44e074 68: onsuccess: 7: Successful build after linux: 6 commits discards c0d1aa8aa5 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards 9b58551ee1 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards a1e04f42ec 65: onsuccess: 7: Successful build after binutils: 3 commits discards e72b97df12 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 1a55568040 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 449a972e7c 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 9df252cf27 61: onsuccess: 4: Successful build after gcc: 5 commits discards 880c9bb4c5 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards af5313569e 59: force: 7: Successful build after gcc: 3 commits discards d09b7911c5 58: onsuccess: 7: Successful build after glibc: 2 commits discards 3e799ddf1e 57: onsuccess: 7: Successful build after gcc: 7 commits discards 29136c26b8 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b661023e0e 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 624defd97a 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards 34af3c700c 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 90b4f560ab 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards d177348eca 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 2e4f76ede9 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f133f46a57 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards fcee221dcd 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards b199863f50 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards cdaf8b8d72 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards ec45a9207b 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e855ed53c0 44: onsuccess: 7: Successful build after linux: 34 commits discards f727e48e8a 43: onsuccess: 7: Successful build after gcc: 2 commits discards a86b62fb19 42: onsuccess: 7: Successful build after baseline build: no [...] discards e3045c6b42 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards dcec0d60a6 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards db64e2c23d 39: onsuccess: 7: Successful build after gcc: 2 commits discards 86d3536243 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards eb5404794a 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 2460a59251 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards df0cc3788e 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 2da9ba46b8 34: onsuccess: 7: Successful build after gcc: 3 commits discards bd1a5acb31 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9462a4c795 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 31aedec35b 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards ca940b10d5 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits discards dffe74a60f 29: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 77f6f55045 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 4f93bdd743 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 7eefa17a9b 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards ffeba14ae3 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 391053473f 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 9d19045461 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 435f2f28cd 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 778d691a8a 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards dc54371ad3 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 78c09da59b 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 10a77fa9cc 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 667e0a50d7 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b29a5c62a8 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 194f45d10a 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards a47f3b2570 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b2e2ce9d20 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 03844ac5d6 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 4416c3e124 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1d401cdce5 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1fad067f56 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 16fac0bf5a 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1d8af85f48 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 200e014194 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 13ae22c48f 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e6a076803e 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 4f5e7ca041 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 6de1303940 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 61b4856036 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 34063d0270 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new acbc32c975 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 0a2931b5d7 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 49936d6317 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 320c51b596 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 811eb78557 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e6a1a28d07 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 596168d866 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 606a21d39e 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new f8641aae7b 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c81bd7a368 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3243ee46cb 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d1c4834415 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 4a77ea7f50 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 85fc29c33f 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5f6b789094 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d97ccd11ab 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new f65b1f85d1 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new a314249612 29: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2f20232e90 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits new 7d246b189f 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new dcc490af8f 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 67cde4e67e 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 459226a28e 34: onsuccess: 7: Successful build after gcc: 3 commits new 84ff586b82 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new c1468d4e5a 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7f3769e82c 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 1a7c1e2b8e 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e6012edf32 39: onsuccess: 7: Successful build after gcc: 2 commits new 763935deed 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 33dc958a61 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new dd6eeace57 42: onsuccess: 7: Successful build after baseline build: no [...] new 6bd285bba4 43: onsuccess: 7: Successful build after gcc: 2 commits new 9745ea63b7 44: onsuccess: 7: Successful build after linux: 34 commits new a921343b7a 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 082e4a1c94 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new ac1acb34f5 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3d3e7cd493 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new b0a7e65b8c 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 84c7888831 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 24fba1894c 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 68352136c0 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new 1f464f8808 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new b630ddbba9 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new fbca687aa1 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 824f7fc881 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 58db60996f 57: onsuccess: 7: Successful build after gcc: 7 commits new 538bb9fa57 58: onsuccess: 7: Successful build after glibc: 2 commits new 8b8ab1f1d7 59: force: 7: Successful build after gcc: 3 commits new b6b537a750 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 9928c7c69b 61: onsuccess: 4: Successful build after gcc: 5 commits new 8f04ab40a7 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new e6a502b858 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new dea75590c3 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new b8eb6d94f5 65: onsuccess: 7: Successful build after binutils: 3 commits new 65a49219f9 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 8bc670579f 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new f27abb88cd 68: onsuccess: 7: Successful build after linux: 6 commits new 5b8f3280a0 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b8b8783001 70: onsuccess: 7: Successful build after gcc: 4 commits new afee202041 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 7df4d10fb8 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 975f38246b 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new af3afb5fbc 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 3f0722d830 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 0b50d2a968 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new e9b0a9d749 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5bdf306d4f 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new ec6e930333 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new e13e8db2bb 80: onsuccess: 7: Successful build after linux: 44 commits new d8b9ba1f56 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d5e21aa546 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 285d8a49c9 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 89b682a858 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 54be0a69d0 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 968a0c1c1e 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 01f86985da 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 56bab9677d 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new a03d9c9d1e 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 0020747600 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 27b29ad0f0 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 35ccecf9fe 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new b2fcc6f892 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 649b480ac3 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 4987e49bb3 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 999adcea7d 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new d0e02947c6 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 639772bf17 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 18fdf10cc7 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new d853e4600d 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 1f6550e3fa 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 020ea2b333 102: force: #1551: 1: Failure after gcc: 306 commits new a93abbe48a 103: onsuccess: #1552: 1: Success after gcc: 5 commits new ecdc22230f 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new a2cceafcf6 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new b03f2de2fc 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 41653a0903 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...]
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 (e5c4e1ae85) \ 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 1736 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30028 -> 30348 bytes 05-build_abe-stage1/console.log.xz | Bin 71812 -> 72700 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 8300 -> 8296 bytes 08-build_abe-glibc/console.log.xz | Bin 240240 -> 239488 bytes 09-build_abe-stage2/console.log.xz | Bin 203304 -> 203332 bytes 10-build_abe-gdb/console.log.xz | Bin 37436 -> 37592 bytes 11-build_abe-qemu/console.log.xz | Bin 31804 -> 31640 bytes 12-check_regression/console.log.xz | Bin 2768 -> 2580 bytes 13-update_baseline/console.log | 40 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++++++++++++----------------- 21 files changed, 47 insertions(+), 47 deletions(-)