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 4423b08f40 240: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 34077091c5 239: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 5bcaace0bb 238: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards f513d47f14 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 5097194106 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 687e441c96 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 4d41584ac7 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards ac8ed50415 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 3f0a0aef4c 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards acea9ef875 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 4f2ed16635 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 9620bc5e5d 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards eb168b0df2 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards fd2fe26734 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 73fd683ecc 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards f0d855c823 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards ebca4619a3 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards fe9bf6612d 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 06b1dc6a56 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards f609ef8066 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards fbac3465d2 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 2b257ee1e2 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 456d013d8a 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 11b58730b5 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards be7376c12c 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 0a3035f97d 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards daf55ca643 214: onsuccess: #26: 1: Success after binutils: 12 commits discards b2b5ef0bd0 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 1db846b89a 212: force: #24: 1: Success after binutils: 2 commits discards fedfe9c385 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 3e323d693c 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 5da017ccf3 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards b79aa9623e 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 950f8795ae 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 57b461f82c 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 4770e2cc8c 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards f27113c3a5 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 92b5cf26dd 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 1567e93363 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 216cde5d49 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 6a06a5ff0f 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 2ac8f04b40 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 392bd8ddf6 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards c03e1dfd9e 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards e2096e20e5 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 0801b41a96 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 8e58ad4889 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 1c5a5ae3bf 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 616650e456 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 677cc497f6 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 1ee42c8b20 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards 31773a28ae 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards f0a2bc392a 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards 2eb75d061a 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards 0d7d5f9b66 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards 9ebb8e88fd 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards a9511209e3 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards d1790b83b7 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards bc20be59a3 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards db8645a6d8 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards 96b6e056df 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards ff8499c389 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards a1f4897521 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards f5ee21c3c7 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards dc1e251a78 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards 847c3623c2 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards 01340a8a80 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards e2a7665d31 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards 7f865e403d 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards d5bf851e7d 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards 56f25b8078 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards 87adfd9eae 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards e19bcc65b3 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards bf4237e82e 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards c570383c43 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards eae5495e74 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards a4077d0161 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards 9716adbd69 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards 41d25f00e9 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards bc021bf64e 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards 3066a3c168 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 4ac51af86e 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards 045970016c 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards c73c148116 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards a5b24b97b4 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards 8e87784827 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards c68d9d61a2 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards 2e78365c52 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards 5a2c3d7464 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards 3e50c1b9a9 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] discards 347306aaf6 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] discards 9db7663ec1 149: onsuccess: #684: 1: Success after linux: 10 commits discards aa03ff027b 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 6973c0c88d 147: onsuccess: #681: 1: Success after gcc: 6 commits discards f99b8ddfcc 146: onsuccess: #680: 1: Success after binutils: 20 commits discards aeab48b09b 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards 267bfaf8f0 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards 50cd86a5ec 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards b39ef6b8e3 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 7359cdb18f 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards 25c7e503a6 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new 0a5ae90d35 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new 6f9ba66b4a 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new 6c07e41d1e 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new ee01532393 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new eaf41e6a3f 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new 0f760cf571 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new 68d92c2fb9 146: onsuccess: #680: 1: Success after binutils: 20 commits new f33cac6fe6 147: onsuccess: #681: 1: Success after gcc: 6 commits new a84de630b6 148: onsuccess: #683: 1: Success after glibc: 9 commits new affb635e33 149: onsuccess: #684: 1: Success after linux: 10 commits new 5a8914dec3 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] new 910b0e2322 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new f561c26371 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new 9716eaeb82 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new ba6efeaf53 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new 5dd5565484 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new 836e240fc7 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new 70a1201a6e 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new c99bc79f43 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 12cef98576 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new a741160cf4 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new 3ed907a7ce 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new 7f60fac6a0 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new b7d7b03e98 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new 1b5755c399 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new febeb85e51 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new 0fc99e2cfc 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new 22472ac3db 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new 2553d4809d 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new d6294d39f4 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new 7b43e538d6 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new 0dd54bf192 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new 843c094ac6 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new f14e51f14d 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new 67615d9992 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new ff234d522a 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new 4aa3e82c3d 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new e6019149c0 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new 9b9ebf3a2b 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new 6d6537c4eb 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new 0284f9e523 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new 0d79daadbf 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new 8a205b86fe 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new c496d1700b 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new d828477ec0 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new 6bac7aa28e 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new 0d5679435b 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new 2766b8f027 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new f99478a3be 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new 26c28cda4b 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new 5960098fa7 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new 34c991f6bb 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new a9f194d3d5 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 887ff84234 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new c2b46ff30e 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new fa226fd1ab 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new fc964c3250 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new d2424f206c 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new b5dd8f458f 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 7fb329c485 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 60e4d91a04 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 8b0de202aa 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 616f6f0e87 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 217fe44115 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 2ee88f0357 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new e5cdb00577 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new c9ad68dbfa 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 5f8df0ca02 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new f1eb6d42b2 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new cbdf738008 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 7de8b396b0 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 0de77a33c1 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new a0e7531b1e 212: force: #24: 1: Success after binutils: 2 commits new 473fbc7b68 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new 5799300c47 214: onsuccess: #26: 1: Success after binutils: 12 commits new 54a44cf9fe 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new fcd6503174 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new fe679e7541 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new e0f34a19c8 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new a1103a805a 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 90cf94e6a1 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 9228f9dcde 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 26b0a4a23e 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new a084fe02fc 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 67206a84b7 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new a707cd69b2 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new debe79e06b 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new c592a9b6a1 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 164f6c6e81 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new c696c80db1 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new f4803cb2ff 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new ceeb8dc224 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 928607b5ef 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new fd9903649f 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 642c6ea819 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new bd8013c4bf 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 113401140c 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new ec3f4bffe4 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 8b5fa6632a 238: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 6917b41d37 239: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 8ba9ac883f 240: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new f1c5df514d 241: force: #67: 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 (4423b08f40) \ 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 -> 2200 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 35672 -> 36524 bytes 04-build_abe-gcc/console.log.xz | Bin 204260 -> 205352 bytes 06-build_abe-linux/console.log.xz | Bin 8900 -> 8912 bytes 07-build_abe-glibc/console.log.xz | Bin 240628 -> 240764 bytes 08-build_abe-gdb/console.log.xz | Bin 34608 -> 34848 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3824 bytes 10-build_abe-check_binutils/console.log.xz | Bin 3000 -> 3004 bytes 11-check_regression/console.log.xz | Bin 1604 -> 1628 bytes 11-check_regression/trigger-bisect | 4 +-- 12-update_baseline/console.log | 38 ++++++++++++++--------------- git/gcc_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 10 ++++---- sumfiles/binutils.log.xz | Bin 62812 -> 62644 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150840 -> 150772 bytes sumfiles/gas.sum | 2 +- sumfiles/ld.log.xz | Bin 122640 -> 122616 bytes sumfiles/ld.sum | 2 +- 21 files changed, 31 insertions(+), 31 deletions(-)