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 3cb39bf711 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 695ea710f4 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 6574a0f848 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards f78629e090 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 9cd5761223 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards bc79624640 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards a409894937 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 59d08c73fa 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards b643123438 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 6fa177aadd 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 6fb3c71769 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 4fd281688c 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards c94228a08b 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 13b03b07f1 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 828ef28ec0 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 1dd4f1330c 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 8f485dac63 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards b7147f58b5 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards b50719f6df 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards b9a0aec767 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 273bef5357 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards abfc9dc622 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 00251fc67c 215: onsuccess: #26: 1: Success after binutils: 10 commits discards 01502faec9 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 20f88c9787 213: force: #24: 1: Success after binutils: 2 commits discards bdb34e58af 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards dd9aa451bd 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards f8cff9acdb 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 7cf846938f 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 2d1ad50a56 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 088a7bf135 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 4a9b775f48 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards f44fb85ae1 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards e7de30de7c 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards a77c72c203 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards ccc3734040 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards f90544c496 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 16b6a30c87 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 260af95bae 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards d1c3911843 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 720cbaac73 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards e0af7a9360 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 0951c34148 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 8cb2271e2c 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards a522505362 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 23ab80bdea 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards d753edc1b4 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] discards eddae5679c 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 8c1b2f0928 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] discards f41cb65286 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 27b8878a30 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] discards 3330bf4fc3 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards b28bf55278 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards 5b29b3f6c7 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] discards 0cc1e64844 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] discards 8fde05c0c0 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards e5f9526156 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards a74990fc10 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 334b48b19f 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 0afa52f88e 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards dbd987bb9d 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 240b20b828 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 3864edc3ff 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] discards 95fe9f6f70 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards dfe0e624f8 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 5219d7459f 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards c2a01ecffd 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 2463c184a6 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 186537cb30 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] discards c8c1ddc7a6 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards b6416b22e7 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 9237f06d00 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards c01bcfaa7e 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 9677bb3d59 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 8465bc3221 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards 1d930b8950 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 126061f7b3 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards 715c30e1dc 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] discards 55f7862856 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards e9c1e539be 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] discards 7ccc883d8f 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] discards 3dcbb75f8a 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 3d808384c1 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 6e4b142196 154: onsuccess: #583: 1: Success after linux: 10 commits discards 15db2cf806 153: onsuccess: #582: 1: Success after glibc: 9 commits discards e534d0e709 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 9be5de97b1 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 79a07421f2 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards 2c760bb415 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 64f198ec2d 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] discards 060a358ad0 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards b70ec1d09c 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits discards f25d00dc9b 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits discards 1bbc07f2d1 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits discards 10d67e54ec 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 702551fa91 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits discards a2baecbf44 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] discards 25c99a5f29 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards bbf53b1b4a 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards 8b4ea04b26 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 5dccc09fd2 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new 895b13dcc1 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new aa6f327d49 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new 5dcee39699 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 64f9b31d60 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new d3cad728f9 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] new da39c01ea9 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits new f98d80054f 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new ac3b243b0c 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits new 22667530fb 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits new a6fb9653f2 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits new 413d630c8a 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 068448ac56 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new e45d9bde87 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 0b62de8522 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new 34a46341ae 151: onsuccess: #579: 1: Success after binutils: 21 commits new af05a7c000 152: onsuccess: #580: 1: Success after gcc: 6 commits new 673d28520c 153: onsuccess: #582: 1: Success after glibc: 9 commits new 96fdd035ef 154: onsuccess: #583: 1: Success after linux: 10 commits new ef6d843dac 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 1c003f7d17 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new d0cc6e8aa9 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] new dfcbdec9fd 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] new 3d53d7e3ab 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 92859c2ce7 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] new 093f1c3622 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new c0000e87fb 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 2953f1b36f 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new 18f50319d3 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 93243e4b74 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 0092aa5249 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new de0584d1db 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 2a07f23dd8 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 015c60a9d1 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] new 91d0e5bbbd 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new 0996cfe99a 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 38eb6b0ed5 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 7811974488 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 75467480e7 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 46c8519b10 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] new 3cb968a2ab 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 80f7e0d4e5 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new adb2bb54ab 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new ffa4263853 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 113020915d 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 467a696259 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 544c330a25 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new 5fc038b461 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] new eb7095272a 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] new 6006e6fee5 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new dc000e11ab 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 21b11ed249 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] new 59e0b50600 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 4d602fcbb2 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] new 9bcc6dd4ea 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 2ef3243490 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] new 489eef21cc 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new 7a4f74207d 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new eadeae2564 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 96afbb35da 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new f694e0387d 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 748dc40674 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new feb50396a3 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new e9b867c313 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 499e3eeb5e 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 00bded73ad 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 06a5276d44 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 3967a25d8e 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 607cf5ac63 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new c0a564c067 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new e8a53d7986 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 7616401744 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new c7c90c51fd 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 019c9e2f64 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 5c076bf296 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new b1f27e94d5 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 9c945b58cb 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new ef07f3c165 213: force: #24: 1: Success after binutils: 2 commits new 8c25652671 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new 193850eacd 215: onsuccess: #26: 1: Success after binutils: 10 commits new db62b28991 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 0332ae7094 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new d56182870d 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 13f37d0592 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 974d19d573 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new a473af39ce 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 36aa38dd5d 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 5ac19fc9f3 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 7d04646c20 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 482a9e869c 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 21edf9030e 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 4284332e0b 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 55c53cd90c 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new c009f8003f 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 4942efc75d 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new e9d1643397 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 8110d34841 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 9e4ba7833a 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 991199c6f7 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 055be34693 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 1e00cacfc6 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 0b3b98b1ec 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 748b549bc1 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...]
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 (3cb39bf711) \ 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 2028 -> 2068 bytes 02-prepare_abe/console.log.xz | Bin 2516 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 49044 -> 48800 bytes 04-build_abe-gcc/console.log.xz | Bin 235936 -> 236028 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8276 -> 8908 bytes 07-build_abe-glibc/console.log.xz | Bin 232472 -> 233856 bytes 08-build_abe-gdb/console.log.xz | Bin 47444 -> 46832 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3804 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2176 -> 2172 bytes 11-check_regression/console.log.xz | Bin 4348 -> 4924 bytes 11-check_regression/results.compare | 8 +++--- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 38 ++++++++++++++--------------- 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 +- mail/changes-list-long.txt | 36 +++++++++++++++++---------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 ++++++++++++------------ manifest.sh | 38 ++++++++++++++--------------- sumfiles/binutils.log.xz | Bin 62708 -> 62592 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100644 -> 100600 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132324 -> 132316 bytes sumfiles/ld.sum | 4 +-- 30 files changed, 96 insertions(+), 86 deletions(-)