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 66cb37f4aa 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards f787539b12 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 8e8da41c16 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 918a8144e0 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 5d81d763fc 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards cab415c170 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 7be0512a0f 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 743d2a495f 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 5c74bed680 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards be5dcce928 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards f28bb5ab7f 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 0dc1a7c3ab 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards fcc83d684e 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 76c2c9ca68 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards c30f9d680d 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 6f99a0379d 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 9a42235c85 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards e6e303149d 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards f568547e25 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 4688dccb6d 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 9b964a0526 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 152083d5a1 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards a8584f8901 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards a2cc25fa8f 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 9b569dc3d8 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 68e9d22f5c 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 3d02ba50a6 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 40bd38962b 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 6161485d75 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards df23fda312 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 6c574750bc 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 2e9a1c812f 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 5d940de605 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a7529367d0 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8b3db4c79b 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 3ca8bdcef0 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dc6a125b29 74: onsuccess: 1: Successful build after linux: 44 commits discards 5b80c6cb8d 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards ddb1151e5c 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c26ed4d636 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 9ff57290e7 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 4a9a7a82f8 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 2ba9080721 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a137a4ab88 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 79069dea3d 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 69f7ada228 65: onsuccess: 1: Successful build after gcc: 4 commits discards 28db31daa4 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e697460749 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 54c65cfd67 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 5065db95d7 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 31da8af415 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 50b53e0458 59: onsuccess: 1: Successful build after glibc: 2 commits discards a839734c18 58: onsuccess: 1: Successful build after binutils: 2 commits discards 9925ad7562 57: onsuccess: 1: Successful build after gcc: 7 commits discards 8554019c31 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f5c386a42c 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d39861fddb 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards e3aa4ccdde 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 7c335b1263 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 9e5385ae7a 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards effbc9faef 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 99c3db5ce8 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 986a847787 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards a29d8741ad 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0001c0d01d 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 5af95da120 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b361c4cf61 44: onsuccess: 1: Successful build after linux: 34 commits discards f6316105ee 43: onsuccess: 1: Successful build after gcc: 2 commits discards 21cf542692 42: onsuccess: 1: Successful build after baseline build: no [...] discards 1cf83a85d5 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 062aacd104 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2ccfa3f7ba 39: onsuccess: 1: Successful build after gcc: 2 commits discards 29d4da9052 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ea031f9a45 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0bc95ea953 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4eb0fa4c0b 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 064acc4e01 34: onsuccess: 1: Successful build after gcc: 3 commits discards 1c839e260d 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards edb9b6047c 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards db196ed8d4 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d389353815 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 7e4d835c8a 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8dd0206522 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 5d47286950 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ce2820ce27 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d99a98b5ea 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b78bfbec94 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d7648c1e74 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e0de9509c5 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 428a2cf1c7 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c4f176c6bf 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 434333c2a2 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c44caae9db 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9b032be791 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 38f607bf0b 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 78ff9d81e6 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d058c63a71 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7a869130f8 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5dbe0e46e2 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7a0d1619ef 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f9c38b6dbd 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e81156953f 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ecd1499b9c 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d47d06a246 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3f60488daf 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 97d32c9631 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e8345ea702 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5485e5fceb 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new abb28b0275 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 615f94b072 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9c10732026 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 560bd6340f 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 80e47128d7 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 565eda05eb 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d620ee7147 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6e66283404 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3f71968a9a 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b79d229fc9 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new fd09d07d55 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 83549da4a0 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new f27ef5eec9 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 117d0323a3 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 35c3edb7c3 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a1805f971e 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 2721132c97 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 212d95f218 34: onsuccess: 1: Successful build after gcc: 3 commits new 7b7a8075e9 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 62e87e5153 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 542ed5b25c 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a960c02bfb 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5df8cb3340 39: onsuccess: 1: Successful build after gcc: 2 commits new c4df25d9bf 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 18390adce2 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 12e55a3ca3 42: onsuccess: 1: Successful build after baseline build: no [...] new dc356c3e29 43: onsuccess: 1: Successful build after gcc: 2 commits new 43351edc68 44: onsuccess: 1: Successful build after linux: 34 commits new ec1cfd3782 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new aba66b0442 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new adbf6161d1 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c0187a331f 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new c82fbc1a22 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new dbba9723e5 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fa19fe9cf9 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 50e38fd43e 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 883926b592 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 17809806a3 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 4f354a785b 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 832be2a5ab 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d4292a6d08 57: onsuccess: 1: Successful build after gcc: 7 commits new d08f05e39c 58: onsuccess: 1: Successful build after binutils: 2 commits new e5b5b8830d 59: onsuccess: 1: Successful build after glibc: 2 commits new b8a0cc4733 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 9f9a4892f3 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 7c279745ed 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 37292ca1a5 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 386e69e639 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bdae685c7a 65: onsuccess: 1: Successful build after gcc: 4 commits new cb2367d13d 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4640c0ed08 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0543435234 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b4d0cabfec 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 3202fe8330 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new b9fb08a86f 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 0c4767954f 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 859eb3bbbe 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new dc559bcdb3 74: onsuccess: 1: Successful build after linux: 44 commits new bb9dd63de6 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b648edd8c3 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new b789fc4fa3 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e5d578fcf8 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 860812c628 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 6723c71010 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 9e16b74ff9 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 90fdd4597f 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 970ed97a03 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 65bcd0b4bc 84: onsuccess: 1: Success after gcc/glibc: 9 commits new f7aa3d99f8 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new b1277d5b3d 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 7ee029fb84 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 69004c824b 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new fea6ee8e5b 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new a4622ea932 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 077ed06ff3 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 6471ab73b5 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 5339afa9db 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 958f2ab644 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new c0b9cf3e12 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 3fe11dfa7b 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 3b0f4d27da 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new cf7e0c5806 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 0b3be45ea3 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new f120722ce3 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 592b7bdd42 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 71eb9ef68e 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 1a0c35545d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 77e8fdd15c 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 3d17e3ae2a 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new f48d4cfe04 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new cf393721f2 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 525d7b2141 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 4c297500c3 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new a1cd3b9afe 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 2653756e07 111: onsuccess: #1704: 1: 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 (66cb37f4aa) \ 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 1684 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 29940 -> 29868 bytes 04-build_abe-stage1/console.log.xz | Bin 91000 -> 91072 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8328 -> 8292 bytes 07-build_abe-glibc/console.log.xz | Bin 233348 -> 234412 bytes 08-build_abe-stage2/console.log.xz | Bin 224304 -> 222944 bytes 09-build_abe-gdb/console.log.xz | Bin 37152 -> 37132 bytes 10-build_abe-qemu/console.log.xz | Bin 31308 -> 31280 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3852 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2692 -> 2540 bytes 13-check_regression/console.log.xz | Bin 4428 -> 6344 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 313 +++- 14-update_baseline/console.log | 66 +- 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 | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.xz | Bin 2686540 -> 2663728 bytes sumfiles/g++.sum | 255 +-- sumfiles/gcc.log.xz | Bin 2211016 -> 2231024 bytes sumfiles/gcc.sum | 2883 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 877372 -> 879100 bytes sumfiles/gfortran.sum | 92 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201132 -> 201132 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 419936 -> 422400 bytes sumfiles/libstdc++.sum | 10 +- 40 files changed, 2065 insertions(+), 1698 deletions(-)