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-arm in repository toolchain/ci/base-artifacts.

discards 748b549bc1 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 0b3b98b1ec 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 1e00cacfc6 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 055be34693 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 991199c6f7 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 9e4ba7833a 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 8110d34841 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards e9d1643397 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 4942efc75d 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards c009f8003f 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 55c53cd90c 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 4284332e0b 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 21edf9030e 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 482a9e869c 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 7d04646c20 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 5ac19fc9f3 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 36aa38dd5d 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards a473af39ce 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 974d19d573 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 13f37d0592 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards d56182870d 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 0332ae7094 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards db62b28991 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 193850eacd 215: onsuccess: #26: 1: Success after binutils: 10 commits discards 8c25652671 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards ef07f3c165 213: force: #24: 1: Success after binutils: 2 commits discards 9c945b58cb 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards b1f27e94d5 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 5c076bf296 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 019c9e2f64 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards c7c90c51fd 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 7616401744 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards e8a53d7986 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards c0a564c067 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 607cf5ac63 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 3967a25d8e 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 06a5276d44 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 00bded73ad 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 499e3eeb5e 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards e9b867c313 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards feb50396a3 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 748dc40674 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards f694e0387d 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 96afbb35da 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards eadeae2564 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 7a4f74207d 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 489eef21cc 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards 2ef3243490 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] discards 9bcc6dd4ea 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 4d602fcbb2 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] discards 59e0b50600 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 21b11ed249 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] discards dc000e11ab 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 6006e6fee5 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards eb7095272a 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] discards 5fc038b461 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] discards 544c330a25 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards 467a696259 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 113020915d 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards ffa4263853 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards adb2bb54ab 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards 80f7e0d4e5 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 3cb968a2ab 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 46c8519b10 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] discards 75467480e7 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 7811974488 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 38eb6b0ed5 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 0996cfe99a 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 91d0e5bbbd 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 015c60a9d1 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] discards 2a07f23dd8 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards de0584d1db 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 0092aa5249 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 93243e4b74 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 18f50319d3 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 2953f1b36f 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards c0000e87fb 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 093f1c3622 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards 92859c2ce7 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] discards 3d53d7e3ab 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards dfcbdec9fd 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] discards d0cc6e8aa9 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] discards 1c003f7d17 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards ef6d843dac 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 96fdd035ef 154: onsuccess: #583: 1: Success after linux: 10 commits discards 673d28520c 153: onsuccess: #582: 1: Success after glibc: 9 commits discards af05a7c000 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 34a46341ae 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 0b62de8522 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards e45d9bde87 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 068448ac56 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] discards 413d630c8a 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards a6fb9653f2 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits discards 22667530fb 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits discards ac3b243b0c 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits discards f98d80054f 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards da39c01ea9 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits discards d3cad728f9 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] discards 64f9b31d60 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards 5dcee39699 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards aa6f327d49 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new 757544c4c6 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new 981829f8f4 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 8f2962b28e 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 2e9d4ace30 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] new 8639d7d64a 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits new d37ded1f75 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new 83e511feb2 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits new dd2722ec40 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits new 24b7acfa1c 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits new 02f8387862 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 84ab499083 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new 74937e9fb1 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 2f703741b5 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new 8f2695c83d 151: onsuccess: #579: 1: Success after binutils: 21 commits new e68f6b9fea 152: onsuccess: #580: 1: Success after gcc: 6 commits new ccc8de581d 153: onsuccess: #582: 1: Success after glibc: 9 commits new d2138cee6d 154: onsuccess: #583: 1: Success after linux: 10 commits new b98bea1486 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 2a321f6268 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 6a6451c3ee 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] new b85cafea75 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] new 2e6114d889 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 67012868b2 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] new 6117c1bb65 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new 3bd6c02e60 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new daa4f8cae0 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new 2ceec708b9 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new d4957c03b7 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new cea4c20152 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new b2e666c903 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 61f4c0987d 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 5dc06aad33 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] new c15505db58 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new 2f97114348 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 45717d9cbc 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 5bbab5b8a1 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new a33316ae18 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 7c61cdf0e3 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] new 3206184e3d 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 63f9b7df15 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 727b7d8c43 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new b8f3e9dffd 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 3800ddd2f4 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new a8a5a42e45 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 2ad8113952 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new 383057a472 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] new dbee6542dc 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] new dfc7d85195 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new 0835d7cf93 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 0f8622c6b6 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] new f7521aa0cf 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new cc0fd88ff8 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] new e68de9dd5a 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new e4a1c6c77a 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] new 097d4989d5 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new b4923979d7 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 05f842eaa4 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new ca65324ba4 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 37b9408808 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new cd864fb1e9 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 90c12499c5 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new c6ec223a71 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 9ce83488c5 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 32dff26665 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 48236163d6 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 4b8cecbf9d 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 1a1320d7f5 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 45a3cba361 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 88cdb183e7 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 6b0984fdf6 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 01c3f3f107 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 1d724cbef4 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new ce3664cd98 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 8399a64719 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 208fe86e42 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new ae5ac66b4d 213: force: #24: 1: Success after binutils: 2 commits new 326b3a75c5 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new 9cee60d20e 215: onsuccess: #26: 1: Success after binutils: 10 commits new c488eb7c86 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 7189b850c5 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new d21c70894f 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new de1524df4b 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 16a04a1d66 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 59c6c0f085 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 48985a02c8 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new d1ad96d753 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 9380fd8c09 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 1d869e0c24 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 0287401bf4 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 5c161bfd5c 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 6c1d59c235 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 9329dc02c1 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 3c07ed1a27 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 144c806823 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 0d0b6e7f4c 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 28023b92c7 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new d07e3adf45 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 932deec48e 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new f239ba5ff0 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 82126a7437 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 60d884c3a8 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new bb94be38bf 239: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...]

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 (748b549bc1) \ 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 2068 -> 2076 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2532 bytes 03-build_abe-binutils/console.log.xz | Bin 48800 -> 49156 bytes 04-build_abe-gcc/console.log.xz | Bin 236028 -> 235196 bytes 06-build_abe-linux/console.log.xz | Bin 8908 -> 8624 bytes 07-build_abe-glibc/console.log.xz | Bin 233856 -> 232480 bytes 08-build_abe-gdb/console.log.xz | Bin 46832 -> 47404 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3808 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2172 -> 2304 bytes 11-check_regression/console.log.xz | Bin 4924 -> 2004 bytes 11-check_regression/results.compare | 4 +-- 11-check_regression/results.compare2 | 4 +-- 12-update_baseline/console.log | 40 ++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 3 +++ mail/changes-list-long.txt | 24 ----------------- mail/changes-list-short.txt | 1 - mail/check-regression-status.txt | 1 + mail/last_good.sh | 34 ------------------------ mail/short-diag.txt | 1 - manifest.sh | 40 +++++++++++++++-------------- sumfiles/binutils.log.xz | Bin 62592 -> 62300 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100600 -> 100584 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132316 -> 132332 bytes sumfiles/ld.sum | 4 +-- 32 files changed, 60 insertions(+), 114 deletions(-) create mode 100755 jenkins/notify.sh delete mode 100644 mail/changes-list-long.txt delete mode 100644 mail/changes-list-short.txt create mode 100644 mail/check-regression-status.txt delete mode 100644 mail/last_good.sh delete mode 100644 mail/short-diag.txt