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 ce917f99c7 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 44733f0d14 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 817f4fbe27 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards a42b65ce05 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 7a1f306ac1 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards d3b2b1738c 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 21477532e7 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 343959b0d8 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards b3d9cbe7c7 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 97e2874bea 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 9fdcb5fb32 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 60f714402f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards bcf3c4996d 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards ca884d3e4b 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 0ae614946f 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 41242bc7f5 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 11b1a9d6ad 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 8df0d21862 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 3bbadcbdbe 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 0efc94703a 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards d60d0f5bf6 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards dc17df05c7 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards d026685872 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 207e33be9e 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 620c491846 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards b59d40514b 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 3f960fae19 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 6a17c3852e 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards b8f6e369e7 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards bd33b3ba80 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards b41730ef41 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 43406dae6a 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards b938de70f9 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 15eb1b8125 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 54bbae9930 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards e31aae9e78 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 0d345dd617 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 780ac4ee17 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards da57bb5568 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 70bef01e15 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 09b612c442 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 5e3745d3b0 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 0b41be28e3 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards e431a2bcd2 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 67869b56ce 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards a3d1dcb5fa 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 3e022fe118 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 3de5ae1820 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a84df03623 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 44fdd7a3ca 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards b005e0f7a3 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5885f4cf71 74: onsuccess: 1: Successful build after linux: 44 commits discards ea0366c129 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards e96a9423d2 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 58ae66ba9a 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards f5d4bf5b6e 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards d9be1a4a66 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 7399ae6c3f 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c0c3c26877 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a94b2ff495 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c436e6e6ea 65: onsuccess: 1: Successful build after gcc: 4 commits discards b61d9ba596 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a1bc261548 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards adddf69665 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 8d835cc2ba 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 1980ae4567 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 153fb8aafe 59: onsuccess: 1: Successful build after glibc: 2 commits discards 9b915a5061 58: onsuccess: 1: Successful build after binutils: 2 commits discards 98ac556aec 57: onsuccess: 1: Successful build after gcc: 7 commits discards 15b635b6ed 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 191260d3b3 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 909e7be8e9 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 463d78dc49 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 402817973c 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 18a66cb425 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2006b09be5 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 90394a2b59 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 74a3664be2 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 0c2355bed1 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cb881ee799 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 968132f4bc 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cbfdffc5bc 44: onsuccess: 1: Successful build after linux: 34 commits discards cdd85c91f2 43: onsuccess: 1: Successful build after gcc: 2 commits discards 1da6c7868a 42: onsuccess: 1: Successful build after baseline build: no [...] discards 26c93be87d 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cd97febc87 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a3e0ac3c95 39: onsuccess: 1: Successful build after gcc: 2 commits discards 032ee63563 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 916008c119 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 9a392f5eec 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 334a3b5f32 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 9c727079b3 34: onsuccess: 1: Successful build after gcc: 3 commits discards a8e09635f5 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards edae2643fd 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 79dca063d3 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7c0569514d 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 5b48981281 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ede28b4f5e 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 8cb8d8298a 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 22be63e70e 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e91b49737f 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ea5fa779ca 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new baf4a3c8a6 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 56989ea742 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 9ab7051d7f 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new c79bafff1c 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 32e1b956d5 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 2daf719874 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new e1e2766cf9 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 1b7ed1fcc7 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a959d826ca 34: onsuccess: 1: Successful build after gcc: 3 commits new 9fc2afbc1f 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new bb5bc96eb7 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 046843dc58 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 5eaadde2a6 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4a5b5c3ff2 39: onsuccess: 1: Successful build after gcc: 2 commits new fad7898add 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 40a83d8f55 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 619af55182 42: onsuccess: 1: Successful build after baseline build: no [...] new 8f97eb5bc0 43: onsuccess: 1: Successful build after gcc: 2 commits new 32e68d8aab 44: onsuccess: 1: Successful build after linux: 34 commits new a637ce2884 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 662e91716a 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 9c4bca7739 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e9b96e4392 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new ffbf2b3bb9 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 197925b825 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 350660f248 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 33ac97bc8b 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 53e410e66a 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 2f4343bffb 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 40fba5fac5 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8dc5163c74 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b7bdf61b29 57: onsuccess: 1: Successful build after gcc: 7 commits new 8533b96b6f 58: onsuccess: 1: Successful build after binutils: 2 commits new 83d6aac58d 59: onsuccess: 1: Successful build after glibc: 2 commits new 52171604c5 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new e0a6cda770 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 45d145c608 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 9a9b6455b4 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ca1fd292a1 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1755cc384b 65: onsuccess: 1: Successful build after gcc: 4 commits new eebfffd0aa 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a1c25317d4 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 36ec396a1b 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d40b15909c 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 867e8e3c34 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 2bb1b4e145 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 2f90dcf0a0 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 622c40e628 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new d6a45135d5 74: onsuccess: 1: Successful build after linux: 44 commits new 955aef7c60 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2dd29c08c2 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new ecc5acea91 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a6d1e7edcb 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new e2d0ea7906 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 04aef70d06 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 9875349549 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 0712eab38c 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new a1cd43b460 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new dbc4b69005 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 27eb4f5b60 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 777c6890f5 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 075d8c1c5d 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new d15dc82ff7 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new fef7e73652 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 1d82dc9391 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 988b3190ff 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new edaf23198e 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 7338df7b18 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 8628ab6283 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 69581a6feb 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 03fa9a16ae 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 63f0213ba4 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new b9ba0e3857 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 186ff70d5a 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 6fdd4946c7 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 9caf85c6eb 101: onsuccess: #1693: 1: Success after glibc: 14 commits new ad9e94997f 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 75509b76c6 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 7de5dd5373 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 0439292baf 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 942597a720 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 267b79e9f2 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 064c7591f4 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 774d23ef3d 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 3eb4bc22fb 110: onsuccess: #1703: 1: Success after gcc: 6 commits new a965c6d844 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 2dc19ae73e 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new d3a1b29121 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 37c3e6cc30 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new bde1e69391 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 20c7a3bca6 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 7d67a3f8a6 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new f4225ad148 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 2ac1e477d6 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 7ab714bc8d 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new bac8880be0 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 714b737eec 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new e42b64da95 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new d42aaa21e6 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 1df3853951 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new a90fb18776 126: onsuccess: #1721: 1: Success after gcc/linux: 24 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 (ce917f99c7) \ 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 1724 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30276 -> 30664 bytes 04-build_abe-stage1/console.log.xz | Bin 91064 -> 91336 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8836 -> 8740 bytes 07-build_abe-glibc/console.log.xz | Bin 233672 -> 234212 bytes 08-build_abe-stage2/console.log.xz | Bin 223792 -> 224532 bytes 09-build_abe-gdb/console.log.xz | Bin 37608 -> 37576 bytes 10-build_abe-qemu/console.log.xz | Bin 31000 -> 30968 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3124 -> 2904 bytes 13-check_regression/console.log.xz | Bin 5656 -> 5852 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 + 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 43 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 26 + sumfiles/g++.log.xz | Bin 2666820 -> 2661552 bytes sumfiles/g++.sum | 106 +- sumfiles/gcc.log.xz | Bin 2199392 -> 2220888 bytes sumfiles/gcc.sum | 2260 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 881392 -> 878688 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201200 -> 201144 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 428188 -> 421208 bytes sumfiles/libstdc++.sum | 14 +- 42 files changed, 1421 insertions(+), 1324 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions