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 771cdce398 239: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards c8fabdfa31 238: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 1728609b35 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 198abf17eb 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 7eeaa22eb4 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 880bba8370 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards efac6678d1 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards a58208f3b2 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 53b99e8b36 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards bc54d00084 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 2632060e5c 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 9112f59c85 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 51c5616de6 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards c11372ae1b 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 989871a908 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 444c215f50 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards ccd9297ae7 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards f2e8652102 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 74eb509564 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards d1072bfbb6 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 370bbcc9e2 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 7825ee3f86 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards b91228ff44 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 1f172b9107 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 9ce3f79fcd 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards a6d3aacb14 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 7336111276 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 708c2ab349 212: force: #24: 1: Success after binutils: 2 commits discards 5455eda74d 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 8770d43e95 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards c54ffa1427 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards d003382895 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 40f1f4fe0d 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 3b1ac49cb4 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards ab48b14e03 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 1dc1841e36 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 72f57e9864 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards f1ff805494 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 1615c8b744 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 6dd8b8cfbb 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 795de34adf 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards d80dfcd62f 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 7d958aa674 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 689fa18633 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 0026b89e08 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards ba48c836ea 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 037407000e 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 6ab6bc3d06 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 46de3f3b7d 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 13a4a52c8b 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards 9674e8652b 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards 0fda204a83 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards d5e1e83f26 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards bc0c74a5b1 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards e9797acc1b 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards c52e8ea3be 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards 02fce028f4 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards 002abd18fa 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards 6493f1c245 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards 5ebb3b5300 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards bb9d948dcb 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards 59bb242bc3 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards b4b6689630 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards 840810e613 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards 80dd6bac4b 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards ceb4d80780 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards a800c39d85 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards d23cf955f7 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards 63eff9d4f8 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards 1e41b3dbaa 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards ce324cca81 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards cdb983ad32 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards a4a1cc03f3 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards 757938866e 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards eb707e5a4a 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards 349150c193 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards 2e8fb57560 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards 9da8c88a3b 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards 1ec9e0c305 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards df77fd212d 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards f4bd4cdd6d 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards 8c45a940a3 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards 7dd5fd6ca5 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards a0b4a04ced 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards 8576e20dca 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards 0f8f440e6b 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards fac997567c 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards ec09728d1d 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards 7afc7d1f6c 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] discards ff2a6282d5 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] discards 30ed5c1599 149: onsuccess: #684: 1: Success after linux: 10 commits discards 72bf281c2e 148: onsuccess: #683: 1: Success after glibc: 9 commits discards cca5a5cf3c 147: onsuccess: #681: 1: Success after gcc: 6 commits discards dc8262a442 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 16e51309d6 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards f05a8dd3f1 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards d9ff4092fa 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards 339018ae3a 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 7915902884 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards 39f34c3e44 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards 4cad5de988 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new 4ef217ceed 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new 25c7e503a6 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new 7359cdb18f 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new b39ef6b8e3 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 50cd86a5ec 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new 267bfaf8f0 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new aeab48b09b 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new f99b8ddfcc 146: onsuccess: #680: 1: Success after binutils: 20 commits new 6973c0c88d 147: onsuccess: #681: 1: Success after gcc: 6 commits new aa03ff027b 148: onsuccess: #683: 1: Success after glibc: 9 commits new 9db7663ec1 149: onsuccess: #684: 1: Success after linux: 10 commits new 347306aaf6 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] new 3e50c1b9a9 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new 5a2c3d7464 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new 2e78365c52 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new c68d9d61a2 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new 8e87784827 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new a5b24b97b4 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new c73c148116 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new 045970016c 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 4ac51af86e 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new 3066a3c168 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new bc021bf64e 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new 41d25f00e9 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new 9716adbd69 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new a4077d0161 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new eae5495e74 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new c570383c43 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new bf4237e82e 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new e19bcc65b3 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new 87adfd9eae 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new 56f25b8078 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new d5bf851e7d 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new 7f865e403d 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new e2a7665d31 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new 01340a8a80 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new 847c3623c2 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new dc1e251a78 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new f5ee21c3c7 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new a1f4897521 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new ff8499c389 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new 96b6e056df 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new db8645a6d8 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new bc20be59a3 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new d1790b83b7 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new a9511209e3 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new 9ebb8e88fd 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new 0d7d5f9b66 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new 2eb75d061a 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new f0a2bc392a 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new 31773a28ae 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new 1ee42c8b20 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new 677cc497f6 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 616650e456 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 1c5a5ae3bf 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 8e58ad4889 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 0801b41a96 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new e2096e20e5 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new c03e1dfd9e 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 392bd8ddf6 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 2ac8f04b40 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 6a06a5ff0f 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 216cde5d49 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 1567e93363 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 92b5cf26dd 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new f27113c3a5 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 4770e2cc8c 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 57b461f82c 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 950f8795ae 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new b79aa9623e 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 5da017ccf3 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 3e323d693c 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new fedfe9c385 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 1db846b89a 212: force: #24: 1: Success after binutils: 2 commits new b2b5ef0bd0 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new daf55ca643 214: onsuccess: #26: 1: Success after binutils: 12 commits new 0a3035f97d 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new be7376c12c 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 11b58730b5 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 456d013d8a 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 2b257ee1e2 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new fbac3465d2 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new f609ef8066 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 06b1dc6a56 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new fe9bf6612d 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new ebca4619a3 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new f0d855c823 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 73fd683ecc 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new fd2fe26734 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new eb168b0df2 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 9620bc5e5d 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 4f2ed16635 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new acea9ef875 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 3f0a0aef4c 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new ac8ed50415 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 4d41584ac7 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 687e441c96 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 5097194106 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new f513d47f14 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 5bcaace0bb 238: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 34077091c5 239: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 4423b08f40 240: force: #65: 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 (771cdce398) \ 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 1972 -> 2216 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 35196 -> 35672 bytes 04-build_abe-gcc/console.log.xz | Bin 204320 -> 204260 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8892 -> 8900 bytes 07-build_abe-glibc/console.log.xz | Bin 241360 -> 240628 bytes 08-build_abe-gdb/console.log.xz | Bin 34656 -> 34608 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3828 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2304 -> 3000 bytes 11-check_regression/console.log.xz | Bin 1600 -> 1604 bytes 11-check_regression/results.compare | 8 ++--- 11-check_regression/results.regressions | 8 ++--- 11-check_regression/trigger-bisect | 2 +- 12-update_baseline/console.log | 46 ++++++++++++++--------------- git/binutils_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 8 ++--- mail/results.regressions | 8 ++--- manifest.sh | 10 +++---- results | 8 ++--- sumfiles/binutils.log.xz | Bin 62620 -> 62812 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150676 -> 150840 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122616 -> 122640 bytes sumfiles/ld.sum | 2 +- 27 files changed, 55 insertions(+), 55 deletions(-)