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 2f260e26c9 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 6ac2284ced 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 97f8f61906 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 5605e65c8b 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 0a0aa5ee42 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 75f39fff4d 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards fb01ee06b2 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 1b1685a57b 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 7005d8bef4 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards fca47379da 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 787c0b6ac5 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 6b6de671e6 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 3c38daccee 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 7c52dee1ce 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards fa5322b392 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 03b25f1662 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 226aadc428 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 0ce2c4929f 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards f3a5d25518 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 2a25fd9ac1 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 8de2316cab 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 6e96051c6e 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards b693ec556a 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards dd433b4420 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards c8bf6a03cf 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 3caa2c447c 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 8c4d20c104 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 80d01fc73a 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards fb7c9c1a53 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards b350273bfb 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 9e04678d01 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 0a681be15d 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 7bd2195f55 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards c912562c2c 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards d7a79745a4 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2515396058 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1c8216536e 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 215edec3a4 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 41331744a4 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 006281681f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 2b7ff71481 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards e6717fd332 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards f879448cae 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 7bc67ea73c 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards c28d77d885 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards cd5ad136c0 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 262023bd29 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 929e5d2388 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e36b4ff520 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 4898ced993 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a542241359 74: onsuccess: 1: Successful build after linux: 44 commits discards 33acda8e4f 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 30b3196b1f 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c7ea99df3f 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards f82c035e67 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 634d523c1b 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards dd15e0c069 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dc5173138e 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cc16f96b33 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c6932390a8 65: onsuccess: 1: Successful build after gcc: 4 commits discards 01e2800c2a 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2c0f53d65d 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5b99bef05f 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 2a6bf43910 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards ee1e6db7d6 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards e719a90bf5 59: onsuccess: 1: Successful build after glibc: 2 commits discards 7c15787702 58: onsuccess: 1: Successful build after binutils: 2 commits discards 17eec55130 57: onsuccess: 1: Successful build after gcc: 7 commits discards 3f946d6c5c 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b99573bfd6 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fea5c7955c 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards f23f5c1c55 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards c3f3e6c088 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards dd7a2bf2e8 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ecb16f14b4 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4c4f0ac824 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 671ff536d9 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards a3af03175b 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 06a3a6a2a2 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 785a12f705 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7ad547a5be 44: onsuccess: 1: Successful build after linux: 34 commits discards 399f5b106d 43: onsuccess: 1: Successful build after gcc: 2 commits discards a8d9133b83 42: onsuccess: 1: Successful build after baseline build: no [...] discards 2636640f33 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a6b5c4e725 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards efb64e088f 39: onsuccess: 1: Successful build after gcc: 2 commits discards 02182fecf2 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 33c873156a 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ee58f11edb 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b118770ed7 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 57b66db3d0 34: onsuccess: 1: Successful build after gcc: 3 commits discards 0005672bd2 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b346af96ee 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards df4861eeff 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2f873fa467 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 07984f40f9 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 32276625e0 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 5ef3014886 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2b9f8f8c88 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a1b3e72047 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 400806b5f7 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 55d59f0d55 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e91b49737f 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 22be63e70e 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8cb8d8298a 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ede28b4f5e 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 5b48981281 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7c0569514d 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 79dca063d3 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new edae2643fd 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new a8e09635f5 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9c727079b3 34: onsuccess: 1: Successful build after gcc: 3 commits new 334a3b5f32 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 9a392f5eec 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 916008c119 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 032ee63563 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a3e0ac3c95 39: onsuccess: 1: Successful build after gcc: 2 commits new cd97febc87 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 26c93be87d 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1da6c7868a 42: onsuccess: 1: Successful build after baseline build: no [...] new cdd85c91f2 43: onsuccess: 1: Successful build after gcc: 2 commits new cbfdffc5bc 44: onsuccess: 1: Successful build after linux: 34 commits new 968132f4bc 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cb881ee799 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 0c2355bed1 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 74a3664be2 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 90394a2b59 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2006b09be5 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 18a66cb425 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 402817973c 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 463d78dc49 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 909e7be8e9 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 191260d3b3 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 15b635b6ed 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 98ac556aec 57: onsuccess: 1: Successful build after gcc: 7 commits new 9b915a5061 58: onsuccess: 1: Successful build after binutils: 2 commits new 153fb8aafe 59: onsuccess: 1: Successful build after glibc: 2 commits new 1980ae4567 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 8d835cc2ba 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new adddf69665 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new a1bc261548 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b61d9ba596 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c436e6e6ea 65: onsuccess: 1: Successful build after gcc: 4 commits new a94b2ff495 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c0c3c26877 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7399ae6c3f 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d9be1a4a66 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new f5d4bf5b6e 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 58ae66ba9a 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new e96a9423d2 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ea0366c129 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 5885f4cf71 74: onsuccess: 1: Successful build after linux: 44 commits new b005e0f7a3 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 44fdd7a3ca 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new a84df03623 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3de5ae1820 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3e022fe118 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new a3d1dcb5fa 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 67869b56ce 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new e431a2bcd2 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 0b41be28e3 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 5e3745d3b0 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 09b612c442 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 70bef01e15 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new da57bb5568 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 780ac4ee17 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 0d345dd617 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new e31aae9e78 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 54bbae9930 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 15eb1b8125 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new b938de70f9 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 43406dae6a 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new b41730ef41 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new bd33b3ba80 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new b8f6e369e7 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 6a17c3852e 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 3f960fae19 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new b59d40514b 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 620c491846 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 207e33be9e 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new d026685872 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new dc17df05c7 104: onsuccess: #1697: 1: Success after gcc: 4 commits new d60d0f5bf6 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 0efc94703a 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 3bbadcbdbe 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 8df0d21862 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 11b1a9d6ad 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 41242bc7f5 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 0ae614946f 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new ca884d3e4b 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new bcf3c4996d 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 60f714402f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 9fdcb5fb32 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 97e2874bea 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new b3d9cbe7c7 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 343959b0d8 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 21477532e7 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new d3b2b1738c 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 7a1f306ac1 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new a42b65ce05 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 817f4fbe27 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 44733f0d14 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new ce917f99c7 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits

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 (2f260e26c9) \ 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 1744 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30032 -> 30276 bytes 04-build_abe-stage1/console.log.xz | Bin 90540 -> 91064 bytes 06-build_abe-linux/console.log.xz | Bin 8808 -> 8836 bytes 07-build_abe-glibc/console.log.xz | Bin 233776 -> 233672 bytes 08-build_abe-stage2/console.log.xz | Bin 223020 -> 223792 bytes 09-build_abe-gdb/console.log.xz | Bin 37228 -> 37608 bytes 10-build_abe-qemu/console.log.xz | Bin 31256 -> 31000 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2440 -> 3124 bytes 13-check_regression/console.log.xz | Bin 5348 -> 5656 bytes 13-check_regression/results.compare | 14 - 13-check_regression/results.compare2 | 54 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- sumfiles/g++.log.xz | Bin 2651708 -> 2666820 bytes sumfiles/g++.sum | 52 +- sumfiles/gcc.log.xz | Bin 2207648 -> 2199392 bytes sumfiles/gcc.sum | 2401 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 879888 -> 881392 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201268 -> 201200 bytes sumfiles/libgomp.sum | 8 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 426708 -> 428188 bytes sumfiles/libstdc++.sum | 8 +- 37 files changed, 1345 insertions(+), 1312 deletions(-)