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 8c458f29baa1 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/g [...] discards a45d3e98fe46 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] discards 8d5e03471eeb 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] discards b5ddab437cb9 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards dba4a56e4e98 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards 7cb21fc94d6b 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards 97937c2b9569 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards f3dfafcc7b03 222: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 8df151b5b5f9 221: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards 1499b0c92538 220: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards 264334cea8f3 219: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards 250b8fa5a311 218: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 1b21953ebb54 217: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards 2381c30c9b54 216: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards 0fb55f8adc73 215: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards 3e23c69b5712 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 9395fe56d4d3 213: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] discards 4d7db6fd029d 212: force: #24: 1: Success after binutils: 2 commits discards eb2545b6cb56 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 296a1f94dd84 210: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 91f17edd6d49 209: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 3462e35b8a58 208: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards b45711124f37 207: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 67937e41d005 206: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 86ff93eab152 205: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards a48b788cd3ab 204: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 09826850b641 203: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards 923bd488c80f 202: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards c645a4090aa5 201: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 4ba2dc96c398 200: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards efe51bcb9dcd 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 58e5a338b37a 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 4059f7fba120 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards fd5cf3b01eb2 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 765a43e93adc 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 93d1b1a49317 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards 98c781a0c2be 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 845c624d1b6a 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards 17ead7b98077 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards f753faca5c5c 190: onsuccess: #726: 1: Success after binutils/gcc/linux/ [...] discards ba86421a4596 189: onsuccess: #725: 1: Success after binutils/gcc/linux/ [...] discards 5a6fcb805b3b 188: onsuccess: #724: 1: Success after binutils/gcc/linux/ [...] discards dfd33479463e 187: onsuccess: #723: 1: Success after binutils/gcc/linux/ [...] discards 0d917a62745b 186: onsuccess: #722: 1: Success after binutils/gcc/linux/ [...] discards c1c0d5642f17 185: onsuccess: #721: 1: Success after binutils/gcc/linux/ [...] discards bf64d1ce9bc6 184: onsuccess: #720: 1: Success after binutils/gcc/linux/ [...] discards 8c57bfedb42c 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 2 [...] discards 04170f39798d 182: onsuccess: #718: 1: Success after binutils/gcc/linux/ [...] discards 67f35e072af5 181: onsuccess: #717: 1: Success after binutils/gcc/linux/ [...] discards 5a11bbbc3d16 180: onsuccess: #716: 1: Success after binutils/gcc/linux/ [...] discards 159aca40adc8 179: onsuccess: #715: 1: Success after binutils/gcc/linux/ [...] discards b69474c793f2 178: onsuccess: #714: 1: Success after binutils/gcc/linux/ [...] discards 499f6f243709 177: onsuccess: #712: 1: Success after binutils/gcc/linux/ [...] discards 3c045ebf5d39 176: onsuccess: #711: 1: Success after binutils/gcc/linux/ [...] discards f718a02b654d 175: onsuccess: #710: 1: Success after binutils/gcc/linux/ [...] discards bde7f53796e3 174: onsuccess: #709: 1: Success after binutils/gcc/linux/ [...] discards a4897a41ff2f 173: onsuccess: #708: 1: Success after binutils/gcc/linux/ [...] discards 628e8f64ad10 172: onsuccess: #707: 1: Success after binutils/gcc/linux/ [...] discards 59a63452dc25 171: onsuccess: #706: 1: Success after binutils/gcc/linux/ [...] discards aa39407ef183 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/ [...] discards 74f9e2785237 169: onsuccess: #704: 1: Success after binutils/gcc/linux/ [...] discards a3f3a9028005 168: onsuccess: #703: 1: Success after binutils/gcc/linux/ [...] discards 2cd5f0d91919 167: onsuccess: #702: 1: Success after binutils/gcc/linux/ [...] discards e2d5d19b0aa6 166: onsuccess: #701: 1: Success after binutils/gcc/linux/ [...] discards 7e2edb5c8044 165: onsuccess: #700: 1: Success after binutils/gcc/linux/ [...] discards 48dcd4009d75 164: onsuccess: #699: 1: Success after binutils/gcc/linux/ [...] discards d81cf55f563b 163: onsuccess: #698: 1: Success after binutils/gcc/linux/ [...] discards 389239239fb6 162: onsuccess: #697: 1: Success after binutils/gcc/linux/ [...] discards e4fc9c235adf 161: onsuccess: #696: 1: Success after binutils/gcc/linux/ [...] discards 63e14627e8a0 160: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] discards 77a7b23289f0 159: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] discards 168a97ea306e 158: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] discards 116bd3157a8f 157: onsuccess: #692: 1: Success after binutils/gcc/linux/ [...] discards 05eb218d30f2 156: onsuccess: #691: 1: Success after binutils/gcc/linux/ [...] discards fe36e96cb8af 155: onsuccess: #690: 1: Success after binutils/gcc/linux/ [...] discards aacf1e3445b0 154: onsuccess: #689: 1: Success after binutils/gcc/linux/ [...] discards 29ad57c95e6d 153: onsuccess: #688: 1: Success after binutils/gcc/linux/ [...] discards 7847cb0f968d 152: onsuccess: #687: 1: Success after binutils/gcc/linux/ [...] discards c0b886386ed5 151: onsuccess: #686: 1: Success after binutils/gcc/linux/ [...] discards 4d2ddd438307 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/ [...] discards 0d3cd0ee3b85 149: onsuccess: #684: 1: Success after linux: 10 commits discards 3e0e92a57870 148: onsuccess: #683: 1: Success after glibc: 9 commits discards df2a9d50c8a9 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 4730eab9c57f 146: onsuccess: #680: 1: Success after binutils: 20 commits discards cf8cda970e8c 145: onsuccess: #678: 1: Success after binutils/gcc/linux/ [...] discards a6aef6cad6f6 144: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] discards 9185e9ef25a1 143: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] discards 702e0e596edb 142: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] discards 95bba4743fee 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 1 [...] discards 46f4fba8b435 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 2 [...] discards b58e52972431 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 2 [...] discards 5c6084d88410 138: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] discards 7e54febbcb64 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 4 [...] discards de692f72b262 136: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] discards b04f80cf0c42 135: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] discards b86a92acf2ad 134: onsuccess: #667: 1: Success after binutils/gcc/linux/ [...] discards c88976e18105 133: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] discards 31d20fe9930d 132: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] discards b008ada3194a 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] discards 8f358b185dd4 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] discards 846351a1fd65 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new 6149f4575401 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new de51b841f902 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] new bdd45a3cc352 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] new 4cba947ed529 132: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] new d5f0ca2936c3 133: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] new d5c4c4d4df9b 134: onsuccess: #667: 1: Success after binutils/gcc/linux/ [...] new a5ea02f539ee 135: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] new ec56d6f06126 136: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] new fe03b33bac5c 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 4 [...] new e6719a87923a 138: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] new 2058620d0aea 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 2 [...] new 263c83a9f737 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 2 [...] new 981cf358f1e4 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 1 [...] new 70552a95a216 142: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] new fbe992caf723 143: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] new 7072371de804 144: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] new 27a39229b480 145: onsuccess: #678: 1: Success after binutils/gcc/linux/ [...] new 52b9b5dac58b 146: onsuccess: #680: 1: Success after binutils: 20 commits new 18d982f9a607 147: onsuccess: #681: 1: Success after gcc: 6 commits new 99e9955646d1 148: onsuccess: #683: 1: Success after glibc: 9 commits new 4916da739947 149: onsuccess: #684: 1: Success after linux: 10 commits new fd4cf21b2727 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/ [...] new 7fa5c0ecb200 151: onsuccess: #686: 1: Success after binutils/gcc/linux/ [...] new 308d199ff5b9 152: onsuccess: #687: 1: Success after binutils/gcc/linux/ [...] new ff85a260ca29 153: onsuccess: #688: 1: Success after binutils/gcc/linux/ [...] new de7c4ef58eee 154: onsuccess: #689: 1: Success after binutils/gcc/linux/ [...] new 5f62baeca5c2 155: onsuccess: #690: 1: Success after binutils/gcc/linux/ [...] new 402e40a284be 156: onsuccess: #691: 1: Success after binutils/gcc/linux/ [...] new a3c8bcc71fc2 157: onsuccess: #692: 1: Success after binutils/gcc/linux/ [...] new d7bcb8bc6735 158: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] new 6a5612d45d3b 159: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] new 625046292e29 160: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] new 620c5987672b 161: onsuccess: #696: 1: Success after binutils/gcc/linux/ [...] new 193bf00ebacc 162: onsuccess: #697: 1: Success after binutils/gcc/linux/ [...] new d98de22b284e 163: onsuccess: #698: 1: Success after binutils/gcc/linux/ [...] new e485dc641945 164: onsuccess: #699: 1: Success after binutils/gcc/linux/ [...] new 04fa6d3c0c1a 165: onsuccess: #700: 1: Success after binutils/gcc/linux/ [...] new 65f5239a7056 166: onsuccess: #701: 1: Success after binutils/gcc/linux/ [...] new e9306957474c 167: onsuccess: #702: 1: Success after binutils/gcc/linux/ [...] new 7690aae3088a 168: onsuccess: #703: 1: Success after binutils/gcc/linux/ [...] new 541729d3d0fa 169: onsuccess: #704: 1: Success after binutils/gcc/linux/ [...] new 3b919620d511 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/ [...] new 34333c9f62db 171: onsuccess: #706: 1: Success after binutils/gcc/linux/ [...] new 2e09f93645db 172: onsuccess: #707: 1: Success after binutils/gcc/linux/ [...] new 0787993e498b 173: onsuccess: #708: 1: Success after binutils/gcc/linux/ [...] new 02339085fe73 174: onsuccess: #709: 1: Success after binutils/gcc/linux/ [...] new 0ce0df3dba93 175: onsuccess: #710: 1: Success after binutils/gcc/linux/ [...] new ef1eec7b0fd8 176: onsuccess: #711: 1: Success after binutils/gcc/linux/ [...] new 325fa8d8fc97 177: onsuccess: #712: 1: Success after binutils/gcc/linux/ [...] new 57e0ed29ccf3 178: onsuccess: #714: 1: Success after binutils/gcc/linux/ [...] new 90fa632daf26 179: onsuccess: #715: 1: Success after binutils/gcc/linux/ [...] new 885e06b03484 180: onsuccess: #716: 1: Success after binutils/gcc/linux/ [...] new 684b21ee4c36 181: onsuccess: #717: 1: Success after binutils/gcc/linux/ [...] new 16eb11533844 182: onsuccess: #718: 1: Success after binutils/gcc/linux/ [...] new bbfc09541fc5 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 2 [...] new d5546f577a7e 184: onsuccess: #720: 1: Success after binutils/gcc/linux/ [...] new eec40378ca5b 185: onsuccess: #721: 1: Success after binutils/gcc/linux/ [...] new ddf209323dfe 186: onsuccess: #722: 1: Success after binutils/gcc/linux/ [...] new 220d7b478d8c 187: onsuccess: #723: 1: Success after binutils/gcc/linux/ [...] new 57e75c76a8e9 188: onsuccess: #724: 1: Success after binutils/gcc/linux/ [...] new 8c884d01c06b 189: onsuccess: #725: 1: Success after binutils/gcc/linux/ [...] new 7760302bc8db 190: onsuccess: #726: 1: Success after binutils/gcc/linux/ [...] new 474433420e56 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new eeb487c12f15 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new d1da52d4a98f 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 4da350f4934e 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new 4df5747a58a4 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new f61db2cbd486 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new e03204de1411 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new d4be09ccb5a6 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 56fce32fa12d 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 09ef13a98ca7 200: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 2b8ead3792f9 201: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new b75327ab3791 202: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 49b6462926c7 203: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 914ee2f99a9c 204: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new f8d8b9fe1edc 205: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new bbd578ffb8e4 206: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new d52d2e7332d6 207: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 56fa491ee853 208: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 96c29d44298a 209: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 8c863863bea5 210: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new fb000a7dd273 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new c8d6eccded26 212: force: #24: 1: Success after binutils: 2 commits new 12ddb6b14aec 213: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] new ae9bdcff9468 214: onsuccess: #26: 1: Success after binutils: 12 commits new 25b8e380e37c 215: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 6e063f18c43c 216: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 35d9f94c8131 217: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new c4ed7b818f54 218: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 0db3c4fa1365 219: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new 8e261db9ca25 220: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 29acad32dd4b 221: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new 1dc131a7aaea 222: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new 435ccc01f3ba 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 894ab7281eee 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new 367fddfb0a36 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new baed8295628a 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new 54fdb1717bbc 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] new 31446701896f 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] new d098b6c3c17e 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/g [...] new 381fecf5a5ed 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/g [...]

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 (8c458f29baa1) \ 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 2024 -> 2028 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2536 bytes 03-build_abe-binutils/console.log.xz | Bin 35512 -> 35212 bytes 04-build_abe-gcc/console.log.xz | Bin 203356 -> 204024 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8676 -> 8764 bytes 07-build_abe-glibc/console.log.xz | Bin 242028 -> 241364 bytes 08-build_abe-gdb/console.log.xz | Bin 35304 -> 34748 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3792 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2784 -> 2176 bytes 11-check_regression/console.log.xz | Bin 5084 -> 4948 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/changes-list-long.txt | 55 +++++++++++------------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 ++++++++-------- manifest.sh | 36 +++++++-------- sumfiles/binutils.log.xz | Bin 62668 -> 63076 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150780 -> 150792 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 122616 -> 122636 bytes sumfiles/ld.sum | 4 +- 30 files changed, 116 insertions(+), 119 deletions(-)