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-aarch64 in repository toolchain/ci/base-artifacts.

discards 381fecf5a5 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards d098b6c3c1 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 3144670189 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 54fdb1717b 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards baed829562 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 367fddfb0a 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 894ab7281e 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 435ccc01f3 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 1dc131a7aa 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 29acad32dd 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 8e261db9ca 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 0db3c4fa13 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards c4ed7b818f 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 35d9f94c81 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 6e063f18c4 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 25b8e380e3 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards ae9bdcff94 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 12ddb6b14a 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards c8d6eccded 212: force: #24: 1: Success after binutils: 2 commits discards fb000a7dd2 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 8c863863be 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 96c29d4429 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 56fa491ee8 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards d52d2e7332 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards bbd578ffb8 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards f8d8b9fe1e 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 914ee2f99a 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 49b6462926 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards b75327ab37 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 2b8ead3792 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 09ef13a98c 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 56fce32fa1 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards d4be09ccb5 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards e03204de14 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards f61db2cbd4 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 4df5747a58 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 4da350f493 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards d1da52d4a9 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards eeb487c12f 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 474433420e 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 7760302bc8 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards 8c884d01c0 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards 57e75c76a8 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards 220d7b478d 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards ddf209323d 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards eec40378ca 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards d5546f577a 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards bbfc09541f 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards 16eb115338 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards 684b21ee4c 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards 885e06b034 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards 90fa632daf 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards 57e0ed29cc 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards 325fa8d8fc 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards ef1eec7b0f 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards 0ce0df3dba 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards 02339085fe 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards 0787993e49 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards 2e09f93645 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards 34333c9f62 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards 3b919620d5 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards 541729d3d0 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards 7690aae308 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards e930695747 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards 65f5239a70 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards 04fa6d3c0c 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards e485dc6419 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards d98de22b28 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards 193bf00eba 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards 620c598767 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards 625046292e 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 6a5612d45d 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards d7bcb8bc67 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards a3c8bcc71f 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards 402e40a284 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards 5f62baeca5 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards de7c4ef58e 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards ff85a260ca 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards 308d199ff5 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards 7fa5c0ecb2 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] discards fd4cf21b27 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] discards 4916da7399 149: onsuccess: #684: 1: Success after linux: 10 commits discards 99e9955646 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 18d982f9a6 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 52b9b5dac5 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 27a39229b4 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards 7072371de8 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards fbe992caf7 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards 70552a95a2 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 981cf358f1 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards 263c83a9f7 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards 2058620d0a 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards e6719a8792 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards fe03b33bac 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits discards ec56d6f061 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards a5ea02f539 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards d5c4c4d4df 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] discards d5f0ca2936 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] discards 4cba947ed5 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards bdd45a3cc3 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards de51b841f9 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 7face8fdb1 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 29c4e986bd 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new 153b7babaa 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new c2b399a03b 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] new 91b5d9adcb 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] new 3c9a46e5d6 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new e968d26310 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new 934d0df149 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new 936ceff840 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new 046133f22d 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new 1a18bb7221 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new eec9717dba 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new a128f5b52a 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 1faf22d051 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new d2ec0ca702 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new b858e6981c 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new c370462dd1 146: onsuccess: #680: 1: Success after binutils: 20 commits new 6e508dea88 147: onsuccess: #681: 1: Success after gcc: 6 commits new 6bcc9cf6b6 148: onsuccess: #683: 1: Success after glibc: 9 commits new ed5f7251be 149: onsuccess: #684: 1: Success after linux: 10 commits new 52beface80 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] new 3ba523c86f 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new 243d677a10 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new ea438cf888 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new 491b8fec95 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new fb94f69f9a 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new b82df59a82 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new 99a1c7fa6b 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new b06ab93d28 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 7e89b871f1 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new 3a7fe8b91b 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new ba993358d7 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new d6fdfe22fd 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new ee7d4db11c 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new ea23ff756d 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new 1a108154e2 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new 6bf1947053 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new f76f54ae2e 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new bf0428a6ae 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new 84e5c9b6eb 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new 798c63936b 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new 8bbe5ce923 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new 9149031835 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new 48bd514c15 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new cb9a410c15 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new 96d0aba18b 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new 19d4e66499 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new 2a1195d322 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new e3ace85615 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new 80926727f9 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new 02c2085ef5 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new 9e5c765b6a 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new 49d4b63a24 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new 2c98fcb45b 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new 830b0393af 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new a2360cbaef 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new 370d8ade33 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new 1718869d74 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new c8fcca39be 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new a4ad71f491 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new fc188178d6 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new 377869f210 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new dff6976434 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 42be39a80a 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 6031607c19 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new d043479864 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new a2c9b469d8 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 7635033097 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 281847a24a 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 13a2b4c16e 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new e1e1352322 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new cbc5c60039 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new a000eb015f 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 7b0b0e2704 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 0205eb3a9c 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 1b5bfde78f 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new a882545888 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new f28386bb94 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 470463d589 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 83a14c2c6b 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 2737c4ab60 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new def10a83fa 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new ab4aa4d416 212: force: #24: 1: Success after binutils: 2 commits new 60e5a7df27 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new de7fd3c03c 214: onsuccess: #26: 1: Success after binutils: 12 commits new 88bb9909e1 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new d64a488118 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 8f72b0b1f6 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new fe4e97d1d6 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 5e8c010161 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 2c71c4c32f 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new f347b942b3 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 91cef9cb38 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new f3dff46b19 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 73c68ca10c 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new dfb8bd24f1 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 22845bf622 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new d6481d1aed 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 944082d039 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new b18050e28e 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 48000fff39 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 8a868996a2 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...]

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 (381fecf5a5) \ 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 -> 2056 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 35212 -> 35192 bytes 04-build_abe-gcc/console.log.xz | Bin 204024 -> 203488 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8764 -> 9468 bytes 07-build_abe-glibc/console.log.xz | Bin 241364 -> 241216 bytes 08-build_abe-gdb/console.log.xz | Bin 34748 -> 34908 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3792 -> 3788 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2176 -> 2404 bytes 11-check_regression/console.log.xz | Bin 4948 -> 5124 bytes 11-check_regression/results.compare | 8 ++--- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 40 ++++++++++----------- 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 | 56 +++++++++++++++-------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 36 +++++++++---------- manifest.sh | 38 ++++++++++---------- sumfiles/binutils.log.xz | Bin 63076 -> 62992 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150792 -> 150688 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122636 -> 122608 bytes sumfiles/ld.sum | 4 +-- 30 files changed, 106 insertions(+), 102 deletions(-)