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 b83339e1efc 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards ac6feebb5cb 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards e0d0fb82dee 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards af974603bcb 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 484a53b59db 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 711092558c7 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 3684b54a2e0 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards de0515a80c0 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 639ef25b454 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 13faf9367b3 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 2ba09f57ba7 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 5b52181cc1a 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards b62b4518d5d 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 6bf46f1b51a 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 41fcc47a135 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 67102708492 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 4f55654235b 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 6cdb045c2d3 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards f580b61b28e 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 95b5544fe45 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards c0935b453f8 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 51e66971cff 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards c4cc894de1e 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 554c69f5b75 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards beaadebf45e 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards ed4895fc79a 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards c5f7490c85a 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards a69b1b21868 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards 6fa3d2cf058 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards 54f3297ea86 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 0a7880eda4a 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 824c7d37a8e 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards e475477404f 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards e366eff3286 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards fe913889333 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards c9fb755f1b5 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards a8daac184b6 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards 423e718e4e1 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 6bb12fbf4b5 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 1923330d5e8 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 21cd2c5052b 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 260abba1ce4 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 7beb3950104 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards bdbddc0fb4a 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards b75a4865949 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards b8d91b43ea3 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 6aab03e3543 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 0a772a45109 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards f7f99a88cb7 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 36e96c80d43 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 81b1bd3f1ac 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards d0eb2a991a8 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 393ff07bfa2 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards 1d05132bc8e 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards ec752e28ccc 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 6647cffc944 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards 423178a5ef6 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards 1a06ee76d52 154: onsuccess: #583: 1: Success after linux: 10 commits discards dd5a4e2c27d 153: onsuccess: #582: 1: Success after glibc: 9 commits discards e7ac80a849d 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 841709c0024 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 302e8f7295f 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 6085f58353a 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 51953e2822e 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards e7f7a563c7e 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards 7581c1fb6c4 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards 99519f91341 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards 6ea3d580e6f 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards 83fb5fb56a5 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards d2fde46a9fe 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards 6972f25f88a 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards 36373c1f787 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 94de2fcf5a7 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 32b1c1970ed 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 49f435da185 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 4bcbb10524a 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards 378553bab6d 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards cb2163c894b 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards b59eb2319da 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 21d280f23e9 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards ee124894a16 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards 184baf4a229 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards aa8c34a24fe 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards 67735d10990 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 4642cda4545 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards a23488d319a 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 552c185c9e9 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards ac2f0b625f0 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards be1c2f93797 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards cd9e9f4a2b2 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 24bae56fe7f 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 9558fd7191b 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 1384257d929 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 3541e9fb444 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 7d28851f911 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards 0cd31e43a96 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards c1f409fe98b 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards 9be94802ca5 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards dfa1f700a51 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards da2ad8ac19a 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards 48007a3c94a 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] new 2f1775851a4 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] new 1b62ff39cc5 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new 58e113dc178 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new fefaa054c3c 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 1e16a001eb9 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new d0247bffe33 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 05d62926687 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 5525963c3ff 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new a34c52561a8 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 63b04672f7f 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 1d4bdd085d2 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new ea269161cde 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 9fd28d0c51f 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new 556b50e025f 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new d9169882284 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 4f0686b365d 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 43afb9943cf 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new 5e65e299f40 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 5b8aefbd940 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new b0c5d86f2e9 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new 7f67fb7b83c 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new fc3c5f67e86 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new a6298667fba 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 0c53571467f 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new abbd5c07204 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 43fbffe132a 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new 71902a4b010 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 90105eb3303 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 1fa8c1498ee 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new c19423e63b1 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 7ceb03134b1 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new e6f53f0bb91 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new c0b87c427ca 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new bfec93d055c 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new 09573350125 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new 22bbb0bb99d 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new 383f671eb9c 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new 5d26d6f88e7 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 3375d1e5bba 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 3ac7b0a8293 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 6aed906c9d9 151: onsuccess: #579: 1: Success after binutils: 21 commits new 527eff037df 152: onsuccess: #580: 1: Success after gcc: 6 commits new cbe9470b8c8 153: onsuccess: #582: 1: Success after glibc: 9 commits new cfc88aa2256 154: onsuccess: #583: 1: Success after linux: 10 commits new b4231f96d32 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new ebf9d25a52b 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new a076c633f89 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new 6c5d88969eb 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 31c3272894c 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new d9a288cd11c 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 22ff44fb8ac 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 2f0b135ed2e 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 094349b7a1e 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 985940c6b8b 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 20fd5c5782d 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new dba49c2ad54 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 8e37b95392d 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 3814437d93f 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 6233dd9f904 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new 13483a2f873 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new ebfd56be6e7 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 4ce6a5aebab 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new b984d1beeb2 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 71297c27e6a 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 2196926849e 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new 184d91310d0 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new c04d8cf4e84 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 1f254cf1c61 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 7884ea906d0 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 3d9e7c16910 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new ef886800974 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 9f7be33e91f 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 6fef78f33b6 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new 49d299b3fa3 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new 5a7b527a899 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new b3b0881790a 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 84967e6908c 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new c6126b88e5b 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 8003c0d3ab7 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 606db981805 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 887fe6b5a47 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 7a789b69ad1 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new cb15f070be9 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 92e85a20a8a 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new f3f95708344 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 09e1bb29e66 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 4a2eeea1a51 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 282e2acb3a2 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new ad23f629d0b 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new f39a61d3096 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new b0a1df2f1ba 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 41418ede423 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new bb6eb6add36 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 56e46a7f88a 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 6b5ee3a4a87 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 3551736db70 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 8d6969ed639 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 2b3d4a97b77 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new d83d260efc4 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new c8ff8dd2042 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new a52b148ebf3 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 3033b7a4da2 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits
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 (b83339e1efc) \ 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 1728 -> 1912 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 3428 bytes 03-build_abe-binutils/console.log.xz | Bin 52324 -> 52324 bytes 04-build_abe-gcc/console.log.xz | Bin 236908 -> 238472 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9088 -> 8492 bytes 07-build_abe-glibc/console.log.xz | Bin 237264 -> 235712 bytes 08-build_abe-gdb/console.log.xz | Bin 50700 -> 50212 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3744 -> 3788 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2036 -> 2116 bytes 11-check_regression/console.log.xz | Bin 6140 -> 4484 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 42 ++-- dashboard/dashboard-generate.sh | 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 62292 -> 62652 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 100576 -> 100592 bytes sumfiles/gas.sum | 274 +++++++++++------------ sumfiles/ld.log.xz | Bin 132036 -> 132072 bytes sumfiles/ld.sum | 342 ++++++++++++++--------------- 28 files changed, 390 insertions(+), 392 deletions(-)