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 01a90bdfe8 238: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards df423d537a 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 81a9ba9aec 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards af44b296e3 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 4290c2a278 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 105c9b291a 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards d29fa24ff9 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 236e1fab14 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards a213393dbb 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 7db112eccc 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 0a2f5ec9a4 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards f3f6b0f04a 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards c2a7658ee8 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards b6b05b460f 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 2d3a40caa5 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards d23ae55eeb 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 40ec49ecb6 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards e63ac78405 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 7d4a38a6e3 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards dccd08e1ae 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 3fca9304c0 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 64aac079a1 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 7d108f8890 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards cf83afac92 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards ccb716707c 214: onsuccess: #26: 1: Success after binutils: 12 commits discards d74f8af8df 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 69aa214247 212: force: #24: 1: Success after binutils: 2 commits discards c6ffb36079 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards e44e1f0031 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 8b191ab1d7 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 2846b8c7dd 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards cf9f3520cd 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 0581798fc8 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 920c0f2832 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 3fb31344ce 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards c43691aeb0 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 7b952122a1 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 38b3c8d9c0 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 1bc2e45792 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 8bf36a90f0 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 05bcdd6b5f 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards acdba97a20 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 7945d16315 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards b1edfa63a5 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 4dab8cde34 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards f324dd4bc0 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards bfcf25f2a2 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 8f54b138a2 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 53fb198ab9 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards 4e9fbbd593 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards 58242b6369 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards 64c4394a7a 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards 74878d05d8 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards c2081ecd33 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards 83fe7883f4 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards eeccf744ea 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards e3e8700102 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards af18931f1e 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards 2c019ebe14 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards b2794b914c 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards 6338a3caef 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards 818db47945 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards 721ce62f49 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards 917b878635 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards 3ee8fc0167 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards 4cd4b4528f 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards eb59c8c5c2 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards 291380c3ba 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards afd08caa07 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards b12219e948 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards 11a493e1de 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards 8a4a6bcbfd 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards aa514a2ac7 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards a002e81d64 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards 133ef91e53 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards f3776cac88 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards 5f8428bafa 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards 25b201dbb7 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards 5f8ab177a9 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards ecf3a365d4 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards 0f7082ca18 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards aa9548655b 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards 6dd7f77d06 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards 2adea9569a 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards b1b6b96e52 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards 6a220f59c2 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards 9d78542b4c 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards ded6d7bdb8 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] discards 89807a0918 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] discards 24c2a0f1fe 149: onsuccess: #684: 1: Success after linux: 10 commits discards a5e26a5c3b 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 3ab3f1030b 147: onsuccess: #681: 1: Success after gcc: 6 commits discards eb8581fdcd 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 66a0e93b77 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards 628ed674b3 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards 4110bdaea3 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards 2274f90981 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards dd7a61f698 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards b7689a5a8f 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards 473fa7a18c 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards 269ecb41c4 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new 862157dad7 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new 4cad5de988 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new 39f34c3e44 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new 7915902884 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new 339018ae3a 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new d9ff4092fa 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new f05a8dd3f1 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new 16e51309d6 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new dc8262a442 146: onsuccess: #680: 1: Success after binutils: 20 commits new cca5a5cf3c 147: onsuccess: #681: 1: Success after gcc: 6 commits new 72bf281c2e 148: onsuccess: #683: 1: Success after glibc: 9 commits new 30ed5c1599 149: onsuccess: #684: 1: Success after linux: 10 commits new ff2a6282d5 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] new 7afc7d1f6c 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new ec09728d1d 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new fac997567c 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new 0f8f440e6b 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new 8576e20dca 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new a0b4a04ced 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new 7dd5fd6ca5 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new 8c45a940a3 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new f4bd4cdd6d 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new df77fd212d 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new 1ec9e0c305 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new 9da8c88a3b 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new 2e8fb57560 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new 349150c193 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new eb707e5a4a 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new 757938866e 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new a4a1cc03f3 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new cdb983ad32 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new ce324cca81 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new 1e41b3dbaa 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new 63eff9d4f8 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new d23cf955f7 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new a800c39d85 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new ceb4d80780 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new 80dd6bac4b 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new 840810e613 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new b4b6689630 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new 59bb242bc3 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new bb9d948dcb 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new 5ebb3b5300 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new 6493f1c245 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new 002abd18fa 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new 02fce028f4 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new c52e8ea3be 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new e9797acc1b 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new bc0c74a5b1 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new d5e1e83f26 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new 0fda204a83 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new 9674e8652b 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new 13a4a52c8b 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new 46de3f3b7d 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 6ab6bc3d06 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 037407000e 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new ba48c836ea 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 0026b89e08 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 689fa18633 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 7d958aa674 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new d80dfcd62f 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 795de34adf 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 6dd8b8cfbb 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 1615c8b744 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new f1ff805494 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 72f57e9864 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 1dc1841e36 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new ab48b14e03 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 3b1ac49cb4 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 40f1f4fe0d 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new d003382895 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new c54ffa1427 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 8770d43e95 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 5455eda74d 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 708c2ab349 212: force: #24: 1: Success after binutils: 2 commits new 7336111276 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new a6d3aacb14 214: onsuccess: #26: 1: Success after binutils: 12 commits new 9ce3f79fcd 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 1f172b9107 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new b91228ff44 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 7825ee3f86 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 370bbcc9e2 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new d1072bfbb6 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 74eb509564 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new f2e8652102 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new ccd9297ae7 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 444c215f50 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 989871a908 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new c11372ae1b 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 51c5616de6 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 9112f59c85 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 2632060e5c 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new bc54d00084 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 53b99e8b36 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new a58208f3b2 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new efac6678d1 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 880bba8370 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 7eeaa22eb4 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 198abf17eb 236: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 1728609b35 237: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new c8fabdfa31 238: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 771cdce398 239: force: #59: 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 (01a90bdfe8) \ 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 2048 -> 1972 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 35076 -> 35196 bytes 04-build_abe-gcc/console.log.xz | Bin 203764 -> 204320 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8788 -> 8892 bytes 07-build_abe-glibc/console.log.xz | Bin 240980 -> 241360 bytes 08-build_abe-gdb/console.log.xz | Bin 34656 -> 34656 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3820 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2156 -> 2304 bytes 11-check_regression/console.log.xz | Bin 1320 -> 1600 bytes 11-check_regression/results.compare | 15 +++------- 11-check_regression/results.compare2 | 45 +---------------------------- 11-check_regression/results.regressions | 4 +++ 11-check_regression/trigger-bisect | 2 ++ 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 41 +++++++++++++------------- git/binutils_rev | 2 +- jenkins/notify.sh | 2 +- mail/check-regression-status.txt | 2 +- mail/results.compare | 15 +++------- mail/results.regressions | 4 +++ manifest.sh | 26 +++++++---------- results | 4 +++ sumfiles/binutils.log.xz | Bin 62676 -> 62620 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150684 -> 150676 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122584 -> 122616 bytes sumfiles/ld.sum | 2 +- 30 files changed, 62 insertions(+), 108 deletions(-) create mode 100644 11-check_regression/results.regressions create mode 100644 11-check_regression/trigger-bisect create mode 100644 11-check_regression/trigger-notify create mode 100644 mail/results.regressions