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 89647a69797 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gc [...] discards f9a3f0adf8e 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gc [...] discards 77c05d0f8ff 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gl [...] discards 23ebd0fcd93 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] discards f70c8604148 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards e00e56b21c9 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards cc3bd16ae82 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards e1060aae86c 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards 958f95bd831 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 1655326d9f5 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards d1fd811441e 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards d0229419bf8 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 74d16ebdcb5 215: onsuccess: #26: 1: Success after binutils: 10 commits discards c3f8ab97f2e 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards 23c0041447b 213: force: #24: 1: Success after binutils: 2 commits discards bbb3a23bc17 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 2550af6f968 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards e51828ceaae 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards c0844062d26 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 5d49cb71e7d 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 1b2ab850776 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards aa45b887618 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 429d4619f90 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 6697c4a71c3 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 46c2925dc6b 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 578d92d1e5f 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 01e7dc3778f 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards aac2fd94db2 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 4269bdc218f 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 4e7aa26761c 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 4d1f97db365 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards acb61581269 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 9d3ef31d9be 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 8ff800dacc2 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 74265a688eb 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 0f0d4dd38df 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 0bded0f3924 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 97d1897b270 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 17505096fee 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards cc6dec8c2b1 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 47e1e2a429c 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 43e024dd187 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 6f334a5a931 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 18387c44bc0 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards c5d25f4f927 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards f351c70a97c 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 210d51ac1fe 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards c7b07500a81 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards eca1cc56f64 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 66f37390c74 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards ae041a3921b 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards a615e503f62 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 8c1ecf0260b 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards 556d42d1cef 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 7e5e5b50f96 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards ffc68c94b0f 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards bcd91dfc7cf 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 651d31d4b4a 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 4ad84d41854 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards 2dce904b9f3 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards a75086fecf4 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards c3f4b76b30f 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards a7c3b42bc09 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 5a43e3ca2c7 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 24e559a8fe8 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 65f89e5d749 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 2c9d68db81a 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 8d584328f32 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 4e8b8fc73ac 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards 9825892ce5d 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards 27ae3cc2b14 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 5038016f76d 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards 140a5be1e05 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards b05b88ee7f9 154: onsuccess: #583: 1: Success after linux: 10 commits discards d0608248681 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 23b07d9356c 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 009d4b2bd41 151: onsuccess: #579: 1: Success after binutils: 21 commits discards dad9a9d84cc 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 93c4f3d78cd 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 9be4a2a9e4f 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 58109c916da 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards aa908a28450 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards bef805adcc0 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards c0c6bebd52a 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards f782e1f8349 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 9a714339851 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards e99dd6e51ce 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards d52ba69176f 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards d66484e1d03 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards c206d5d961d 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards afb07386135 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards e63c3ce3830 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards 297eb4549a6 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 283e5785d36 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 7a8e974666f 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 94e4c41b900 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards 42fc582eab2 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards a52e80127eb 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards eccac6800fe 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards a6cd809de39 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards da7dcb09fc7 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new 2dc2778a481 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new 38304092d10 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new d03c9733e71 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new f549c00b5b0 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new beed6f06c59 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new aac4ea642f5 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new fb339f1bc43 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new db5371fa430 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 98d9f921e35 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 0db2ed28ca5 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new bba7ea740be 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new f52aad8bf7f 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new a1f525482ae 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 665659384dc 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 2847f55f0c1 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 67b2329beba 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new b891bc98b4a 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new 29a4671bc3d 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new b2a3d5b4b2a 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new 89f6c5ba9ec 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new a34935f6530 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new cbfb3c72ef0 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new d9bb5d184ae 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new ec9cf3994ba 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 587f5815180 151: onsuccess: #579: 1: Success after binutils: 21 commits new 28ae1bc54f1 152: onsuccess: #580: 1: Success after gcc: 6 commits new 40f16f4be2a 153: onsuccess: #582: 1: Success after glibc: 9 commits new 4c8f1e7048c 154: onsuccess: #583: 1: Success after linux: 10 commits new bc8380a6332 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new bfbde6be3f6 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new 2b908da31ba 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new 91fad1f13a1 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new b1226dc5149 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new ed85d21c130 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new a1755405f58 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new f58a8ff20c9 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new e72c8710798 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 6ff34a26de5 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 4e1c03cb3c5 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new bac60aff09d 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 8cf2558c5cc 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new d98621da972 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new ea8f571d517 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new ec136863211 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new 9e2075df058 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 27e99c9e042 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 11f75ac548e 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new dc063f11ca6 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 7dcebad02b7 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new e30b86c4470 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 887c5ebbf5a 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 2c1e88319f2 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new fe12d207316 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 514760f3b57 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 0135667723d 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new ece68ef3467 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new fe877b8c1fd 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new e37f535d93f 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new b003c28356e 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new cf2282b6d3c 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 7a7ce3276cb 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 924051661a4 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new ed0ae0bab20 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 29539752367 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new a139d7af437 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 5120b732f57 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 964418e8bd3 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 3e1adcf0725 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 9b3f7b37fa8 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new f56c8e8b845 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 547bfbb345a 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new a446b2ecccc 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 1a54366ca66 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 01535574613 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new a7363e2a8d2 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 5713bee3e48 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new c0ed873fbea 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 5bc56a50d57 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new ddf53c3cf80 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new c7e67123d22 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 5db7d486636 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new ddec2beb23a 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 09113a91354 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 69e156cce64 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new e2c6ffee95b 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new d509a4ff6b3 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 52841cac6be 213: force: #24: 1: Success after binutils: 2 commits new fcad06b721e 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new d5ccc730495 215: onsuccess: #26: 1: Success after binutils: 10 commits new 0bed005b3d6 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 712da74ad55 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 3fd6e7e60d7 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 047e0e059e2 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 6af9538a327 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new dd53c2c080b 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new 1baecc07993 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new 082d57ce9ee 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new 4b9c5cd0a3f 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] new b3a4506cdb1 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gl [...] new a4b6b3fa523 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gc [...] new 8e0a6fe2ad8 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gc [...] new d0598251464 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gc [...]
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 (89647a69797) \ 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 2028 -> 2036 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 49164 -> 48804 bytes 04-build_abe-gcc/console.log.xz | Bin 236380 -> 236820 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8376 -> 8440 bytes 07-build_abe-glibc/console.log.xz | Bin 232072 -> 231984 bytes 08-build_abe-gdb/console.log.xz | Bin 46900 -> 46732 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3792 -> 3772 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2140 -> 2104 bytes 11-check_regression/console.log.xz | Bin 4996 -> 5004 bytes 11-check_regression/results.compare | 8 ++--- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 44 ++++++++++++------------ 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/changes-list-long.txt | 53 ++++++++++++++--------------- mail/changes-list-short.txt | 2 +- manifest.sh => mail/last_good.sh | 0 manifest.sh | 38 ++++++++++----------- sumfiles/binutils.log.xz | Bin 62592 -> 62988 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100616 -> 100660 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132260 -> 132232 bytes sumfiles/ld.sum | 4 +-- 30 files changed, 86 insertions(+), 87 deletions(-) copy manifest.sh => mail/last_good.sh (100%)