This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm in repository toolchain/ci/base-artifacts.
discards 28ccaa0aa4e 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards c7b7fce7de3 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 8bbd69bd96c 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 69031d3b3d8 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 51580484c89 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards f3c20a90888 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 9f0bad0b621 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 86b5669f916 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards fc32a6f0bb6 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 89f8de6fe45 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 55ee55fcbb3 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 315a285b91f 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 20e35cb65e0 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 9e77b248b66 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 4db53a884c9 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards d1f12adccab 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 66af982d494 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 75f22917cd6 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards ec2f9a9ebb2 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 70d800b3c0a 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards cfed9471c62 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 5f24001bd4d 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 8f2f83ae64c 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 374839e9518 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 07386f28f61 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards e486259d9ed 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards bcd43f2367f 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 9da29446b41 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 29b34a8ecd1 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards cbf3198b765 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards e5605dced81 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 92692fcc86b 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 2cfd1d555d8 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 95a965c491c 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards 3a5614a80b4 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 51048af6d41 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 26f9c263a01 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 0343ae824c5 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards fd4ce81e609 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 4f96512cb92 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards dbf41858fdd 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards af28551342e 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 773c3dab82f 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards f5f929503b4 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 3e5dda9bac2 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards aee28b0c1ab 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 710b9134cd4 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards b7c22281f50 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards f7371b70b74 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 42c483d492a 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards 53184e7fc74 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards 45d525219d0 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 9e42881c2cb 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards 580a445b327 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards 7434a01274c 154: onsuccess: #583: 1: Success after linux: 10 commits discards efc38d18cb3 153: onsuccess: #582: 1: Success after glibc: 9 commits discards c8052f97eda 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 8d0b54c06df 151: onsuccess: #579: 1: Success after binutils: 21 commits discards f184e94db79 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards b925a738df5 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 40e5d3368f0 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards d203129f89e 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards a402c66f25c 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards 346a619002b 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards 9572eae5a4d 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards 240cf542971 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 2f5c038cf8b 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards 6853f78a745 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards 0b0845085ac 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 70efe845e83 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 29dacffa194 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards f8a32ffd4b3 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards abcf6ad0a5d 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards 4dffefade76 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 83b88f524ca 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 04319bfe394 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards efb3f58b360 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards f6bcc72b9c2 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards 01ed1193885 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards 2af525a9d5a 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards c3f572b500a 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 702f30c0112 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 1c4205056c0 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 517bd210ca9 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 3c9faa675c9 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards 718c4f8954f 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards a78a50bd99f 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 3623aa849bb 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 891872ccb91 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 86bfd3554ca 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 5add9c5d2d7 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 7c9eda03779 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards d7073913fd4 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards bc1fff5f29e 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards 65a1068b6d6 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards af5fbbd19a3 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards e7d8b325b27 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards 4391a309789 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] discards d2db057d238 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] discards 6adfa438e91 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] discards 9df44a0df2b 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] new 07e063976f0 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] new bf55bc1d383 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] new ac99343e424 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] new b3f2930f28d 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] new d83c7b87192 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new 612ebfe7b60 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new 67508ae869d 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 5c61907c2c4 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new dbe1581bba2 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new bbaf9d5c189 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 0e607569d37 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new ec5e28d8b9b 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 9915a76a7ab 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 8bcceb5615b 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 3982ac57efb 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 86e66fea02e 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new 3cca3cfa6f5 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new a6b5d9c0931 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 89d4a7463eb 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new f2670dc1d65 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new 12f72cbfcc7 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 1fef2f70a98 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new d87f3a2970e 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new 98df8d6833e 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new dfe1016f24e 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new 9f3d26619ab 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new dcf1c2a4a0f 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new f26a79a41ab 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 248827c1808 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new 2cbbcf1312c 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new d8da57ae7a6 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new deb73647345 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 9cec31fb259 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 9a742f7bc12 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 6beea0369c0 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new b955211d612 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new c7eb11abc88 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new 66a871d8f39 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new 67f9ffcbe77 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new a5a6f7c31df 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new ab5a6ce6149 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 4da6db06f05 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 54b488bfa78 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 4ec0bf26f50 151: onsuccess: #579: 1: Success after binutils: 21 commits new 40a37bfb2c8 152: onsuccess: #580: 1: Success after gcc: 6 commits new 51059449943 153: onsuccess: #582: 1: Success after glibc: 9 commits new 1c460611863 154: onsuccess: #583: 1: Success after linux: 10 commits new 5904781f60d 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new 9400387fb07 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new 872561bc0e6 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new 0c3ac80c77e 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 07815e1e7a6 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 08bd13a93af 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 8d7475c7906 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 2bdc44dcbd9 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 7410de29131 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 02c9be8a6f8 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new b1a321a092d 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new ae35c201dde 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new df89b8f78f5 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new c8eccbfcbd3 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 9b7839928d5 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new f323bbe6f2b 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new f952b4d4268 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 5279c550d58 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new f711a5a1f8b 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 30282ee9b8d 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 99e6fe243e6 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new 8a72cceb3e0 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 599e9230f89 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new efd54f992fe 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 7b647879e9d 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new ffd51616aa1 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 45308e82ff4 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 9b992cca2cf 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new ee8453e8407 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new 2bddedc37f8 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new eb64428099b 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 473ac772e07 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new eaa9c030116 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new b7f2f51db0d 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 9c99c29e11c 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new fb80ed273c5 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new d165e0997b9 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 37e1ff75b6f 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new efdbcb04f8b 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new ac911c5d0bc 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 584319d2fd3 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 1eef3551871 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 85238d93ea0 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new ce52a248e73 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 9ec7ed20ea5 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new a1a6c2715dd 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 8b451925d82 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new dee35930d31 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 2fdfd22b5d7 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new f964344d751 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 5e244102f32 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 0d57f2637f8 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 5f7313526a3 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new d26ac98b1d7 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 30959c53f6a 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...]
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 (28ccaa0aa4e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...]
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 1756 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 52632 -> 52736 bytes 04-build_abe-gcc/console.log.xz | Bin 236388 -> 236472 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8836 -> 8280 bytes 07-build_abe-glibc/console.log.xz | Bin 237276 -> 235420 bytes 08-build_abe-gdb/console.log.xz | Bin 50516 -> 51076 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3748 -> 3748 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2028 -> 2052 bytes 11-check_regression/console.log.xz | Bin 5756 -> 5844 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 68 +++--- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +-- sumfiles/binutils.log.xz | Bin 62820 -> 62180 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 100620 -> 100616 bytes sumfiles/gas.sum | 274 +++++++++++------------ sumfiles/ld.log.xz | Bin 131984 -> 132048 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 30 files changed, 408 insertions(+), 408 deletions(-)