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 2538f0c7d36 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gc [...] discards 421e7719053 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gl [...] discards d632a7bd880 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] discards 3c66d72c53c 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards de07cda5266 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards b5b3c24a07b 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards 9a8ab82b43c 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards b247fff007e 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 8a6be787db1 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards d9dce1eb91d 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards a03a385c9a0 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 2798b4c613e 215: onsuccess: #26: 1: Success after binutils: 10 commits discards 569818bb736 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards 3688a34d7ca 213: force: #24: 1: Success after binutils: 2 commits discards f516d04e7ad 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards f739aa75a74 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 4c4cec9a4ed 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 32ed06ba78a 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 1f58a734126 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 97f824aa83a 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards c8e4819105f 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards f5b88c99093 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards a8b7058acee 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards e57aed61761 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards c8ec17a692e 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards d66d77c05fd 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards c571d735f7d 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards ee1ab5bb23b 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 33e650dca18 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 428076924a0 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 95b5b4af44e 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 989e398d283 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 26110c4053f 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 4add3027929 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards ef84b8945fa 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards daa59ac5468 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 5f709ea35ab 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 766e68a065e 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 2deae86b46e 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 08b6ad7430b 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 17b7bbad210 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards ea3cc11d571 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 14a47a8807e 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards 35f5923a45e 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards 1247b74faca 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards f3ba745f63b 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 2bdf7618146 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 57a1af62d1a 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 12c3911106a 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 6f58901526f 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards bc9572f3bfa 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 5edc56bae6c 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards 3eb4ea56cad 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 427747329bc 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards e68de5ed224 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards d4e38d50e78 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 4aa1b797426 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards b855cf5befa 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards ee514581e4d 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 315f6aef708 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 61daee904c4 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards eddb2d54401 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 1f0ac2f5ab2 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards e43d2bdabe1 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 4d644632fc2 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 89b96590778 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 70f1bdca91c 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 8833ffc19bf 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards 254c0462082 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards c9225a7178b 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 2820ef246a8 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards 73b4055706d 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards 7fcef01175e 154: onsuccess: #583: 1: Success after linux: 10 commits discards fb36f7eb0f1 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 60366bfa4f5 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 7ba548f2550 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 8f6b2f8888b 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards e726b954af9 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 241483e2df7 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 26ba2a2374b 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards 59ffe00ab73 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards cb1269a78bb 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards 726c24b8728 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards ef90311e0cf 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 72c1e885d1a 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards 9358604a606 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards f860fd691aa 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 08b50ef3ad1 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 8908ccfd3dc 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 666bdc5e662 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards cf97f98e2c4 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards 2702a6da2e8 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 5291402ddda 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards ac5f1cabcd5 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards ef3867b9544 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards 87184e43533 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards 10bcad0156c 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards 102acfe26c2 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards d474606af54 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards a490ba122f6 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards dd8248320ad 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 984bf234c43 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new da7dcb09fc7 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new a6cd809de39 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new eccac6800fe 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new a52e80127eb 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new 42fc582eab2 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new 94e4c41b900 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new 7a8e974666f 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 283e5785d36 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 297eb4549a6 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new e63c3ce3830 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new afb07386135 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new c206d5d961d 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new d66484e1d03 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new d52ba69176f 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new e99dd6e51ce 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 9a714339851 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new f782e1f8349 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new c0c6bebd52a 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new bef805adcc0 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new aa908a28450 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new 58109c916da 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new 9be4a2a9e4f 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 93c4f3d78cd 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new dad9a9d84cc 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 009d4b2bd41 151: onsuccess: #579: 1: Success after binutils: 21 commits new 23b07d9356c 152: onsuccess: #580: 1: Success after gcc: 6 commits new d0608248681 153: onsuccess: #582: 1: Success after glibc: 9 commits new b05b88ee7f9 154: onsuccess: #583: 1: Success after linux: 10 commits new 140a5be1e05 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new 5038016f76d 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new 27ae3cc2b14 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new 9825892ce5d 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 4e8b8fc73ac 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 8d584328f32 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 2c9d68db81a 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 65f89e5d749 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 24e559a8fe8 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 5a43e3ca2c7 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new a7c3b42bc09 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new c3f4b76b30f 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new a75086fecf4 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 2dce904b9f3 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 4ad84d41854 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new 651d31d4b4a 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new bcd91dfc7cf 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new ffc68c94b0f 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 7e5e5b50f96 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 556d42d1cef 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 8c1ecf0260b 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new a615e503f62 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new ae041a3921b 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 66f37390c74 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new eca1cc56f64 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new c7b07500a81 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 210d51ac1fe 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new f351c70a97c 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new c5d25f4f927 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new 18387c44bc0 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new 6f334a5a931 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 43e024dd187 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 47e1e2a429c 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new cc6dec8c2b1 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 17505096fee 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 97d1897b270 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 0bded0f3924 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 0f0d4dd38df 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 74265a688eb 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 8ff800dacc2 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 9d3ef31d9be 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new acb61581269 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 4d1f97db365 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 4e7aa26761c 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 4269bdc218f 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new aac2fd94db2 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 01e7dc3778f 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 578d92d1e5f 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 46c2925dc6b 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 6697c4a71c3 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 429d4619f90 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new aa45b887618 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 1b2ab850776 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 5d49cb71e7d 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new c0844062d26 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new e51828ceaae 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 2550af6f968 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new bbb3a23bc17 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 23c0041447b 213: force: #24: 1: Success after binutils: 2 commits new c3f8ab97f2e 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 74d16ebdcb5 215: onsuccess: #26: 1: Success after binutils: 10 commits new d0229419bf8 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new d1fd811441e 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 1655326d9f5 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 958f95bd831 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new e1060aae86c 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new cc3bd16ae82 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new e00e56b21c9 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new f70c8604148 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new 23ebd0fcd93 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] new 77c05d0f8ff 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gl [...] new f9a3f0adf8e 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gc [...] new 89647a69797 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gc [...]

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 (2538f0c7d36) \ 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 2064 -> 2028 bytes 02-prepare_abe/console.log.xz | Bin 2516 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 49072 -> 49164 bytes 04-build_abe-gcc/console.log.xz | Bin 235964 -> 236380 bytes 06-build_abe-linux/console.log.xz | Bin 8584 -> 8376 bytes 07-build_abe-glibc/console.log.xz | Bin 232416 -> 232072 bytes 08-build_abe-gdb/console.log.xz | Bin 47720 -> 46900 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3792 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2236 -> 2140 bytes 11-check_regression/console.log.xz | Bin 5072 -> 4996 bytes 11-check_regression/results.compare2 | 4 +- 12-update_baseline/console.log | 36 +++++++++--------- 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 | 57 ++++++++++++++--------------- mail/changes-list-short.txt | 2 +- manifest.sh | 36 +++++++++--------- sumfiles/binutils.log.xz | Bin 62776 -> 62592 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100700 -> 100616 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 132252 -> 132260 bytes sumfiles/ld.sum | 4 +- 27 files changed, 77 insertions(+), 80 deletions(-)