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 ebd1602fe06 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards ac340991e1d 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards d270126f54c 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 267fe5fe8cd 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards cdf88f67214 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 770b869c244 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards ad77c27186c 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 757e1d5b171 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 6449871ed8c 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 1fe13e37b7f 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 7e64e6e8743 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards c4453892f6c 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 0b0a4a9abc7 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 5e1dc8682e7 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 63f1b4aa91a 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 86f1c8c3a29 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards dec1a7f42a1 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 462f44a58f0 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards a0d5d70aff9 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 32074f91589 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 81ffa745870 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards eb793768e6f 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards 0f9f65f1a39 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 3d081abb622 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 0c46ad9486b 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards e014ea8d3ee 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards dfdf23f6aa4 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 973492617ae 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 93417e1e035 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards be4bbcf0627 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards 4be5201baad 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 66d1e4eff6c 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 52136599600 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 81f41588357 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 497c7a15c0f 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 4d29c7ce72e 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards e02d0927984 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards d0c63313b84 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards fe1db6d11d3 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 7ffb2ab9f78 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 0c99e6e746d 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 067f66264b8 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards efd3614a1a6 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 121150f00b3 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards de3766f0cae 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 3896bdc2914 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards 971928f3092 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards 36bd23ea70d 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 9021a826b87 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards 81ee1e67370 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards bd600ba4436 154: onsuccess: #583: 1: Success after linux: 10 commits discards 713179c3b72 153: onsuccess: #582: 1: Success after glibc: 9 commits discards d0b9cbe4002 152: onsuccess: #580: 1: Success after gcc: 6 commits discards d91595c5970 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 8f4bc7fe16f 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 38cf93314e9 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 249905898fb 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards b0f4a00a216 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards 0acd16395ac 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards 175d80f4f85 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards ddbfc6a6a84 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards eaccba1d23a 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards d7cffd1650a 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards f4d41bfd927 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards d22c0af405e 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 07e94d84345 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 5801bb8fbc0 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 374059a6caf 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 51d432251d3 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards b605eb0238b 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 0d13a2279a1 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 0df311a85ad 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 9d64456601a 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards 72b40dd0b6e 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards c609eaad989 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards f37787d3d6c 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards fc3949e32f5 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards a55137694b4 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 4f837bd457e 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 76764282003 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 6008ecf350a 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards 2ed9f33867a 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 2ac94dbcb82 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards fb531754429 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards f81b5572e21 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards e83726e036e 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 40a4824fddb 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards f865f8574a4 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards 7ea3e0b9b28 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards 0b93e705507 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards ad994ff43ea 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards eb4f626b980 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards 82a1d2ced9f 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards 9caefdb5b8f 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] discards 61f02fa383c 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] discards 53616ab2831 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] discards e99adfd220c 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] discards aefdffbe504 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] discards d11e9094e00 106: onsuccess: #532: 1: Success after binutils/gcc/linux/g [...] discards 75a1d106c2a 105: onsuccess: #531: 1: Success after binutils/gcc/linux/g [...] discards 2a43b7b508e 104: onsuccess: #530: 1: Success after gcc: 7 commits new 5520367c077 104: onsuccess: #530: 1: Success after gcc: 7 commits new a42644c04c1 105: onsuccess: #531: 1: Success after binutils/gcc/linux/g [...] new d4915905f4f 106: onsuccess: #532: 1: Success after binutils/gcc/linux/g [...] new 94cbcf91eba 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] new ec7f0a2bc47 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] new 930b4de4734 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] new 90b7da7343c 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] new 66cac8a8f9d 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] new b1c64bcd59c 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new 83533a8d0a4 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new 195582f7bae 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new d720a6fb36d 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new 53fa6284a90 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new b10c3f91797 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 7d65bce7600 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 7404cb45a73 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 154c3c50180 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new c3b360f169e 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 6e6591a1532 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new a87673a15b7 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new cf8bca26a1b 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 6bea3256b9b 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new ab02b668af1 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new adecad14266 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new 20cea35f6e9 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 10061d68454 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new 17f7fd549c0 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new ce5e5fcf52e 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new 538e6f989f6 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new 99db46537a3 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new f8ef35a1e8f 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 00a45bf2185 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 6aee9cf7213 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new f34a4484826 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new f5f3906554a 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 38e7bb65c95 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new f2ab6a7e360 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 490e0cd87b3 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 6125db952a2 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new 24f16ad4b2d 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new a8717ac8c7f 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new b21babf4e50 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new d5d8364be35 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new e59444d394f 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new 87c1e31151f 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 2b9b18fcc8d 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 02e599c0c7c 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new f5587d3d680 151: onsuccess: #579: 1: Success after binutils: 21 commits new e9c7b4b8868 152: onsuccess: #580: 1: Success after gcc: 6 commits new 34137d5bf30 153: onsuccess: #582: 1: Success after glibc: 9 commits new 6ce31608e7a 154: onsuccess: #583: 1: Success after linux: 10 commits new d1c32b6d0f4 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new 15bda6c1e56 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new 8079171de5b 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new de57c70f219 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 8ebbb239f0b 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 1771cd75277 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new ead9512431e 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 96768b35f91 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 30f675affcb 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 01e40038aa1 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new bbbbb1cf57b 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 89c0ef43746 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 2ec67b97157 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 1b8893c8c97 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new d229d037c1e 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new b1fefcde5ce 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new b96461162b8 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 23985f13b86 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 18025caea88 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new df53142765a 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 4a8ba7025a8 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new 338f4728fe2 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 3c2ac67109e 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new f44683bf0a2 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 7c761c1d931 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new a9c5ea2e50b 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 55c5f1d9ddc 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 9eb9bc6c5e0 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 36cbc71e51c 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new 2c62a170e3f 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new cd0dbe4fc25 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 411f5fec2d9 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 035c597a208 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 05629d3a6ca 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new e42fdc2f2ad 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new fd4525b3d39 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new af04b302808 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 11ff1455224 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 04ddc021d8f 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 53b3bbf70e2 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 8a2a9773f14 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 9bc3b18d392 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 27a5d93a408 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 810a4da60c0 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 2badad06c5c 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 1f335a063a9 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 89a19e4fece 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new fa61a935cc7 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 2433219c74f 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new bacf11875cc 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 0dca3152a74 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...]
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 (ebd1602fe06) \ 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 1744 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 52956 -> 52460 bytes 04-build_abe-gcc/console.log.xz | Bin 236484 -> 236352 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9616 -> 8536 bytes 07-build_abe-glibc/console.log.xz | Bin 236652 -> 235516 bytes 08-build_abe-gdb/console.log.xz | Bin 51432 -> 51048 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3748 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2388 -> 2036 bytes 11-check_regression/console.log.xz | Bin 5860 -> 6508 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 35 ++- 12-update_baseline/console.log | 40 ++-- 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/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +-- sumfiles/binutils.log.xz | Bin 62888 -> 62736 bytes sumfiles/binutils.sum | 62 ++--- sumfiles/gas.log.xz | Bin 100608 -> 100632 bytes sumfiles/gas.sum | 274 +++++++++++----------- sumfiles/ld.log.xz | Bin 132092 -> 133516 bytes sumfiles/ld.sum | 362 +++++++++++++++-------------- 30 files changed, 439 insertions(+), 398 deletions(-)