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 bb94be38bf 239: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 60d884c3a8 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 82126a7437 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards f239ba5ff0 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 932deec48e 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards d07e3adf45 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 28023b92c7 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 0d0b6e7f4c 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 144c806823 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 3c07ed1a27 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 9329dc02c1 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 6c1d59c235 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 5c161bfd5c 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 0287401bf4 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 1d869e0c24 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 9380fd8c09 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards d1ad96d753 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 48985a02c8 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 59c6c0f085 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 16a04a1d66 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards de1524df4b 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards d21c70894f 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 7189b850c5 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards c488eb7c86 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 9cee60d20e 215: onsuccess: #26: 1: Success after binutils: 10 commits discards 326b3a75c5 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards ae5ac66b4d 213: force: #24: 1: Success after binutils: 2 commits discards 208fe86e42 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 8399a64719 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards ce3664cd98 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 1d724cbef4 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 01c3f3f107 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 6b0984fdf6 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 88cdb183e7 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 45a3cba361 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 1a1320d7f5 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 4b8cecbf9d 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 48236163d6 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 32dff26665 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 9ce83488c5 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards c6ec223a71 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 90c12499c5 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards cd864fb1e9 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 37b9408808 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards ca65324ba4 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 05f842eaa4 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards b4923979d7 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 097d4989d5 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards e4a1c6c77a 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] discards e68de9dd5a 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards cc0fd88ff8 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] discards f7521aa0cf 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 0f8622c6b6 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] discards 0835d7cf93 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards dfc7d85195 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards dbee6542dc 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] discards 383057a472 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] discards 2ad8113952 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards a8a5a42e45 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 3800ddd2f4 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards b8f3e9dffd 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 727b7d8c43 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards 63f9b7df15 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 3206184e3d 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 7c61cdf0e3 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] discards a33316ae18 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 5bbab5b8a1 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 45717d9cbc 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 2f97114348 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards c15505db58 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 5dc06aad33 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] discards 61f4c0987d 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards b2e666c903 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards cea4c20152 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards d4957c03b7 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 2ceec708b9 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards daa4f8cae0 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards 3bd6c02e60 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 6117c1bb65 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards 67012868b2 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] discards 2e6114d889 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards b85cafea75 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] discards 6a6451c3ee 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] discards 2a321f6268 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards b98bea1486 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards d2138cee6d 154: onsuccess: #583: 1: Success after linux: 10 commits discards ccc8de581d 153: onsuccess: #582: 1: Success after glibc: 9 commits discards e68f6b9fea 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 8f2695c83d 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 2f703741b5 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards 74937e9fb1 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 84ab499083 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] discards 02f8387862 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 24b7acfa1c 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits discards dd2722ec40 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits discards 83e511feb2 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits discards d37ded1f75 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 8639d7d64a 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits discards 2e9d4ace30 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] discards 8f2962b28e 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards 981829f8f4 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 224ec98314 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 65ea3b6a57 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 2a5825d7cd 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] new 8ebf7a0849 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits new 8d5cfb94fe 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new 4500a46371 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits new 25e16346e9 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits new 0a795ccae9 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits new cd8109c734 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 5cd296cbef 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new 507d808f82 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new bc09e9b646 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new 10912f3f2f 151: onsuccess: #579: 1: Success after binutils: 21 commits new 0e15d1b210 152: onsuccess: #580: 1: Success after gcc: 6 commits new 9e79515355 153: onsuccess: #582: 1: Success after glibc: 9 commits new 9c959f4f63 154: onsuccess: #583: 1: Success after linux: 10 commits new 55d37f5700 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new dae564e509 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 7cf5dcffa7 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] new 56a60a2f85 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] new a758d65e0f 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new f26d48c6b9 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] new 7422c53162 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new 134b2b8444 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 4dd09eff08 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new e4f3e4b045 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 015a843794 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 9d19df52fd 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new d5b6a4a503 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 707eb64f85 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 6fc3cf0bf6 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] new e9393eb991 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new 2de10cdac2 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 61550da27e 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new f9b1d1ed4b 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new f8ce44b3c0 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 511d687694 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] new ced52c59b5 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new bd29cc8a58 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 10caa398c3 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new 6798ebd950 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 5c69074d3e 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 0a0da23a3b 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 1205ddc8cc 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new c14b5e55cc 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] new c96489bff2 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] new 9960552ec0 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new a4340cf67c 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 72c7c78b44 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] new 27b03afd6b 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 501c9ccb06 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] new 9cb12d6527 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new b5bcd97720 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] new 74a21b9ef0 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new 9db2d1e504 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new b752d7a19a 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 78f7a6f34e 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new a976331a9d 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new e7e4c107a2 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new f9f1447d2b 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 48d583cfa3 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 7135768a9b 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 97968509b2 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new f86f9f30df 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 9de25bfde2 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 5bd35ce42b 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new ed0e39ec61 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 23db40b4ea 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 5d87045586 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new ed5179337f 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new a294e1b659 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 88fe4a673d 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 61c74c675e 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 049a81286c 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 0e8d7bc4d3 213: force: #24: 1: Success after binutils: 2 commits new fa64094eeb 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new 680e1057b9 215: onsuccess: #26: 1: Success after binutils: 10 commits new aef896e716 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 20c03e74a0 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 220fa364af 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new d2457701c5 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 25e0a369f0 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 9a98673f70 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new e7b789339c 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 6e13d78574 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 84c8c16fbd 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new ae97731e37 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 0e5e06fec3 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 8a2f328e2b 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 932ac7c82d 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 83f1bd33bc 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new a0895c34e9 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 3868c44d57 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new d615450588 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 66bd22b4b2 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 67939c8edf 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 0adf260977 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 52ea12b0f6 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 116c09eda2 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new b6cd543e7a 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new ddb599ed6c 239: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new bf9b9fa0ed 240: onsuccess: #54: 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 (bb94be38bf) \ 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 2076 -> 2052 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2532 bytes 03-build_abe-binutils/console.log.xz | Bin 49156 -> 49328 bytes 04-build_abe-gcc/console.log.xz | Bin 235196 -> 235328 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8624 -> 8616 bytes 07-build_abe-glibc/console.log.xz | Bin 232480 -> 232940 bytes 08-build_abe-gdb/console.log.xz | Bin 47404 -> 47748 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3816 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2304 -> 2592 bytes 11-check_regression/console.log.xz | Bin 2004 -> 2000 bytes 11-check_regression/results.compare | 8 +++--- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 42 ++++++++++++++--------------- 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 | 2 +- manifest.sh | 38 +++++++++++++------------- sumfiles/binutils.log.xz | Bin 62300 -> 62196 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100584 -> 100580 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132332 -> 132284 bytes sumfiles/ld.sum | 4 +-- 28 files changed, 59 insertions(+), 59 deletions(-)