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_build/master-arm in repository toolchain/ci/base-artifacts.
discards 72114fd1509 228: onsuccess: #35: 6: Success after binutils/gcc/linux/gl [...] discards e0c30c77dc9 227: onsuccess: #34: 6: Success after binutils/gcc/linux/gd [...] discards 0a2a4db7686 226: onsuccess: #32: 6: Success after binutils/gcc/linux/gd [...] discards 2175e739435 225: onsuccess: #31: 6: Success after binutils/gcc/linux/gl [...] discards 1a8ec2b2d02 224: onsuccess: #30: 6: Success after binutils/gcc/linux/gd [...] discards 9e2a60171be 223: onsuccess: #29: 6: Success after binutils/gcc/linux/gd [...] discards 0626edacc63 222: onsuccess: #28: 6: Success after binutils/gcc/linux/gd [...] discards 03778f802ca 221: onsuccess: #26: 6: Success after binutils/gcc/linux/gd [...] discards 852584f85ba 220: onsuccess: #25: 6: Success after binutils/gcc/linux/gd [...] discards 8db0035dd36 219: onsuccess: #24: 6: Success after binutils/gcc/linux/gl [...] discards 17f920c5af4 218: onsuccess: #23: 6: Success after binutils/gcc/linux/gd [...] discards 97454f0722b 217: onsuccess: #22: 6: Success after binutils/gcc/linux/gl [...] discards 0b13e9577cd 216: onsuccess: #21: 6: Success after binutils/gcc/linux/gd [...] discards 153ddf36f52 215: onsuccess: #20: 6: Success after binutils/gcc/linux/gl [...] discards b205f55cb58 214: onsuccess: #19: 6: Success after binutils/gcc/linux/gd [...] discards 6ef3758b824 213: onsuccess: #18: 6: Success after binutils/gcc/linux/gl [...] discards ba308a66265 212: onsuccess: #17: 6: Success after binutils/gcc/linux/gl [...] discards b6437398520 211: onsuccess: #12: 6: Success after binutils/gcc/linux/gl [...] discards 5f5570ea6e3 210: onsuccess: #11: 6: Success after binutils/gcc/linux/gd [...] discards 99823f4c851 209: onsuccess: #10: 6: Success after binutils/gcc/linux/gd [...] discards d8a80ce7cb1 208: onsuccess: #9: 6: Success after binutils/gcc/linux/gli [...] discards 566007aafae 207: onsuccess: #8: 6: Success after binutils/gcc/linux/gli [...] discards 3578063fda9 206: onsuccess: #7: 6: Success after binutils/gcc/linux/gdb [...] discards d9dc63ea19f 205: onsuccess: #6: 6: Success after binutils/gcc/linux/gli [...] discards 4394d28d0d5 204: onsuccess: #5: 6: Success after binutils/gcc/linux/gli [...] discards 571eb187755 203: onsuccess: #4: 6: Success after binutils/gcc/linux/gli [...] discards b74f0330089 202: onsuccess: #3: 6: Success after binutils/gcc/linux/gdb [...] discards 97c68c7e3f4 201: onsuccess: #2: 6: Success after binutils/gcc/linux/gli [...] discards e594f7ff58d 200: onsuccess: #1: 6: Success after binutils/gcc/linux/gli [...] discards 822797df05a 199: onsuccess: #630: 6: Success after binutils/gcc/linux/g [...] discards 4fbf0185d6f 198: onsuccess: #629: 6: Success after binutils/gcc/linux/g [...] discards 11df9c9ce55 197: onsuccess: #628: 6: Success after binutils/gcc/linux/g [...] discards f088d2deaae 196: onsuccess: #621: 6: Success after binutils/gcc/linux/g [...] discards 6367880ef09 195: onsuccess: #620: 6: Success after binutils/gcc/linux/g [...] discards ac6b8e16b22 194: onsuccess: #619: 6: Success after binutils/gcc/linux/g [...] discards 2e676e67dfe 193: onsuccess: #618: 6: Success after binutils/gcc/linux/g [...] discards c0d1e1ae228 192: onsuccess: #617: 6: Success after binutils/gcc/linux/g [...] discards ce60417fd1c 191: onsuccess: #615: 6: Success after binutils/gcc/linux/g [...] discards 418ee9f1918 190: onsuccess: #614: 6: Success after binutils/gcc/linux/g [...] discards 36f87d0d6ca 189: onsuccess: #613: 6: Success after binutils/gcc/linux/g [...] discards ae54088649b 188: onsuccess: #612: 6: Success after binutils/gcc/linux/g [...] discards 70e37d84548 187: onsuccess: #611: 6: Success after binutils/gcc/linux/g [...] discards 62d60d3f321 186: onsuccess: #610: 6: Success after binutils/gcc/linux/g [...] discards 18b9a274c57 185: onsuccess: #609: 6: Success after binutils/gcc/linux/g [...] discards 6532e323ac7 184: onsuccess: #608: 6: Success after binutils/gcc/linux/g [...] discards 571451e5043 183: onsuccess: #607: 6: Success after binutils/gcc/linux/g [...] discards 220b34dcb0d 182: onsuccess: #606: 6: Success after binutils/gcc/linux/g [...] discards 0bb22640236 181: onsuccess: #605: 6: Success after binutils/gcc/linux/g [...] discards 650d27a3ad7 180: onsuccess: #604: 6: Success after binutils/gcc/linux/g [...] discards d7ddfe79991 179: onsuccess: #603: 6: Success after binutils/gcc/linux/g [...] discards 28dbeb0664a 178: onsuccess: #602: 6: Success after binutils/gcc/linux/g [...] discards 66f66c2624f 177: onsuccess: #601: 6: Success after binutils/gcc/linux/g [...] discards 876851d8214 176: onsuccess: #600: 6: Success after binutils/gcc/linux/g [...] discards eef2e3600d6 175: onsuccess: #599: 6: Success after binutils/gcc/linux/g [...] discards 1ca60543e76 174: onsuccess: #598: 6: Success after binutils/gcc/linux/g [...] discards 784c3718d4c 173: onsuccess: #597: 6: Success after binutils/gcc/linux/g [...] discards d69c666c000 172: onsuccess: #596: 6: Success after binutils/gcc/linux/g [...] discards a074b27f590 171: onsuccess: #595: 6: Success after binutils/gcc/linux/g [...] discards db9d880b4dc 170: onsuccess: #594: 6: Success after binutils/gcc/linux/g [...] discards 4f67503ee5d 169: onsuccess: #593: 6: Success after binutils/gcc/linux/g [...] discards e2fe9395d27 168: onsuccess: #591: 6: Success after binutils/gcc/linux/g [...] discards 94f6ad250cd 167: onsuccess: #590: 6: Success after binutils/gcc/linux/g [...] discards b4eb8ea1d4e 166: onsuccess: #589: 6: Success after binutils/gcc/linux/g [...] discards 1178cb50333 165: onsuccess: #588: 6: Success after binutils/gcc/linux/g [...] discards bf6f3343bad 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/g [...] discards ef6982f9fe1 163: onsuccess: #586: 6: Success after binutils/gcc/linux/g [...] discards a3f354fe199 162: onsuccess: #579: 6: Success after gcc: 11 commits discards f3bacb778c7 161: onsuccess: #578: 6: Success after binutils: 15 commits discards ad8fda41814 160: onsuccess: #576: 6: Success after binutils/gcc/linux/g [...] discards 3c3c8b31ad0 159: onsuccess: #575: 6: Success after binutils/gcc/linux/g [...] discards 27144fd66c1 158: onsuccess: #574: 6: Success after binutils/gcc/linux/g [...] discards 5fafd008cb9 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits discards 227179d8b08 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 [...] discards 2594326997d 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 [...] discards 126d57822eb 154: onsuccess: #570: 6: Success after binutils/gcc/linux/g [...] discards ac605ec866b 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 [...] discards 44f932c8dea 152: onsuccess: #568: 6: Success after binutils/gcc/linux/g [...] discards b9b48733a2a 151: onsuccess: #567: 6: Success after binutils/gcc/linux/g [...] discards 308f336ea72 150: onsuccess: #566: 6: Success after binutils/gcc/linux/g [...] discards fc2590a1dcb 149: onsuccess: #565: 6: Success after binutils/gcc/linux/g [...] discards 0e9a5778d0b 148: onsuccess: #564: 6: Success after binutils/gcc/linux/g [...] discards 360f9144097 147: onsuccess: #563: 6: Success after binutils/gcc/linux/g [...] discards 9a9d0734e4a 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 [...] discards a2d95c0d6be 145: onsuccess: #561: 6: Success after binutils/gcc/linux/g [...] discards 515f5f8df54 144: onsuccess: #560: 6: Success after binutils/gcc/linux/g [...] discards c9a2774ad30 143: onsuccess: #559: 6: Success after binutils/gcc/linux/g [...] discards c8fffc47675 142: onsuccess: #558: 6: Success after binutils/gcc/linux/g [...] discards 59e962eb9b5 141: onsuccess: #557: 6: Success after binutils/gcc/linux/g [...] discards b1cd5db2c8c 140: onsuccess: #556: 6: Success after binutils/gcc/linux/g [...] discards bca61e34750 139: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] discards d682eeb1a93 138: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] discards 0a2ad59eaaf 137: onsuccess: #553: 6: Success after binutils/gcc/linux/g [...] discards de94dd5a3c7 136: onsuccess: #551: 6: Success after binutils/gcc/linux/g [...] discards de521a561f2 135: onsuccess: #550: 6: Success after binutils/gcc/linux/g [...] discards 84652fc3679 134: onsuccess: #544: 6: Success after binutils: 18 commits discards bf308aa75bb 133: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] discards 9e7d1a9c8d3 132: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] discards 1e6a514a8f2 131: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] discards 8fe71fd1b65 130: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] discards 752fba7bddd 129: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] discards 3136037d4f0 128: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] new e1bfe8d4334 128: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] new caf290a15bc 129: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] new f70f7f0f80b 130: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] new 7273763558c 131: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] new b9d315ac9b7 132: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] new 99a87d31f39 133: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] new 0b9bea29f02 134: onsuccess: #544: 6: Success after binutils: 18 commits new f9c387ef86b 135: onsuccess: #550: 6: Success after binutils/gcc/linux/g [...] new 0d0d26eca52 136: onsuccess: #551: 6: Success after binutils/gcc/linux/g [...] new 96a3215d367 137: onsuccess: #553: 6: Success after binutils/gcc/linux/g [...] new f40c3eafd8d 138: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] new 3926a0fce7f 139: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] new fba84961538 140: onsuccess: #556: 6: Success after binutils/gcc/linux/g [...] new d5d7598022f 141: onsuccess: #557: 6: Success after binutils/gcc/linux/g [...] new 41738499759 142: onsuccess: #558: 6: Success after binutils/gcc/linux/g [...] new 5c00e50de19 143: onsuccess: #559: 6: Success after binutils/gcc/linux/g [...] new 8c79b94814c 144: onsuccess: #560: 6: Success after binutils/gcc/linux/g [...] new 23fdd437f8b 145: onsuccess: #561: 6: Success after binutils/gcc/linux/g [...] new 4ca2ec38f8a 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 [...] new 317ce34174d 147: onsuccess: #563: 6: Success after binutils/gcc/linux/g [...] new 7b663db7c4c 148: onsuccess: #564: 6: Success after binutils/gcc/linux/g [...] new d66c0cd6d98 149: onsuccess: #565: 6: Success after binutils/gcc/linux/g [...] new 57358a0c461 150: onsuccess: #566: 6: Success after binutils/gcc/linux/g [...] new 5b43b8b7e4d 151: onsuccess: #567: 6: Success after binutils/gcc/linux/g [...] new c6a9aba8b75 152: onsuccess: #568: 6: Success after binutils/gcc/linux/g [...] new 77bc43323fa 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 [...] new ef5f64d5476 154: onsuccess: #570: 6: Success after binutils/gcc/linux/g [...] new 80f75a22006 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 [...] new 2e85a97ffd1 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 [...] new 015a9abeb2f 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits new 8529097c64f 158: onsuccess: #574: 6: Success after binutils/gcc/linux/g [...] new 46b14ce61d4 159: onsuccess: #575: 6: Success after binutils/gcc/linux/g [...] new c0606b2c4f4 160: onsuccess: #576: 6: Success after binutils/gcc/linux/g [...] new 681a371e04a 161: onsuccess: #578: 6: Success after binutils: 15 commits new 35ab740f57a 162: onsuccess: #579: 6: Success after gcc: 11 commits new 8130c96d4ab 163: onsuccess: #586: 6: Success after binutils/gcc/linux/g [...] new 7f0dc1efd16 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/g [...] new f6a8cc13e1a 165: onsuccess: #588: 6: Success after binutils/gcc/linux/g [...] new e0ed7e55365 166: onsuccess: #589: 6: Success after binutils/gcc/linux/g [...] new 6dedc31211b 167: onsuccess: #590: 6: Success after binutils/gcc/linux/g [...] new 8a5ee4328cf 168: onsuccess: #591: 6: Success after binutils/gcc/linux/g [...] new 3f3a15c07b3 169: onsuccess: #593: 6: Success after binutils/gcc/linux/g [...] new bea97cdcf5f 170: onsuccess: #594: 6: Success after binutils/gcc/linux/g [...] new f5cabb7e6c6 171: onsuccess: #595: 6: Success after binutils/gcc/linux/g [...] new 6146493a0ee 172: onsuccess: #596: 6: Success after binutils/gcc/linux/g [...] new 289c0b1945a 173: onsuccess: #597: 6: Success after binutils/gcc/linux/g [...] new 1478f679eec 174: onsuccess: #598: 6: Success after binutils/gcc/linux/g [...] new 276421415f5 175: onsuccess: #599: 6: Success after binutils/gcc/linux/g [...] new 373cf1fe70e 176: onsuccess: #600: 6: Success after binutils/gcc/linux/g [...] new 62a94e1552f 177: onsuccess: #601: 6: Success after binutils/gcc/linux/g [...] new 7cdf5f8f445 178: onsuccess: #602: 6: Success after binutils/gcc/linux/g [...] new da6e3a7f7c3 179: onsuccess: #603: 6: Success after binutils/gcc/linux/g [...] new 534f2dd7c87 180: onsuccess: #604: 6: Success after binutils/gcc/linux/g [...] new 4dd8873f291 181: onsuccess: #605: 6: Success after binutils/gcc/linux/g [...] new 189bf6db193 182: onsuccess: #606: 6: Success after binutils/gcc/linux/g [...] new d3d2b23d6af 183: onsuccess: #607: 6: Success after binutils/gcc/linux/g [...] new 7ad8dac5f98 184: onsuccess: #608: 6: Success after binutils/gcc/linux/g [...] new c517c57e3bd 185: onsuccess: #609: 6: Success after binutils/gcc/linux/g [...] new eeb3a38133d 186: onsuccess: #610: 6: Success after binutils/gcc/linux/g [...] new acce2f52981 187: onsuccess: #611: 6: Success after binutils/gcc/linux/g [...] new bb88fcff4a4 188: onsuccess: #612: 6: Success after binutils/gcc/linux/g [...] new 08e0199f8cb 189: onsuccess: #613: 6: Success after binutils/gcc/linux/g [...] new 388aafb94c7 190: onsuccess: #614: 6: Success after binutils/gcc/linux/g [...] new b5da54bd7b7 191: onsuccess: #615: 6: Success after binutils/gcc/linux/g [...] new da5b1ad4c94 192: onsuccess: #617: 6: Success after binutils/gcc/linux/g [...] new d12581a85a0 193: onsuccess: #618: 6: Success after binutils/gcc/linux/g [...] new 93d5d5a325f 194: onsuccess: #619: 6: Success after binutils/gcc/linux/g [...] new b6868a962e3 195: onsuccess: #620: 6: Success after binutils/gcc/linux/g [...] new 241e5754f84 196: onsuccess: #621: 6: Success after binutils/gcc/linux/g [...] new 93c30032fc9 197: onsuccess: #628: 6: Success after binutils/gcc/linux/g [...] new 221a9f74a58 198: onsuccess: #629: 6: Success after binutils/gcc/linux/g [...] new 068b8c81067 199: onsuccess: #630: 6: Success after binutils/gcc/linux/g [...] new c95cd80bfc7 200: onsuccess: #1: 6: Success after binutils/gcc/linux/gli [...] new ced795e03ee 201: onsuccess: #2: 6: Success after binutils/gcc/linux/gli [...] new cb2e31595a8 202: onsuccess: #3: 6: Success after binutils/gcc/linux/gdb [...] new 2109e7ef6c5 203: onsuccess: #4: 6: Success after binutils/gcc/linux/gli [...] new 181586ecc72 204: onsuccess: #5: 6: Success after binutils/gcc/linux/gli [...] new 7808f040886 205: onsuccess: #6: 6: Success after binutils/gcc/linux/gli [...] new 00d193b6e66 206: onsuccess: #7: 6: Success after binutils/gcc/linux/gdb [...] new 77640825e05 207: onsuccess: #8: 6: Success after binutils/gcc/linux/gli [...] new cd87466fbeb 208: onsuccess: #9: 6: Success after binutils/gcc/linux/gli [...] new a2df6f54287 209: onsuccess: #10: 6: Success after binutils/gcc/linux/gd [...] new d136606fa87 210: onsuccess: #11: 6: Success after binutils/gcc/linux/gd [...] new 22cc25c9fc3 211: onsuccess: #12: 6: Success after binutils/gcc/linux/gl [...] new 2190fd32c3e 212: onsuccess: #17: 6: Success after binutils/gcc/linux/gl [...] new 80409c71d39 213: onsuccess: #18: 6: Success after binutils/gcc/linux/gl [...] new 40ff3f56bcb 214: onsuccess: #19: 6: Success after binutils/gcc/linux/gd [...] new ef9a166a7f8 215: onsuccess: #20: 6: Success after binutils/gcc/linux/gl [...] new f3155dd5cd9 216: onsuccess: #21: 6: Success after binutils/gcc/linux/gd [...] new 3376a9bbf91 217: onsuccess: #22: 6: Success after binutils/gcc/linux/gl [...] new 218f94cfd9d 218: onsuccess: #23: 6: Success after binutils/gcc/linux/gd [...] new d365128426c 219: onsuccess: #24: 6: Success after binutils/gcc/linux/gl [...] new 3c1044b3359 220: onsuccess: #25: 6: Success after binutils/gcc/linux/gd [...] new 73409ed4824 221: onsuccess: #26: 6: Success after binutils/gcc/linux/gd [...] new cdf6a04c445 222: onsuccess: #28: 6: Success after binutils/gcc/linux/gd [...] new c48cdd47700 223: onsuccess: #29: 6: Success after binutils/gcc/linux/gd [...] new 70590260699 224: onsuccess: #30: 6: Success after binutils/gcc/linux/gd [...] new 9e8f32b9e44 225: onsuccess: #31: 6: Success after binutils/gcc/linux/gl [...] new 1582d1336b5 226: onsuccess: #32: 6: Success after binutils/gcc/linux/gd [...] new b0b6e621fe9 227: onsuccess: #34: 6: Success after binutils/gcc/linux/gd [...] new e5f9c6ed891 228: onsuccess: #35: 6: Success after binutils/gcc/linux/gl [...] new 5b7fa54c881 229: onsuccess: #37: 6: [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 (72114fd1509) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...]
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 2016 -> 2028 bytes 02-prepare_abe/console.log.xz | Bin 2524 -> 2540 bytes 04-build_abe-binutils/console.log.xz | Bin 49280 -> 49700 bytes 05-build_abe-gcc/console.log.xz | Bin 236344 -> 238656 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8396 -> 8788 bytes 08-build_abe-glibc/console.log.xz | Bin 232028 -> 232184 bytes 09-build_abe-gdb/console.log.xz | Bin 46756 -> 48028 bytes 10-check_regression/console.log.xz | Bin 3844 -> 4420 bytes 10-check_regression/mail-body.txt | 31 ---------------- 10-check_regression/mail-subject.txt | 1 - 11-update_baseline/console.log | 68 +++++++++++++++++------------------ 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 | 32 +++++++++++++++++ mail/changes-list-short.txt | 1 + mail/mail-body.txt | 31 ---------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 38 ++++++++++---------- 24 files changed, 93 insertions(+), 123 deletions(-) delete mode 100644 10-check_regression/mail-body.txt delete mode 100644 10-check_regression/mail-subject.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt