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 96c610376f 242: force: #69: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 83120ed34e 241: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards c1a366554c 240: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards d2d0bc7057 239: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 1319e4e7d9 238: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards a0d51f7b2b 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 146300a769 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 382d27e16a 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 2b9823c9d7 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards fba763a231 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 3391acd3dd 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards fe5c03c695 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 0e05833fa6 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 826360e817 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 16104c3187 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 4c44aa4541 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 011dd94e5c 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards ba3f858508 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards c186f8993a 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards cfa58e070a 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 6773a8a1ad 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 6a0d0d7f38 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards e736e2f586 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards b1d49f5996 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 6677c70e3f 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 525b817d78 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 28995428ba 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 6544b7e559 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards bea8122269 214: onsuccess: #26: 1: Success after binutils: 12 commits discards b449fd9c91 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards fc3bdfe99a 212: force: #24: 1: Success after binutils: 2 commits discards bdc433f018 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards fec9e9b7e6 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 1b5d0dc5bf 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 3f903b7e8d 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 8b08f31029 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards b3257a725b 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards b562ac9548 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 45840b2ac4 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 8380eaa068 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards bb983ff0c4 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 19beab284b 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 48d886b77d 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards f6b41a640c 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards bcf3f86144 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 872010bb8e 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 3cc466d562 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards adc91f840b 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 551f3b415d 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards df46751b7e 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 3f0e8eea27 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards a30ec8f662 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards c33b34d84f 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards 99ac464b80 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards e1324626df 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards 4ff3fe459e 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards c78f7b85c9 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards c4e04f5985 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards 0acba170ff 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards 184df87015 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards e147df09a5 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards e0b467fc92 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards a3156b95ec 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards 1b5887203d 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards a980f39d54 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards 4aabf80dc9 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards 15f4391a00 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards cb500dfbed 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards ddd6ba4b6a 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards e076c96dc6 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards f2c04cebfb 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards ca8d211119 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards a2f57d0bd8 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards e82078cfb3 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards 88da549218 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards 76d5f49ca8 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards c47ad58eb0 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards c101679530 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards db70a7338f 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards 05c46868d3 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards ed4e1ac612 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards 3bbf72ddd4 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards 0545ec9598 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards dffe266a28 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards 2541c22a19 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards f5a5b6c687 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards cb2754e6f2 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards cd0d91be21 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards b1b0fdebbf 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards 80b8b05366 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards 2236e68614 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards 9e31d35cd3 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] discards fdbad4583e 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] discards e79e50513a 149: onsuccess: #684: 1: Success after linux: 10 commits discards 3c9daae322 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 8ca6e0daac 147: onsuccess: #681: 1: Success after gcc: 6 commits discards e654306dbf 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 5bca80fe46 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards 6a7f3bfc44 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards 92034a829a 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards 7e97d0b2e7 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 019f18bd5c 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new fe3117963e 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new 69691b961a 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new 51fac635e6 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new 21a90ab7ff 146: onsuccess: #680: 1: Success after binutils: 20 commits new 1be638489a 147: onsuccess: #681: 1: Success after gcc: 6 commits new 04f4e63ca5 148: onsuccess: #683: 1: Success after glibc: 9 commits new 437a1e3419 149: onsuccess: #684: 1: Success after linux: 10 commits new eba15acc72 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] new eb680dba23 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new add0bb3d26 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new 6d1255cb88 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new 11e940f8df 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new 11d20e5aea 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new bff2d1d462 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new 22778577a4 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new f8f7a23f53 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new dd2756672e 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new 126598f547 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new faf7c9d93c 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new 50e9690e0b 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new 4f33021ac7 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new c6cc914455 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new 7bd139e103 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new 7420ac7c9a 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new d89f7b39a6 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new 75a5df625e 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new b05dc76106 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new f6fdd28e13 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new 9958243090 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new 45aa770fcc 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new aba1a510ff 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new 4ca5b67db7 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new cb878fed18 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new 76078a1cba 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new 50375866b4 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new dfd47923ff 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new 1d6654bb3e 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new 94a52e8e2e 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new 2c8cedba5d 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new 0939d1105f 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new ffa82596f2 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new 6f66167e24 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new 57d906a50a 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new ee4d34cc2a 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new 28c2a58759 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new 2c5f4e0114 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new fd9341d175 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new 05f98e1675 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new 0ed2234a6f 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 51f6cea97c 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 5d6ab22eec 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new a10371b012 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 50f67bb9ae 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 0885c84a09 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new d7d0856374 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 4322c11f75 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new ccead872f5 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 8f403b66e6 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new a7dc000e3b 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 99d7ea9982 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new af6d5dfe3d 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 0e784d7713 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 1d4166ae99 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new ee65b84c51 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 1885c593f6 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 05481b29a3 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new b3928cc288 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 7578108b5f 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 994b723a52 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 4383761db8 212: force: #24: 1: Success after binutils: 2 commits new 7daaf1bd00 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new 6780c3bd81 214: onsuccess: #26: 1: Success after binutils: 12 commits new c63ea30806 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new a01dd5758a 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 8bc943bc83 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new bb2f34acd1 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 5612cbe3ed 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 10e8b441e0 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 15f20f1ef1 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 39eace3318 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new bed0d88d85 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new a395609271 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new d01b3ebc51 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 5ce91fe2ee 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new b3c4765793 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new c6f26709ba 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 6885ba8356 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 2eca85a6d6 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new deae5c8caa 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 7836550b48 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 0d0a886d50 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 36ea684b03 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new d051b4339a 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 9788e29ed0 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 87c56f5c67 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 9c349cb42a 238: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 904ee82495 239: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 75d54987a0 240: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new a3e95262d5 241: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new d1cc2bad8f 242: force: #69: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 1f29c93615 243: force: #71: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...]

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 (96c610376f) \ 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 2216 -> 2240 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2556 bytes 03-build_abe-binutils/console.log.xz | Bin 35896 -> 35908 bytes 04-build_abe-gcc/console.log.xz | Bin 204448 -> 203404 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8912 -> 8932 bytes 07-build_abe-glibc/console.log.xz | Bin 240988 -> 241452 bytes 08-build_abe-gdb/console.log.xz | Bin 34856 -> 35048 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3820 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2996 -> 3004 bytes 11-check_regression/console.log.xz | Bin 1600 -> 1600 bytes 11-check_regression/results.compare | 8 ++-- 11-check_regression/results.regressions | 8 ++-- 11-check_regression/trigger-bisect | 4 +- 12-update_baseline/console.log | 70 ++++++++++++++--------------- git/glibc_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 8 ++-- mail/results.regressions | 8 ++-- manifest.sh | 8 ++-- results | 8 ++-- sumfiles/binutils.log.xz | Bin 62652 -> 62664 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150716 -> 150712 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 122612 -> 122644 bytes sumfiles/ld.sum | 2 +- 27 files changed, 67 insertions(+), 67 deletions(-)