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 a418d5e57d6 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gl [...] discards 969343d39d7 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] discards ed7f73a8fbc 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards 4579b80f9ab 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards 377f50faaea 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards 32a6c01a1ff 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards 74f8659a90e 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards f9daa76f4a5 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 7e274c34e31 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 1b8edf47feb 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 5916421ca0b 215: onsuccess: #26: 1: Success after binutils: 10 commits discards a7c3d4bc702 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards 4cc6c2fa961 213: force: #24: 1: Success after binutils: 2 commits discards b7f32f6bae3 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 6b5ebb209c3 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 9928df3e255 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards c84d05ecba0 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 32998204a32 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 762560471fb 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 1a297e6c81c 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 48f49d12c54 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 4256cb14ceb 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards ba2ef3a1f40 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards e33bd7bf36a 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 0296183b580 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards cea762d6818 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards f3dbd8a2f01 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 0bee5c84d07 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards ab6a3c626fd 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards e26c42988dd 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 39a28929987 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 304d8d76e47 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards e0d002adbe9 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 3bb249388dd 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 28485cae472 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 0f0c12f4e1d 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards e249198e8f3 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards e0d81739b3e 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards ffb770b289d 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 5c7f361d7a4 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 1848bd322a0 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards db8d2c2b2aa 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards 81c25312f88 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards eb13f76e4bc 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards fcb6e3f75d2 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 75b8aa189c0 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 67efe43084a 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 08e63cde32a 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards e1a82094bb6 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 50fc7e4fa7d 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards ca4db11a2cf 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards b0f6f66e05c 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 13013d2176a 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 5fe592ad1d2 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 316ad7212d7 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards bb08355eb2a 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 6ab2d437780 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards 2d65d5f72f4 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 63ee5523329 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards d846fb669e6 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards df1852878ba 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards dbccb7d2d31 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 2d03c275c41 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 9171d98d587 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 6d4799bfb04 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards a72c37768c8 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards d238359ceb2 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards 6b6148c4e93 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards 8502a51ca25 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 4c84cbea1e6 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards 19725c120b4 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards c4b8e9fb473 154: onsuccess: #583: 1: Success after linux: 10 commits discards c98b221f7ae 153: onsuccess: #582: 1: Success after glibc: 9 commits discards f5d36616412 152: onsuccess: #580: 1: Success after gcc: 6 commits discards e920c1cc496 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 7db8b9bb6be 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 1868bb33056 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards d41699ed3fe 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards b1038832119 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards f440ce404e2 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards 3bd6a69fa6d 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards 5b8e467fce1 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards 47296f76f9c 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 43a86f83ad4 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards 8a53ac14075 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards b08bc811a92 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards ffb96f9a68a 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards e195d26c5e2 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 6985e658271 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 29a095e6508 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards 849012064ce 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 4d08fb001f8 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards b70487e3484 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards dc39a07aa5a 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards dfa6203caf6 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards a56d47a2820 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards cac31d6d0f0 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards bf520751515 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards db0f4b65b4f 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 4118a2fbbf0 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards f8163456920 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 6e61b0bfcd8 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new dd8248320ad 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new a490ba122f6 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new d474606af54 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 102acfe26c2 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new 10bcad0156c 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new 87184e43533 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new ef3867b9544 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new ac5f1cabcd5 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 5291402ddda 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 2702a6da2e8 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new cf97f98e2c4 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new 666bdc5e662 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 8908ccfd3dc 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 08b50ef3ad1 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new f860fd691aa 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 9358604a606 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 72c1e885d1a 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new ef90311e0cf 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new 726c24b8728 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new cb1269a78bb 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new 59ffe00ab73 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new 26ba2a2374b 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new 241483e2df7 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new e726b954af9 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 8f6b2f8888b 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 7ba548f2550 151: onsuccess: #579: 1: Success after binutils: 21 commits new 60366bfa4f5 152: onsuccess: #580: 1: Success after gcc: 6 commits new fb36f7eb0f1 153: onsuccess: #582: 1: Success after glibc: 9 commits new 7fcef01175e 154: onsuccess: #583: 1: Success after linux: 10 commits new 73b4055706d 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new 2820ef246a8 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new c9225a7178b 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new 254c0462082 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 8833ffc19bf 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 70f1bdca91c 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 89b96590778 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 4d644632fc2 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new e43d2bdabe1 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 1f0ac2f5ab2 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new eddb2d54401 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 61daee904c4 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 315f6aef708 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new ee514581e4d 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new b855cf5befa 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new 4aa1b797426 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new d4e38d50e78 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new e68de5ed224 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 427747329bc 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 3eb4ea56cad 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 5edc56bae6c 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new bc9572f3bfa 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 6f58901526f 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 12c3911106a 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 57a1af62d1a 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 2bdf7618146 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new f3ba745f63b 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 1247b74faca 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 35f5923a45e 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new 14a47a8807e 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new ea3cc11d571 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 17b7bbad210 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 08b6ad7430b 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 2deae86b46e 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 766e68a065e 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 5f709ea35ab 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new daa59ac5468 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new ef84b8945fa 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 4add3027929 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 26110c4053f 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 989e398d283 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 95b5b4af44e 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 428076924a0 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 33e650dca18 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new ee1ab5bb23b 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new c571d735f7d 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new d66d77c05fd 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new c8ec17a692e 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new e57aed61761 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new a8b7058acee 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new f5b88c99093 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new c8e4819105f 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 97f824aa83a 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 1f58a734126 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 32ed06ba78a 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 4c4cec9a4ed 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new f739aa75a74 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new f516d04e7ad 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 3688a34d7ca 213: force: #24: 1: Success after binutils: 2 commits new 569818bb736 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 2798b4c613e 215: onsuccess: #26: 1: Success after binutils: 10 commits new a03a385c9a0 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new d9dce1eb91d 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 8a6be787db1 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new b247fff007e 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 9a8ab82b43c 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new b5b3c24a07b 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new de07cda5266 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new 3c66d72c53c 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new d632a7bd880 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] new 421e7719053 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gl [...] new 2538f0c7d36 226: onsuccess: #39: 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 (a418d5e57d6) \ 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 -> 2064 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2516 bytes 03-build_abe-binutils/console.log.xz | Bin 48404 -> 49072 bytes 04-build_abe-gcc/console.log.xz | Bin 235688 -> 235964 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8204 -> 8584 bytes 07-build_abe-glibc/console.log.xz | Bin 234696 -> 232416 bytes 08-build_abe-gdb/console.log.xz | Bin 46652 -> 47720 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3764 -> 3768 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2120 -> 2236 bytes 11-check_regression/console.log.xz | Bin 4800 -> 5072 bytes 11-check_regression/mail-body.txt | 35 ------------------------ 11-check_regression/mail-subject.txt | 1 - 11-check_regression/results.compare | 8 +++--- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 42 ++++++++++++++--------------- 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 | 35 ------------------------ mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 38 +++++++++++++------------- sumfiles/binutils.log.xz | Bin 62376 -> 62776 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100648 -> 100700 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132196 -> 132252 bytes sumfiles/ld.sum | 4 +-- 34 files changed, 92 insertions(+), 130 deletions(-) delete mode 100644 11-check_regression/mail-body.txt delete mode 100644 11-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