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 6cf93a4feb 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 3744ea3649 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards ab91e4b90f 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 5c1146216a 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 2a12462e9c 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 8e1398106c 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 8ef15db9ba 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 5edc62e084 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 6f0a0b9446 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 70b3063a31 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 210deb0d8a 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 69d9f93d35 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 2eba566b54 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards cac44c0077 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards c655dad470 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards dda2bfc9db 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards ace8fdd154 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards e04b33fd10 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards b16a78a43a 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 598a8fc9a6 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 27a2df9661 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 46090094ff 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 4dd3ae9783 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards fb2259f5c9 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards ea8feb0dc2 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards faed20e4e3 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 1aa99a1df9 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards b9fa43af76 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 9ca037e35b 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards b4391ae683 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards f1930121b7 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2f9624dcf5 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 3aca5cb934 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 2d85a3bbe7 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards fc8975484a 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards cbee85da6f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 5ead184d63 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 1b5b575c9b 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 01a4526e55 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 607d8be8be 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 7b659a6dc6 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards cd79f331a9 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 463c2415a2 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 04f433d638 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 168df31197 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards b85b0e3c0d 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 40d2110431 74: onsuccess: 1: Successful build after linux: 44 commits discards cbc1cb86e2 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 51a65f1885 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1bbf45f942 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards bbdd4f8eff 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 76e869f38d 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards c89ffff3a8 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d29b2b9a48 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5bd301bc33 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d2c9f51647 65: onsuccess: 1: Successful build after gcc: 4 commits discards a513d5cbcd 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0d292a008f 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 121aee6731 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 3f73fbdf99 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 2ce99b79df 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 993cb72303 59: onsuccess: 1: Successful build after glibc: 2 commits discards 57c6c1285a 58: onsuccess: 1: Successful build after binutils: 2 commits discards ce67293d4e 57: onsuccess: 1: Successful build after gcc: 7 commits discards e806de8a9a 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2c962715d3 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 68b0edb93d 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 20c2afa76a 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 9b4148e59d 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 112951b067 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ddee9d5821 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6379d45be9 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards da86da5704 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards d1543f6f77 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d57c27aff5 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards f4ec3fd84a 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8e0a1c2a82 44: onsuccess: 1: Successful build after linux: 34 commits discards 6e11926588 43: onsuccess: 1: Successful build after gcc: 2 commits discards a8d8faccf2 42: onsuccess: 1: Successful build after baseline build: no [...] discards 81ef9bd520 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c539472f53 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 790984d2df 39: onsuccess: 1: Successful build after gcc: 2 commits discards e472062a92 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c80680021c 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 659e8c9906 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 45451b5cdf 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c4e0195e55 34: onsuccess: 1: Successful build after gcc: 3 commits discards d955523345 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a2cd69e24a 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards b7f13cc06e 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards cfd427be33 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards f68ae2c1e0 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 59b14e1099 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards f0a438f08d 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5e5f3b1e3e 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 76af08d71a 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b9998e2af6 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6e855d2211 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b5d3969c9e 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 66aeb1d4f7 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9a007a697d 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ab546fb047 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5ef61bd60c 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 41cb28991c 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3ab0a9609d 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4a53f58c12 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d5d0928409 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 124cdba344 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4c133ed4ce 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 5f7ea2341a 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new ecac602032 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d8c4354ab9 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new c833845c65 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0ff8671492 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 571978ee12 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1ff6426099 34: onsuccess: 1: Successful build after gcc: 3 commits new f104ba6333 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3c74e9b921 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2e4944952a 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 89e91bbb89 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2457adf8ea 39: onsuccess: 1: Successful build after gcc: 2 commits new 87fdbeb9c5 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 21feff93c8 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d194034f4f 42: onsuccess: 1: Successful build after baseline build: no [...] new 60f5e63d05 43: onsuccess: 1: Successful build after gcc: 2 commits new d6ea50e69a 44: onsuccess: 1: Successful build after linux: 34 commits new c5f0a48026 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e86dd47a7e 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new c7b6ef3efa 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 48e9c64a9c 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 811969b231 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 64a876f04c 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4fbd438766 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 8d90c5a361 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new d57bbd87d5 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new ff9f5748ae 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 77916ccf3d 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7f6b0630ed 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bcc6b43c68 57: onsuccess: 1: Successful build after gcc: 7 commits new 116b5b8354 58: onsuccess: 1: Successful build after binutils: 2 commits new 380ddf4dd0 59: onsuccess: 1: Successful build after glibc: 2 commits new 48d089131e 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new eb6e1ad31b 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 72d95dbbe4 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 8851ea5153 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 31f45b1297 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d06e2643fe 65: onsuccess: 1: Successful build after gcc: 4 commits new cf31c7f78b 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new caf38f49ff 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3de7e02883 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 66a33e7cfd 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 5a23d1837c 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 37fd8a2758 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 46b674f4f2 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1524c123d5 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 1e7add6298 74: onsuccess: 1: Successful build after linux: 44 commits new fc30297416 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 10a8a1d168 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 051cb33928 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9c9ef65e5e 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 980a418e0a 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 3197963920 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 93387a15eb 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 0cd1e8b652 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 5a6adaa3ce 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new aad082b030 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 2aba92347f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new e0a7643bb4 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new c72faf8b42 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 1d979bd027 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new dc149f046a 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 3b5f0e7710 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 83d6addc9c 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new c70aeb9fa3 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new e158ba75d5 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 2a58e55a10 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 1e349ba238 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 429a1b3acc 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new a2173b3685 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new ac3c1521f3 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new d248acae62 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new e58ddd0aaa 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new ffc26f858b 101: onsuccess: #1693: 1: Success after glibc: 14 commits new c30657b383 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 5cfd242dfd 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new cb0843bb75 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 344492181a 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 9ed26614d5 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new f5b06f8877 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 26e0bcbb28 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 6586f883b0 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new eac536b4f4 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 36c48241d6 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new a3b1e74257 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 58177afed8 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new a8a5c7b274 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 9a52f4d367 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new d1494b368b 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 26e4ef8aac 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 71ec2b256a 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new f78c47a01b 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 95ee0fc2b2 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 5d6475c55f 121: onsuccess: #1716: 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 (6cf93a4feb) \ 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 1700 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 31136 -> 30104 bytes 04-build_abe-stage1/console.log.xz | Bin 91220 -> 91000 bytes 06-build_abe-linux/console.log.xz | Bin 9264 -> 8572 bytes 07-build_abe-glibc/console.log.xz | Bin 234064 -> 233576 bytes 08-build_abe-stage2/console.log.xz | Bin 225256 -> 223740 bytes 09-build_abe-gdb/console.log.xz | Bin 38260 -> 37248 bytes 10-build_abe-qemu/console.log.xz | Bin 31348 -> 31108 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3844 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2624 -> 2780 bytes 13-check_regression/console.log.xz | Bin 6456 -> 6736 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 14 + 13-check_regression/results.compare2 | 178 +-- 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 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 43 +- sumfiles/g++.log.xz | Bin 2684556 -> 2677476 bytes sumfiles/g++.sum | 45 +- sumfiles/gcc.log.xz | Bin 2216340 -> 2212280 bytes sumfiles/gcc.sum | 2304 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 881176 -> 881336 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201032 -> 201184 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 422452 -> 422648 bytes sumfiles/libstdc++.sum | 2 +- 40 files changed, 1284 insertions(+), 1448 deletions(-)