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 a90fb1877 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 1df385395 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards d42aaa21e 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards e42b64da9 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/gd [...] discards 714b737ee 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/gl [...] discards bac8880be 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/gl [...] discards 7ab714bc8 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/gd [...] discards 2ac1e477d 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] discards f4225ad14 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 7d67a3f8a 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] discards 20c7a3bca 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] discards bde1e6939 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits discards 37c3e6cc3 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] discards d3a1b2912 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] discards 2dc19ae73 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] discards a965c6d84 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] discards 3eb4bc22f 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 774d23ef3 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 064c7591f 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 267b79e9f 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] discards 942597a72 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] discards 0439292ba 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards 7de5dd537 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 75509b76c 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards ad9e94997 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards 9caf85c6e 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 6fdd4946c 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards 186ff70d5 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards b9ba0e385 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards 63f0213ba 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 03fa9a16a 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 69581a6fe 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards 8628ab628 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 7338df7b1 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards edaf23198 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards 988b3190f 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 1d82dc939 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards fef7e7365 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards d15dc82ff 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 075d8c1c5 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 777c6890f 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 27eb4f5b6 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards dbc4b6900 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards a1cd43b46 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 0712eab38 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 987534954 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 04aef70d0 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards e2d0ea790 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards a6d1e7edc 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards ecc5acea9 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2dd29c08c 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards 955aef7c6 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d6a45135d 74: onsuccess: 1: Successful build after linux: 44 commits discards 622c40e62 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 2f90dcf0a 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2bb1b4e14 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards 867e8e3c3 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards d40b15909 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 36ec396a1 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a1c25317d 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards eebfffd0a 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 1755cc384 65: onsuccess: 1: Successful build after gcc: 4 commits discards ca1fd292a 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9a9b6455b 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 45d145c60 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards e0a6cda77 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 52171604c 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 83d6aac58 59: onsuccess: 1: Successful build after glibc: 2 commits discards 8533b96b6 58: onsuccess: 1: Successful build after binutils: 2 commits discards b7bdf61b2 57: onsuccess: 1: Successful build after gcc: 7 commits discards 8dc5163c7 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 40fba5fac 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2f4343bff 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 53e410e66 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 33ac97bc8 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 350660f24 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 197925b82 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ffbf2b3bb 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards e9b96e439 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 9c4bca773 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 662e91716 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards a637ce288 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 32e68d8aa 44: onsuccess: 1: Successful build after linux: 34 commits discards 8f97eb5bc 43: onsuccess: 1: Successful build after gcc: 2 commits discards 619af5518 42: onsuccess: 1: Successful build after baseline build: no n [...] discards 40a83d8f5 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards fad7898ad 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 4a5b5c3ff 39: onsuccess: 1: Successful build after gcc: 2 commits discards 5eaadde2a 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 046843dc5 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards bb5bc96eb 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9fc2afbc1 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards a959d826c 34: onsuccess: 1: Successful build after gcc: 3 commits discards 1b7ed1fcc 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e1e2766cf 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 2daf71987 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 32e1b956d 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards c79bafff1 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9ab7051d7 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 56989ea74 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards baf4a3c8a 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 656e65197 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e5aa90f98 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new dd9952277 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 7fede6098 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7a3a218ce 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 55d3c0d98 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 418c3c035 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new b7b05df82 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5615129c0 34: onsuccess: 1: Successful build after gcc: 3 commits new d43d1e4ff 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 9f8997930 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d91c3b69c 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 218d095ed 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d1a4c8185 39: onsuccess: 1: Successful build after gcc: 2 commits new a22154a8e 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2bacfb96d 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9b0730539 42: onsuccess: 1: Successful build after baseline build: no n [...] new 5c46061b2 43: onsuccess: 1: Successful build after gcc: 2 commits new 457db79a2 44: onsuccess: 1: Successful build after linux: 34 commits new 993b830bc 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7906dd60c 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 7f3d6a68b 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cea172dc8 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new dcc47842d 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 24b50b4d1 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a61e31e27 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new df09c041c 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 43422bfd2 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 24214537d 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new fbbce4d01 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 866067361 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9731bdef7 57: onsuccess: 1: Successful build after gcc: 7 commits new 60f697bed 58: onsuccess: 1: Successful build after binutils: 2 commits new 43cfa8242 59: onsuccess: 1: Successful build after glibc: 2 commits new cb7b9266b 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 6a91fc17d 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 30839728a 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new e76e2c0c0 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b7efbee6a 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 6f3479732 65: onsuccess: 1: Successful build after gcc: 4 commits new 78ad44b0e 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 43047e947 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 58909e792 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 43fce54d1 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new d8b7b0232 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new 10bbbec0d 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new a2e46312c 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9eb76997d 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new fd3ea558d 74: onsuccess: 1: Successful build after linux: 44 commits new edd79fbca 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new dec5c755a 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new fe0d992c6 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e1219dd8b 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 10e75f8c8 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 8c53a1aea 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 477c92f57 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 2d7e46625 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new da69525f3 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 73686f9fe 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 1ffa07e02 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new b9434aa1c 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 2412d28ba 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 8e1b0a0a9 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new c22f72dec 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 7f03420af 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 03b59f733 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 2712aff8b 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new 5c198ccb1 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 454e4b939 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new 493bded24 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new 646799c67 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 32ce0067a 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new 3c7ef8241 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new 07fa6f853 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new 4b02043a1 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new 65c67f971 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 0750ab61a 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new 2b35d63f9 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new faceea8a2 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 3732f364e 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new ac4b6456b 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] new 696ca3211 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] new 8c392da52 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new ed5116ad8 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 78286363e 110: onsuccess: #1703: 1: Success after gcc: 6 commits new dcab2f2f4 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] new 8606484cf 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] new 28e917751 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] new 069677c39 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] new 633890d79 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits new ff4826d89 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] new 1dea96696 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] new c8706f740 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 3c7dc1573 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] new 24613f0af 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/gd [...] new 84a65d35d 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/gl [...] new a022787d1 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/gl [...] new e86520955 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/gd [...] new 5e4c89121 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 249992a72 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 7ca1a7ea9 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 5c5b9a7e7 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 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 (a90fb1877) \ 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 1688 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30664 -> 29940 bytes 04-build_abe-stage1/console.log.xz | Bin 91336 -> 90376 bytes 06-build_abe-linux/console.log.xz | Bin 8740 -> 8764 bytes 07-build_abe-glibc/console.log.xz | Bin 234212 -> 233720 bytes 08-build_abe-stage2/console.log.xz | Bin 224532 -> 223256 bytes 09-build_abe-gdb/console.log.xz | Bin 37576 -> 37180 bytes 10-build_abe-qemu/console.log.xz | Bin 30968 -> 31016 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2904 -> 2440 bytes 13-check_regression/console.log.xz | Bin 5852 -> 5300 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 25 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 70 +- 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 | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 26 - sumfiles/g++.log.xz | Bin 2661552 -> 2683832 bytes sumfiles/g++.sum | 6 +- sumfiles/gcc.log.xz | Bin 2220888 -> 2198808 bytes sumfiles/gcc.sum | 2518 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 878688 -> 877232 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201144 -> 201104 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2676 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 421208 -> 423708 bytes sumfiles/libstdc++.sum | 2 +- 42 files changed, 1382 insertions(+), 1463 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions