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_check_gcc/master-arm in repository toolchain/ci/base-artifacts.

discards 5d6475c55f 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 95ee0fc2b2 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards f78c47a01b 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 71ec2b256a 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 26e4ef8aac 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards d1494b368b 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 9a52f4d367 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards a8a5c7b274 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 58177afed8 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards a3b1e74257 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 36c48241d6 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards eac536b4f4 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 6586f883b0 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 26e0bcbb28 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards f5b06f8877 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 9ed26614d5 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 344492181a 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards cb0843bb75 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 5cfd242dfd 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards c30657b383 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards ffc26f858b 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards e58ddd0aaa 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards d248acae62 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards ac3c1521f3 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards a2173b3685 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 429a1b3acc 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 1e349ba238 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 2a58e55a10 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards e158ba75d5 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards c70aeb9fa3 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 83d6addc9c 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 3b5f0e7710 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards dc149f046a 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1d979bd027 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards c72faf8b42 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards e0a7643bb4 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 2aba92347f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards aad082b030 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 5a6adaa3ce 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 0cd1e8b652 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 93387a15eb 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 3197963920 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 980a418e0a 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 9c9ef65e5e 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 051cb33928 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 10a8a1d168 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards fc30297416 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1e7add6298 74: onsuccess: 1: Successful build after linux: 44 commits discards 1524c123d5 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 46b674f4f2 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 37fd8a2758 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 5a23d1837c 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 66a33e7cfd 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 3de7e02883 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards caf38f49ff 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cf31c7f78b 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d06e2643fe 65: onsuccess: 1: Successful build after gcc: 4 commits discards 31f45b1297 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8851ea5153 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 72d95dbbe4 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards eb6e1ad31b 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 48d089131e 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 380ddf4dd0 59: onsuccess: 1: Successful build after glibc: 2 commits discards 116b5b8354 58: onsuccess: 1: Successful build after binutils: 2 commits discards bcc6b43c68 57: onsuccess: 1: Successful build after gcc: 7 commits discards 7f6b0630ed 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 77916ccf3d 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ff9f5748ae 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards d57bbd87d5 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 8d90c5a361 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 4fbd438766 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 64a876f04c 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 811969b231 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 48e9c64a9c 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards c7b6ef3efa 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e86dd47a7e 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards c5f0a48026 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d6ea50e69a 44: onsuccess: 1: Successful build after linux: 34 commits discards 60f5e63d05 43: onsuccess: 1: Successful build after gcc: 2 commits discards d194034f4f 42: onsuccess: 1: Successful build after baseline build: no [...] discards 21feff93c8 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 87fdbeb9c5 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2457adf8ea 39: onsuccess: 1: Successful build after gcc: 2 commits discards 89e91bbb89 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2e4944952a 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3c74e9b921 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f104ba6333 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 1ff6426099 34: onsuccess: 1: Successful build after gcc: 3 commits discards 571978ee12 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0ff8671492 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards c833845c65 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d8c4354ab9 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards ecac602032 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5f7ea2341a 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 4c133ed4ce 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 124cdba344 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d5d0928409 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4a53f58c12 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3ab0a9609d 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 41cb28991c 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5ef61bd60c 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d95779d92c 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c196afd92c 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b1781df772 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 453e34e250 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9672090d24 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 20bac3262e 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 22d252f562 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4aaf013d2d 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 695bc0b80f 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6bae8b85ca 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 3f73260332 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 63f75c6eca 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 52e2e9dc22 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ff8ca7b2cf 34: onsuccess: 1: Successful build after gcc: 3 commits new f21730a09f 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 95352be294 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a64dfebcc4 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2c0d84ce3a 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 723b5d9d9c 39: onsuccess: 1: Successful build after gcc: 2 commits new 1a50ec5672 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 260c9806e8 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new aff9593b68 42: onsuccess: 1: Successful build after baseline build: no [...] new d3bf6e864f 43: onsuccess: 1: Successful build after gcc: 2 commits new 7e72073f57 44: onsuccess: 1: Successful build after linux: 34 commits new 2a7438e418 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 214a5b950b 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new c767289c4a 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8c32b0bccd 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new f65f2e4354 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3f4d848fda 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 86903039de 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3c7abe5321 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 567080e40f 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new a8a65e0c01 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 162281bbc7 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0c940ed976 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e458109a19 57: onsuccess: 1: Successful build after gcc: 7 commits new 57265a09e2 58: onsuccess: 1: Successful build after binutils: 2 commits new 453be4d9e3 59: onsuccess: 1: Successful build after glibc: 2 commits new 9d1dbd2b85 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new fd777f81f7 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new b52b9d1609 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 4bee82a486 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 10bc9b9b88 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ce22f2cedc 65: onsuccess: 1: Successful build after gcc: 4 commits new 505a4316b7 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 059eccacd9 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4d7608b2a3 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 675f095bc7 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 9046432133 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new ce708713e0 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 4e5939d70a 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6ee25a807c 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 49195f235f 74: onsuccess: 1: Successful build after linux: 44 commits new 3dfc5764a0 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 57a21573d5 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 7289a41f92 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5c4a3275d6 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1c7fb87f70 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 90abb185a1 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new a62de56b0d 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 0073238a62 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 1b76dc1d0e 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new feac2fc637 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 2c1eeafee5 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 32bc3d8b45 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new fa2606fcc7 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 338916d5c3 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new ea8a0d0465 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new d60f2d2a2b 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 3e2def9a16 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new b64df19169 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new bc0a676274 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 037f72ed6b 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 8fe73609cc 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 6030347cec 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 1e75a4b03e 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 599a1a9a98 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new a2dcf7bec0 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 9e9019db48 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 330f824c27 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 0d243243c5 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new a09d99b551 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new f5c6f25cc0 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 1ab24f2e4e 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 1cb097d98b 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 7708cfb095 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 9f2f64a29c 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 2e6c8aea73 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new a5d202fd80 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 3a103bfd88 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 1ba3d6caaf 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 5eafc60014 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 9df9d0c34e 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 1e24a6418f 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new f68e9fec51 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 778ef6c1f7 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 8f44f84653 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new d77b2157da 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new a75796f09e 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new b0a20b9d19 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 1e6634ec1d 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/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 (5d6475c55f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]

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 1740 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30104 -> 29996 bytes 04-build_abe-stage1/console.log.xz | Bin 91000 -> 90832 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8572 -> 8952 bytes 07-build_abe-glibc/console.log.xz | Bin 233576 -> 233688 bytes 08-build_abe-stage2/console.log.xz | Bin 223740 -> 224692 bytes 09-build_abe-gdb/console.log.xz | Bin 37248 -> 37204 bytes 10-build_abe-qemu/console.log.xz | Bin 31108 -> 31224 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2780 -> 2752 bytes 13-check_regression/console.log.xz | Bin 6736 -> 7292 bytes 13-check_regression/results.compare | 56 +- 13-check_regression/results.compare2 | 149 +- 14-update_baseline/console.log | 42 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- sumfiles/g++.log.xz | Bin 2677476 -> 2663288 bytes sumfiles/g++.sum | 146 +- sumfiles/gcc.log.xz | Bin 2212280 -> 2227740 bytes sumfiles/gcc.sum | 2697 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 881336 -> 882820 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201184 -> 201120 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 422648 -> 426244 bytes sumfiles/libstdc++.sum | 10 +- 40 files changed, 1679 insertions(+), 1549 deletions(-)