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 f1c5df514d 241: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 8ba9ac883f 240: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 6917b41d37 239: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 8b5fa6632a 238: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards ec3f4bffe4 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 113401140c 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards bd8013c4bf 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 642c6ea819 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards fd9903649f 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 928607b5ef 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards ceeb8dc224 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards f4803cb2ff 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards c696c80db1 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 164f6c6e81 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards c592a9b6a1 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards debe79e06b 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards a707cd69b2 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 67206a84b7 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards a084fe02fc 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 26b0a4a23e 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 9228f9dcde 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 90cf94e6a1 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards a1103a805a 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards e0f34a19c8 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards fe679e7541 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards fcd6503174 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 54a44cf9fe 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 5799300c47 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 473fbc7b68 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards a0e7531b1e 212: force: #24: 1: Success after binutils: 2 commits discards 0de77a33c1 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 7de8b396b0 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards cbdf738008 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards f1eb6d42b2 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 5f8df0ca02 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards c9ad68dbfa 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards e5cdb00577 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 2ee88f0357 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 217fe44115 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 616f6f0e87 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 8b0de202aa 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 60e4d91a04 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 7fb329c485 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards b5dd8f458f 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards d2424f206c 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards fc964c3250 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards fa226fd1ab 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards c2b46ff30e 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 887ff84234 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards a9f194d3d5 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 34c991f6bb 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 5960098fa7 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards 26c28cda4b 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards f99478a3be 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards 2766b8f027 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards 0d5679435b 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards 6bac7aa28e 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards d828477ec0 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards c496d1700b 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards 8a205b86fe 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards 0d79daadbf 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards 0284f9e523 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards 6d6537c4eb 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards 9b9ebf3a2b 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards e6019149c0 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards 4aa3e82c3d 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards ff234d522a 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards 67615d9992 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards f14e51f14d 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards 843c094ac6 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards 0dd54bf192 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards 7b43e538d6 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards d6294d39f4 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards 2553d4809d 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards 22472ac3db 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards 0fc99e2cfc 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards febeb85e51 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards 1b5755c399 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards b7d7b03e98 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards 7f60fac6a0 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards 3ed907a7ce 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards a741160cf4 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 12cef98576 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards c99bc79f43 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards 70a1201a6e 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards 836e240fc7 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards 5dd5565484 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards ba6efeaf53 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards 9716eaeb82 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards f561c26371 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards 910b0e2322 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] discards 5a8914dec3 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] discards affb635e33 149: onsuccess: #684: 1: Success after linux: 10 commits discards a84de630b6 148: onsuccess: #683: 1: Success after glibc: 9 commits discards f33cac6fe6 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 68d92c2fb9 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 0f760cf571 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards eaf41e6a3f 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards ee01532393 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards 6c07e41d1e 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 6f9ba66b4a 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new 71c15d8390 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new 7e97d0b2e7 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 92034a829a 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new 6a7f3bfc44 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new 5bca80fe46 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new e654306dbf 146: onsuccess: #680: 1: Success after binutils: 20 commits new 8ca6e0daac 147: onsuccess: #681: 1: Success after gcc: 6 commits new 3c9daae322 148: onsuccess: #683: 1: Success after glibc: 9 commits new e79e50513a 149: onsuccess: #684: 1: Success after linux: 10 commits new fdbad4583e 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] new 9e31d35cd3 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new 2236e68614 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new 80b8b05366 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new b1b0fdebbf 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new cd0d91be21 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new cb2754e6f2 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new f5a5b6c687 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new 2541c22a19 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new dffe266a28 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new 0545ec9598 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new 3bbf72ddd4 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new ed4e1ac612 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new 05c46868d3 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new db70a7338f 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new c101679530 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new c47ad58eb0 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new 76d5f49ca8 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new 88da549218 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new e82078cfb3 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new a2f57d0bd8 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new ca8d211119 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new f2c04cebfb 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new e076c96dc6 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new ddd6ba4b6a 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new cb500dfbed 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new 15f4391a00 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new 4aabf80dc9 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new a980f39d54 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new 1b5887203d 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new a3156b95ec 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new e0b467fc92 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new e147df09a5 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new 184df87015 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new 0acba170ff 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new c4e04f5985 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new c78f7b85c9 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new 4ff3fe459e 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new e1324626df 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new 99ac464b80 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new c33b34d84f 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new a30ec8f662 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 3f0e8eea27 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new df46751b7e 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 551f3b415d 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new adc91f840b 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 3cc466d562 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 872010bb8e 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new bcf3f86144 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new f6b41a640c 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 48d886b77d 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 19beab284b 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new bb983ff0c4 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 8380eaa068 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 45840b2ac4 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new b562ac9548 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new b3257a725b 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 8b08f31029 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 3f903b7e8d 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 1b5d0dc5bf 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new fec9e9b7e6 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new bdc433f018 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new fc3bdfe99a 212: force: #24: 1: Success after binutils: 2 commits new b449fd9c91 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new bea8122269 214: onsuccess: #26: 1: Success after binutils: 12 commits new 6544b7e559 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 28995428ba 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 525b817d78 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 6677c70e3f 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new b1d49f5996 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new e736e2f586 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 6a0d0d7f38 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 6773a8a1ad 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new cfa58e070a 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new c186f8993a 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new ba3f858508 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 011dd94e5c 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 4c44aa4541 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 16104c3187 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 826360e817 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 0e05833fa6 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new fe5c03c695 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 3391acd3dd 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new fba763a231 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 2b9823c9d7 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 382d27e16a 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 146300a769 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new a0d51f7b2b 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 1319e4e7d9 238: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d2d0bc7057 239: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new c1a366554c 240: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 83120ed34e 241: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 96c610376f 242: force: #69: 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 (f1c5df514d) \ 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 2200 -> 2216 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 36524 -> 35896 bytes 04-build_abe-gcc/console.log.xz | Bin 205352 -> 204448 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8912 -> 8912 bytes 07-build_abe-glibc/console.log.xz | Bin 240764 -> 240988 bytes 08-build_abe-gdb/console.log.xz | Bin 34848 -> 34856 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3844 bytes 10-build_abe-check_binutils/console.log.xz | Bin 3004 -> 2996 bytes 11-check_regression/console.log.xz | Bin 1628 -> 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/gdb_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 8 ++-- mail/results.regressions | 8 ++-- manifest.sh | 12 ++--- results | 8 ++-- sumfiles/binutils.log.xz | Bin 62644 -> 62652 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150772 -> 150716 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 122616 -> 122612 bytes sumfiles/ld.sum | 2 +- 27 files changed, 69 insertions(+), 69 deletions(-)