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 3033b7a4da2 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards a52b148ebf3 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards c8ff8dd2042 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards d83d260efc4 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 2b3d4a97b77 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 8d6969ed639 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 3551736db70 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 6b5ee3a4a87 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 56e46a7f88a 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards bb6eb6add36 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 41418ede423 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards b0a1df2f1ba 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards f39a61d3096 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards ad23f629d0b 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 282e2acb3a2 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 4a2eeea1a51 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 09e1bb29e66 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards f3f95708344 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 92e85a20a8a 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards cb15f070be9 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 7a789b69ad1 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 887fe6b5a47 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 606db981805 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 8003c0d3ab7 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards c6126b88e5b 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 84967e6908c 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards b3b0881790a 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 5a7b527a899 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 49d299b3fa3 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards 6fef78f33b6 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards 9f7be33e91f 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards ef886800974 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 3d9e7c16910 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 7884ea906d0 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 1f254cf1c61 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards c04d8cf4e84 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 184d91310d0 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 2196926849e 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards 71297c27e6a 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards b984d1beeb2 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 4ce6a5aebab 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards ebfd56be6e7 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 13483a2f873 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 6233dd9f904 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards 3814437d93f 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 8e37b95392d 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards dba49c2ad54 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 20fd5c5782d 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 985940c6b8b 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 094349b7a1e 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 2f0b135ed2e 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 22ff44fb8ac 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards d9a288cd11c 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 31c3272894c 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards 6c5d88969eb 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards a076c633f89 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards ebf9d25a52b 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards b4231f96d32 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards cfc88aa2256 154: onsuccess: #583: 1: Success after linux: 10 commits discards cbe9470b8c8 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 527eff037df 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 6aed906c9d9 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 3ac7b0a8293 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 3375d1e5bba 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 5d26d6f88e7 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 383f671eb9c 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards 22bbb0bb99d 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards 09573350125 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards bfec93d055c 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards c0b87c427ca 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards e6f53f0bb91 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards 7ceb03134b1 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards c19423e63b1 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 1fa8c1498ee 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 90105eb3303 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 71902a4b010 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 43fbffe132a 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards abbd5c07204 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 0c53571467f 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards a6298667fba 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards fc3c5f67e86 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards 7f67fb7b83c 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards b0c5d86f2e9 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards 5b8aefbd940 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards 5e65e299f40 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 43afb9943cf 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 4f0686b365d 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards d9169882284 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 556b50e025f 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards 9fd28d0c51f 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards ea269161cde 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 1d4bdd085d2 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 63b04672f7f 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards a34c52561a8 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 5525963c3ff 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 05d62926687 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards d0247bffe33 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards 1e16a001eb9 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards fefaa054c3c 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards 58e113dc178 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards 1b62ff39cc5 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new 3ab6a2733fd 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new a60a59c2e4b 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new 31dbe5e92a2 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 456e3c5858e 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new 59ba16ed939 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 9df08219cb4 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 244da427af4 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 570ed5ac484 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 7620d4a1e37 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 101442b6358 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 1c410ac3c33 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new fa1474f204d 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new c0f4e2e8b56 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 9f5cc4edc2f 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 5344a87c34d 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 16a23d4c386 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new e0bb0abdf06 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 55f291dfdf8 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new d2c057dff0b 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new e95df942bc4 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new 77d1d168424 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new 0243dcaa98f 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new b0ebc669ecc 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 0ab9cddb219 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 006298c86ac 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new a1bb92b4b7e 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 0c7622ce489 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new d8b987f265c 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 84531b51c58 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 22cd64ba22c 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 477469588bf 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new 736a0c6a347 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new 90ff893db34 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new f5623edff3d 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new 0df7f27e42f 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new 309d79396ce 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new 4fdeb620ce6 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 36bf3d07048 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new cdd239c2758 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 824a37cdde6 151: onsuccess: #579: 1: Success after binutils: 21 commits new 3465f4f1efc 152: onsuccess: #580: 1: Success after gcc: 6 commits new bc4fb832b26 153: onsuccess: #582: 1: Success after glibc: 9 commits new e561fe471fa 154: onsuccess: #583: 1: Success after linux: 10 commits new 9864bf4ddaa 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new ae879913a68 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new 6293bc36ecc 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new 75b9abb2a0e 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 0bcde9bef5c 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 39d0a5f354f 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new fa1c1e13cdf 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new dc92098b11f 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 5b249d7b0f3 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 973582ae8c1 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 3f24fed0aa0 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 82277251756 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new f119b31eaa6 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 981c3ce6f4a 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 842de85df1e 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new dd84a694a8e 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new 29664a9cd55 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 9c00a31a50a 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 4948a62836c 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 7146d1b147e 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 530d2fefee9 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new 5c37a259756 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new bc396fbf7e7 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 7e9f1265c05 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 5b9ecdfbfb4 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 82199722aaf 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 8caf9aadb79 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 68cd9ae5641 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 6660bfe9597 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new eedab659d51 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new ea1e80e2085 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 06db2aa8a05 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new ecf970bb80c 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 4fb640db543 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 7a7366b5ca0 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 54631dfd82b 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 556d5ff6377 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 59aef198d7c 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new b090748e5fa 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 668984a803d 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 72ef2d065e0 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 103cd9f39df 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new de4c7a24815 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 86475f0715b 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 41017edf370 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new f2ea457fa3d 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 43445161685 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 43f43cbbd8c 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new b2cf729781a 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new be1da56c667 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 2bd2f54619a 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 30f54119510 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new f89081a832b 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 9fdb5af572e 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 9d4297cbd4b 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 3c774a45276 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 829a1ad714a 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new ce0915780b1 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 1c60231cba7 213: force: #24: 1: Success after binutils: 2 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 (3033b7a4da2) \ 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 1912 -> 1944 bytes 02-prepare_abe/console.log.xz | Bin 3428 -> 3440 bytes 03-build_abe-binutils/console.log.xz | Bin 52324 -> 52632 bytes 04-build_abe-gcc/console.log.xz | Bin 238472 -> 236672 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8492 -> 8544 bytes 07-build_abe-glibc/console.log.xz | Bin 235712 -> 235404 bytes 08-build_abe-gdb/console.log.xz | Bin 50212 -> 50456 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3788 -> 3780 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2116 -> 2196 bytes 11-check_regression/console.log.xz | Bin 4484 -> 3156 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 45 +--- 12-update_baseline/console.log | 40 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- sumfiles/binutils.log.xz | Bin 62652 -> 62720 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 100592 -> 100656 bytes sumfiles/gas.sum | 274 +++++++++++------------ sumfiles/ld.log.xz | Bin 132072 -> 132024 bytes sumfiles/ld.sum | 342 ++++++++++++++--------------- 26 files changed, 378 insertions(+), 423 deletions(-)