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 22d2d8a629 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] discards c9bb6f8dfd 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards bca2e02e84 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] discards 7eb18fecb9 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards f0f625792b 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] discards 8c7db272a8 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 4c49f7fe04 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards 4493947af2 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] discards 2c6eab64f0 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] discards 4eee06895d 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards 1b74380ec7 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 90b1aaaab6 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards f860ff7639 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 4184252530 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards c9f110da5d 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 354d6ad2a5 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 22b3cec297 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] discards 38f39427ac 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards ccf4051189 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 463090787b 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 9085af0ee8 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards b874f2e8af 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 5733f9d3d8 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] discards 721007bb79 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards bbb27ba096 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 6761e9f73d 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 76bdf84b3e 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 287548491c 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards f14770aa4a 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards 9a0b4ebb6f 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 09706623a7 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards 6fdc7b8edc 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] discards 6a1319cd99 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards f82b3130d9 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] discards 2c7448b39d 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] discards 6e9ae385f3 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 597b865f9b 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 41c29ff14b 154: onsuccess: #583: 1: Success after linux: 10 commits discards e7e7fa3e09 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 587d3eb22a 152: onsuccess: #580: 1: Success after gcc: 6 commits discards c38918a3d7 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 438cfb41cf 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards e29845135f 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards edef1bb60b 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] discards 0bb0e84fa6 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 09c2de719b 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits discards f5a401162e 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits discards baa157da9a 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits discards dc4e31cac6 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 791cf88651 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits discards 409407ef4b 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] discards 15ada95aa4 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards dac4ada97d 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards f78961973b 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards d973ff13e3 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards 4bb9a1439f 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] discards 64b8a82c17 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 82d702ee01 134: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards ddab767bfe 133: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards da6ff3d571 132: onsuccess: #559: 1: Success after binutils/gcc/linux/gd [...] discards 235c0aea70 131: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] discards a8eb47b796 130: onsuccess: #557: 1: Success after binutils/gcc/linux/gl [...] discards f81218f48b 129: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] discards a0883d2796 128: onsuccess: #555: 1: Success after binutils/gcc/linux/gd [...] discards 7773461174 127: onsuccess: #554: 1: Success after binutils/gcc/linux/gl [...] discards 4c4e43b0ac 126: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] discards 0bba154601 125: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards b01ef1d506 124: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 619c9b4530 123: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] discards 66e310d442 122: onsuccess: #549: 1: Success after binutils/gcc/linux/gd [...] discards 90d60dea68 121: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] discards 053a5c0002 120: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] discards db2e8cd64a 119: onsuccess: #546: 1: Success after binutils/gcc/linux/gd [...] discards 64e33be1da 118: onsuccess: #545: 1: Success after binutils/gcc/linux/gd [...] discards bee32b12e4 117: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] discards b1c5aa4c82 116: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 2f8be2b013 115: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 51f0c0df2e 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] discards 370bd96602 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards 8f8890b200 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] discards d02a119e6f 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits discards e524a75ed2 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards d5bff01036 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] discards e272b64af1 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] discards c357a7ae33 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards 8ebc85ee15 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] discards 3c5922b763 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] discards 7d73dc3532 104: onsuccess: #530: 1: Success after gcc: 7 commits discards fb75aeec89 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards f384b92241 102: onsuccess: #527: 1: Success after binutils: 5 commits discards fd89b61468 101: onsuccess: #524: 1: Success after binutils: 2 commits discards b0f551c7e6 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 45ed11423b 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards e24bdfdb57 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards 0ca185fedb 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 835844951d 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards c9f476f7a5 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards 555d079d5e 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards 05ffa62035 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards c6ede80d8a 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards 759b9ab781 91: onsuccess: #511: 1: Success after linux: 27 commits new 7b4dfdbb1f 91: onsuccess: #511: 1: Success after linux: 27 commits new 8a3634a58e 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new ca86a1eeef 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new d1a6b71472 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new 39128e23f5 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new a67e3a1ae4 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 3a64109e5a 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 0dc98c312d 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new 097c7f614a 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 2848852117 100: onsuccess: #521: 1: Success after binutils: 10 commits new 6ee3034a1d 101: onsuccess: #524: 1: Success after binutils: 2 commits new 69a4903250 102: onsuccess: #527: 1: Success after binutils: 5 commits new 4ec1c915d0 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new 953067d61e 104: onsuccess: #530: 1: Success after gcc: 7 commits new 0cc6ffa8ba 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] new 4d060a58f3 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] new b0e6953067 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new c40d383b2c 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] new 8152b188e4 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] new fc4558bfb2 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 77a226c0e7 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits new 43ece10d35 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] new 1a794f51ee 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 234f186540 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] new c97dd1700a 115: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 4042f92138 116: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 93c55d3465 117: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] new 93d91a5d08 118: onsuccess: #545: 1: Success after binutils/gcc/linux/gd [...] new b418f0aa1d 119: onsuccess: #546: 1: Success after binutils/gcc/linux/gd [...] new 95b5298ad2 120: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] new 6e8c6ba6df 121: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] new 64f0d08aff 122: onsuccess: #549: 1: Success after binutils/gcc/linux/gd [...] new 0fe61461f6 123: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] new e2a7ecfce6 124: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 2855d85e84 125: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 1ae2e2be64 126: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] new 4b251eebfc 127: onsuccess: #554: 1: Success after binutils/gcc/linux/gl [...] new 41076b097e 128: onsuccess: #555: 1: Success after binutils/gcc/linux/gd [...] new 7cc2f1b76b 129: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] new 20cef17d7f 130: onsuccess: #557: 1: Success after binutils/gcc/linux/gl [...] new 1df61b823e 131: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] new ca6b119736 132: onsuccess: #559: 1: Success after binutils/gcc/linux/gd [...] new f16fcc0dab 133: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new c40461a3e7 134: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new cae3e29320 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new f3abaa4152 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] new 6270d9f29f 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new 196bc0c145 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new 786578a57b 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 792afa70c8 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 9803b232ed 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] new 0cd5ebba19 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits new 4e32db4377 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new 8494b10d7a 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits new 25d7d03038 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits new f51da19389 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits new 85e70ee051 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new c5f7c86058 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new acb2da00d3 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new f0387de04f 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new d77734d889 151: onsuccess: #579: 1: Success after binutils: 21 commits new e102f5f05b 152: onsuccess: #580: 1: Success after gcc: 6 commits new cc6d4c5c82 153: onsuccess: #582: 1: Success after glibc: 9 commits new 59309f3d52 154: onsuccess: #583: 1: Success after linux: 10 commits new baf07b8e11 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 8ec13c5490 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 6e38aa2736 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] new 12168452f2 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] new f63e58fab8 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new e314bf4911 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] new ca441b9d55 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new 0fc676533d 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new f31e252391 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new 4cfb179775 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 356568048a 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new a472d659c0 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 1bd7009fd9 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 831fabf861 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new c0a2ef7c0a 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] new 27694598cc 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new 67382439e4 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new d5b400c38d 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new d393f065f2 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 915c350e79 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new b7733878c2 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] new 6b99cd7949 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 0a362ba895 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 48723a5683 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new 4e043c6891 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new c8be581f76 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 92a9d52128 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new d1048a95e6 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new 08aba13ece 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] new 36ba980cdf 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] new dfc033b767 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new dc8f458a81 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new ef0a2ea40e 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] new b9fcd7582a 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new abee3a0e02 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] new f6a4de11f4 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 6d762a3305 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] new 6a240e4494 192: onsuccess: #627: 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 (22d2d8a629) \ 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 1748 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 52780 -> 52636 bytes 04-build_abe-gcc/console.log.xz | Bin 237284 -> 237740 bytes 06-build_abe-linux/console.log.xz | Bin 8984 -> 9096 bytes 07-build_abe-glibc/console.log.xz | Bin 237596 -> 235388 bytes 08-build_abe-gdb/console.log.xz | Bin 51580 -> 51436 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3772 -> 3772 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2428 -> 2036 bytes 11-check_regression/console.log.xz | Bin 6356 -> 6200 bytes 11-check_regression/results.compare2 | 4 +- 12-update_baseline/console.log | 66 ++++++++++++++--------------- 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 62204 -> 62576 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100616 -> 100596 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 132128 -> 132104 bytes sumfiles/ld.sum | 4 +- 28 files changed, 68 insertions(+), 68 deletions(-)