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 3f0efce6953 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards d88236c1a57 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards 7c324a80c6a 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 3b7070368ea 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 984689f21ee 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 064b34959cb 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 85542896ff8 215: onsuccess: #26: 1: Success after binutils: 10 commits discards 066c5518f80 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards 1f72675b88b 213: force: #24: 1: Success after binutils: 2 commits discards 218c8906616 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 8faee05fc70 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards df2128e0734 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards f9e0b2719ac 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 83781eb7255 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards dc999f6f056 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 3aee4e68311 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards c8d576e2078 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards d2857e6d1ff 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards bc4c25e4213 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards de24fe0a9ab 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards bd7a0fda2d4 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 7c2fe9a4ec6 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 39554b03cbf 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 0448b8c154a 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 3c8b8895ab5 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 08aa92bd191 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards e3679257b3f 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards c8bb6709cbc 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 099b303d2b0 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 5c479b408ac 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 12288fc44dd 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 84275bcfdae 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 69d5888d416 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 5ed736957e3 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 14625e2588f 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards d16a4e79c0e 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 3fad8053cc9 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards fa9ed7a7b4f 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards d4fccafbe16 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards baa96bc444a 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards e7a482b1701 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 280a29bd627 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards cd071ea5249 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 7b2553a8f08 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards a29933c45db 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards e9ba7fb0b7a 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 32d06e4a98f 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards eb38504e644 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 6aab5732854 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards e0c27b595a9 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 8179089e1df 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards bce5601b9f9 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards e522cbe0f5e 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards 313f0eec01f 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 22711016cdd 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards cd46f5a04ed 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 3588e670abe 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 729f246a305 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 8eb679b402f 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 113ef01b127 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 616ddf30697 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 68416a47271 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards fe9503472bc 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards f6eef39936f 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards 011591e0355 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards fa277de6f0a 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards 62bdf8d76f3 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards adfe01094ba 154: onsuccess: #583: 1: Success after linux: 10 commits discards 28589d6e036 153: onsuccess: #582: 1: Success after glibc: 9 commits discards af3e7b02cda 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 08267b23144 151: onsuccess: #579: 1: Success after binutils: 21 commits discards dc590b3b6b8 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards b6b639db922 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 8295e272d9e 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards ad9a92ae001 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards 069bd93cb6c 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards bd2cf2630de 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards 4075c1b2e7b 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards 7e3643a97b9 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 0edfbeb62b5 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards 745314fdf5e 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards bdc5f517d67 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 0258e3d471d 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards e504a42e8be 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 41790b12917 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 81366df8a96 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards 5e97c50a321 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 658d8f49d65 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards a7917cad45c 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 0b44441e607 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards f64901808f0 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards 819f7e12b92 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards 78c49ffd879 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards 22a0956baa2 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards a9c22ac930e 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 7e01190900e 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 6393729b6a1 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 6b992534037 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards df8dbf13f52 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 8b9a4cb8591 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards c6ca0995576 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 7e97a43a511 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new fee64090761 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 72a9788faa5 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new 4c81558ab81 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 2ad302b56e2 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 8e42dadbfae 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 71475966f94 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new 0e5e5ed22a7 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 3b09d9668c4 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new 339d899f51b 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new f4e35278848 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new d836dfbd113 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new b25e96be598 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new c848c94a621 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new ec64951a99c 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new b09d9c841b6 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new 5d651f6817c 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new a5025355670 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new c17a1a2fa69 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 3529959db1b 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new c9ff0fb4f8a 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 1155aa9d555 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new 1a5e24621da 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new c39f4b3efbd 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new a2a8c5ca30e 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new 5cdc50b9159 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new 2d81dc4e90f 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new ed367d697dd 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 5d75e5a369e 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 9d7cf3dbcf5 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 30dfabda209 151: onsuccess: #579: 1: Success after binutils: 21 commits new 77eec787681 152: onsuccess: #580: 1: Success after gcc: 6 commits new 1dd21f97b58 153: onsuccess: #582: 1: Success after glibc: 9 commits new 80393dbad5f 154: onsuccess: #583: 1: Success after linux: 10 commits new 9708880603e 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new 63053ad6467 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new a37c6a4b517 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new f7f0ae60846 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 435dd5bb4db 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 09bfcdd57d9 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 4e92d8663e0 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 6521e172dc4 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 59aed8c4eda 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 1acb79c926f 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new d7d785cd3fc 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new c102c6ba9c6 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 4340f0967f1 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 42b847f0b53 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 28ed8528d59 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new dc953d0ad90 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new f95333f00e6 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 904ffac2406 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new a2423dbcdae 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 79d773e140d 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new aa1de8d372e 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new 9fc9507143c 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 2113090bced 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 65745f2a93b 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 3810245df9d 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new bb81cce30db 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 23bf08464a7 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new e55033fdd7a 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 5c2fd9d0f13 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new 9a1b71ebd4e 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new 26260d29267 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 2440c9f8dd0 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 1330428cf73 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 239457b96ce 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new e94a1172c75 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 88eed3f7712 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 93bb28ab77c 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 40b8a4f6295 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new c9e59029167 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new ed0824b3714 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 3773945b4bf 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new ce14ce09c21 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new f8aa72d09e3 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new cbe89cb88f0 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 60a0182967a 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 691243284b8 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new b6b447c2a0f 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 9b930d3db0c 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new df895c58edf 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 3db8a712e9a 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 9783ea9dce1 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new f2b352d615a 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new b7b128b0555 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new c5b546f311a 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 0712680f46f 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 091f2f99d40 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 759ec01ad7b 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new ab04ca8a516 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new dfa9dd72614 213: force: #24: 1: Success after binutils: 2 commits new 0b5372159a5 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 1d9d11cf787 215: onsuccess: #26: 1: Success after binutils: 10 commits new cabc2a86e3d 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 08dd9c0f12a 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 9b29085c40a 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new d41676000af 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new e6adc707ddb 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new 1f08d4cbb3b 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new 08f60e6c604 222: onsuccess: #34: 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 (3f0efce6953) \ 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 2216 -> 2068 bytes 02-prepare_abe/console.log.xz | Bin 2560 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 48384 -> 49012 bytes 04-build_abe-gcc/console.log.xz | Bin 235712 -> 235364 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8376 -> 8424 bytes 07-build_abe-glibc/console.log.xz | Bin 234688 -> 232916 bytes 08-build_abe-gdb/console.log.xz | Bin 47368 -> 47276 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3764 -> 3768 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2108 -> 2108 bytes 11-check_regression/console.log.xz | Bin 4820 -> 4816 bytes 11-check_regression/results.compare | 8 ++-- 11-check_regression/results.compare2 | 6 +-- 12-update_baseline/console.log | 66 ++++++++++++++--------------- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++-------- sumfiles/binutils.log.xz | Bin 62296 -> 62388 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100604 -> 100612 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 132244 -> 132236 bytes sumfiles/ld.sum | 4 +- 29 files changed, 70 insertions(+), 70 deletions(-)