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 ada0739fa87 215: onsuccess: #26: 1: Success after binutils: 10 commits discards 107675619f7 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards 102cd60dc5c 213: force: #24: 1: Success after binutils: 2 commits discards 69c01450d84 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards b8462ed2579 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards d61ab31e85f 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards e1e0b01587a 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 7ae74c59eee 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 37cc33591e8 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 545578df10e 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards b283c83f75d 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards e66c4826668 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 528fc877fd7 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 9c9b7800dcd 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards ed1ebe6a7fa 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 6bb2022d469 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards a183514316d 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards c6a5d4ad501 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards c4f785dec81 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards a3615c56f5d 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 73e5cd1f597 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 294629f7ed0 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 78d6f11131d 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 0f23256a651 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 7426109c658 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards f65075f8223 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 4a700141c83 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 0079c36e9de 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards e64a6612659 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 31476480638 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 83f40fd5d56 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 20876accdcb 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards 6cd1e316041 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards 6d05f31d4f7 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards d0c3c842179 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 8fd78f1ce20 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards b416c9d6485 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards d0d615866a4 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 25f000d1296 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 4e9e2279e2c 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 634e12ea426 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards 351a0808805 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 3d5b48a2be1 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards b3e4f747dea 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 68b31d131db 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards e1ced45e800 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 917ac0027e0 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards 1de5b175f8f 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards b96775bda8b 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 6aa31190835 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 6903e8637b0 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards ccb14ec937b 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards afd793b198d 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 2da0fc1bc95 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 247dcd804ac 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 46a35d241ef 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards cc709a6ec16 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards 3c421570302 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards 1d3f145305c 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards a5915d53343 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards 137cfc14ca7 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards 5b72e15bb6c 154: onsuccess: #583: 1: Success after linux: 10 commits discards 3df84144984 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 5a96e00948b 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 5f75e912d1d 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 851c838b42d 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 7e038ecd2db 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards f02845ca41d 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards aca15795230 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards 8714612ccd6 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards df6d931941d 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards d84407029d2 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards e8e879272a6 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 56471ee1688 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards 2191bdf144e 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards 0b91e7c02d4 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 0ba57ba8788 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 491663f67ce 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards b915d0c2c41 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 58274a2596a 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards 7fc51ec040c 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards a02dc39def2 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards e6b9ccf34e6 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 0972d8f5e3a 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards 74fb4c7653a 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards d8d5ca9fc57 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards 7bfa42f7bcf 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards 91b6d23e16e 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 5e09d813d6b 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 0fc52fc9255 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 4f2fe64acd2 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards aca9b78895e 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards f74b520db6d 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 04cde5c1ec2 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards f8146583d82 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 03d76f3dfd9 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 7abc67d593b 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 83c9f9bc2dd 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 22ec2f9f77a 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards b69d337474b 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards f0b27a61235 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new d94f89bede1 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new c2bfbfbd2e6 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 037bb336faf 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 86a401908c9 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 5b14621efe0 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new e61a4940172 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new df9fd1b2079 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 351057396af 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 6034632f3ca 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new fd9ac1fc7b4 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 42872226fda 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new b6636aedcab 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new a1eb0a76840 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new df34782edaf 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 80206000f1e 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new 8f099a0e785 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new 060b3850a48 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new d100b586268 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new 3e2bf7d0883 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 82d87620918 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new f0314f19ef0 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 5d32dfcea75 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new f729c40a1c9 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new e781887fdab 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new ee2f31b2799 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new e186da0cad7 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 267c0f57dea 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new a85dc986b12 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new d17ae276870 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new d5c76478793 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new 0a84ffc39f0 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new 4bcc44d024a 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new 57914399350 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new c7f77634657 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 4815d803507 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new d2d21954643 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 35f855fbf6a 151: onsuccess: #579: 1: Success after binutils: 21 commits new b2b148027e3 152: onsuccess: #580: 1: Success after gcc: 6 commits new 44517e9e168 153: onsuccess: #582: 1: Success after glibc: 9 commits new ce4cfe5a7ba 154: onsuccess: #583: 1: Success after linux: 10 commits new 0717f975a2f 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new 16ac071b552 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new f00d0c4d365 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new 3c67df923c8 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 7b421739a80 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new ee5d9981226 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 5a297b18034 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new c3266dc701f 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 0a48e62847d 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 759c96fcc54 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new cee8b0c29ed 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 25cf77eb386 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new df03567dbc8 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new abf304c5f87 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new a2ee415275e 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new 407676cf05c 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new 9b65061a69d 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new f7565df0f32 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 3e75720c39e 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new d814bfb3bcd 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new d6708dee7ef 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new 5a722a81669 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 495d701b31b 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 67f14ba6d5f 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new bb2dd342a1f 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 261e67cc004 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 60df225594c 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new edf00aa86e4 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new ac265baffe8 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new 70b389a8368 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new 5b71c84e1c9 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 36ec155e831 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new d0ff16c2ad2 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new b8e681fc940 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 1bbc0109245 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 1bd37bc9da7 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 6470713b355 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 79a29abc2e7 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new fb06ab267bb 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 3e8edcb3ed6 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 944f5b06d84 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 0996584e677 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 09403c86972 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new d1b86c801ad 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 95c6fa74396 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new e8003463b54 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new ed20fa9de24 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 2beebdbdc5b 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new a693e59cba9 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new ea89d52ba1c 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new c079d1d8cd3 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new f029ffcc635 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 2f60c64fdc3 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new c940f9526d0 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new a8467b7039e 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new ac60e5490e8 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new d382b228ee7 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new fead459da38 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new ab54db94064 213: force: #24: 1: Success after binutils: 2 commits new d77553c2851 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new d90bcfed047 215: onsuccess: #26: 1: Success after binutils: 10 commits new 9b6c1300521 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...]
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 (ada0739fa87) \ 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 2008 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 3432 -> 2480 bytes 03-build_abe-binutils/console.log.xz | Bin 53440 -> 49196 bytes 04-build_abe-gcc/console.log.xz | Bin 237816 -> 234440 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8580 -> 8532 bytes 07-build_abe-glibc/console.log.xz | Bin 235916 -> 232952 bytes 08-build_abe-gdb/console.log.xz | Bin 50624 -> 47164 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3764 -> 3780 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2520 -> 2108 bytes 11-check_regression/console.log.xz | Bin 3584 -> 5020 bytes 11-check_regression/mail-body.txt | 19 -- 11-check_regression/results.compare | 25 +- 11-check_regression/results.compare2 | 23 +- 12-update_baseline/console.log | 36 +-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 21 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +-- sumfiles/binutils.log.xz | Bin 62612 -> 62380 bytes sumfiles/binutils.sum | 62 ++--- sumfiles/gas.log.xz | Bin 100572 -> 100560 bytes sumfiles/gas.sum | 274 +++++++++++----------- sumfiles/ld.log.xz | Bin 132192 -> 132136 bytes sumfiles/ld.sum | 352 ++++++++++++++--------------- 30 files changed, 424 insertions(+), 434 deletions(-)