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 0e19f43120 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards d314f143d4 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 6ee38f1307 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 294fc84e1d 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 90e50e259b 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 4e11de3d95 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards b148e203d2 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 0c14cca51e 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards e550a40d02 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 773e053cd7 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 3423bebd4d 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards bb7aadb197 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 91b193834a 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 66003f270d 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 7da4813224 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards a05d34e250 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards d9f5ba4f50 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards d3bdf79ed4 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 9d63c3703f 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 579443ddb3 215: onsuccess: #26: 1: Success after binutils: 10 commits discards 45d1004cc9 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 27e0703da9 213: force: #24: 1: Success after binutils: 2 commits discards 6216e0bbeb 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 26b9df8b44 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 56b2f9b94f 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 9c3e8d8ddd 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards a979cae2d0 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 4e1d93b9eb 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 12cbb28a95 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards c1a4747e7a 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards f5762dfa6b 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 170436f4f4 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 2159d425be 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards cbc8dbd9cb 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 0a51bd42ea 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 87c1e13fcb 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 1e674a8c0a 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards d94ba8f30a 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 3df6d354ee 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 17eda2d286 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 4c6bf84c7b 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 3e21feb20d 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 78f43b2610 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards 09eb098b9a 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] discards 25f05ed58a 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards a1f0de6564 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] discards cac8506f67 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 9f71ad91d7 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] discards e653bcea8d 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 5b058b4aef 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards 22c6cdf346 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] discards 96fec44844 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] discards ba819f6d92 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards c721d879ec 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards c8e4fafc0e 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 4e8a084b9d 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards ea0aa285ad 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards 946512c206 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 98fc89805c 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards bac90aae08 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] discards 066e273411 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 988ce35af7 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 9db1f7cc54 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 94fb335310 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 25e626f6e0 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 40dc488306 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] discards 4db5b4d2a5 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards b004d1e86a 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards f62d8e6376 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 3477191cf9 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 734e35e13a 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 927947e913 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards f10f1d270a 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 27cc673f97 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards f6bd84fddf 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] discards 3011b2d6bf 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards aca3bd5222 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] discards 38cfd19ed1 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] discards b511329f84 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 0ea394ccaf 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 91493cfc86 154: onsuccess: #583: 1: Success after linux: 10 commits discards 1df2099f2b 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 687593b743 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 8b94020316 151: onsuccess: #579: 1: Success after binutils: 21 commits discards ea49fb52f0 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards 67fd09786c 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 64925c2897 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] discards cc1c1e1409 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 1040d78083 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits discards d2ba39f2b0 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits discards b21447d3fc 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits discards 9148106eca 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 65f3d9b7b0 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits discards 60fe9c336a 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] discards a181771707 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards 206976d415 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards 26a56309de 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 07f66bc1e1 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards 188310edf2 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] discards 928567e871 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 43eaccd163 134: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 8dfb9dab65 134: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 4e245fd4c5 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new f12a2c409c 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] new 037013b1a1 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new 823f7c2491 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new ca30fa46d2 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 86ac65c2d1 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 2d1c6132ed 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] new 2e842aa764 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits new 5b7a915ba8 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new b730776f8a 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits new 374c1e686d 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits new 7421ae6ef2 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits new 62b5cd5346 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 65855c0a4b 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new 72e3b82f15 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new dfbedbc6c8 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new b75e45a809 151: onsuccess: #579: 1: Success after binutils: 21 commits new 5b945c4f04 152: onsuccess: #580: 1: Success after gcc: 6 commits new 173edfc70c 153: onsuccess: #582: 1: Success after glibc: 9 commits new 5fe81a03bc 154: onsuccess: #583: 1: Success after linux: 10 commits new 6d99f1bb6b 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new c83ca69e0a 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new f37e5f9770 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] new 2cbbfd10f7 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] new 0664999c40 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 53f59ae163 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] new ef4459c6ae 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new 83df1f3637 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 1bdc0d85b6 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new cd7d5be4c7 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 980e45a7bb 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 36e3f79dbe 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new a136dc8fe7 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 84366cc001 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new cd0e21ad77 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] new 2562f19450 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new a798b4cc24 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 08759ccf5b 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 062eddda1d 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 5e36ed7f37 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 0138d3ded8 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] new 22d44e58eb 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 5038eac8fe 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 5442e55948 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new 85493627b7 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 1bce800ceb 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 5e2c43a7ae 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 216c5e6ec5 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new f0989b546f 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] new b9cce2011a 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] new b3d894409f 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new a03eca5a71 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 622f90295a 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] new e4351eeafc 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new a76e999b32 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] new 29399dfc39 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new a9d8528a58 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] new f0a7f17ef9 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new da9874d86c 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 6e228bf3bd 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 206b4e174d 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new ee19303c5f 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new c04e571d7e 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new fafbc4eed3 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 5ecb679028 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 360f486755 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 4de317bb1e 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 6035e0fe5e 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 1f4490316f 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 48d3ff8668 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 44de991171 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 0c341c829c 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new d2061dcae3 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new a053eced19 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 8cd0ec044d 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new d83a09d921 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 6d19adb277 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 8725cae74b 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 2cf7498bc3 213: force: #24: 1: Success after binutils: 2 commits new bd1d084b3f 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new 02b58b3f7c 215: onsuccess: #26: 1: Success after binutils: 10 commits new b82e61f222 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 16a950171f 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 3545ecfc9c 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 825fae43ca 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 7af676061a 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 0ace79c243 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 2eb2bb8dca 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 91870fdeb8 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 0715ba9be7 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new c0f941f2f4 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 13c9a28d4b 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new ba96d5dc79 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 9a438412cf 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 4c00e545a0 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new bd16b7bf18 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 90d30c51f9 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new f9daa953b7 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 571a9c1fc8 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new addbbae548 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 624918485e 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...]

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 (0e19f43120) \ 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 2016 -> 2036 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 49000 -> 48776 bytes 04-build_abe-gcc/console.log.xz | Bin 234928 -> 236528 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9484 -> 8500 bytes 07-build_abe-glibc/console.log.xz | Bin 232688 -> 232360 bytes 08-build_abe-gdb/console.log.xz | Bin 46876 -> 46900 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3804 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2412 -> 2164 bytes 11-check_regression/console.log.xz | Bin 5024 -> 4840 bytes 11-check_regression/results.compare | 10 ++--- 11-check_regression/results.compare2 | 6 +-- 12-update_baseline/console.log | 68 ++++++++++++++--------------- 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 | 56 +++++++++++------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 ++++++++-------- manifest.sh | 38 ++++++++-------- sumfiles/binutils.log.xz | Bin 62784 -> 62744 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100604 -> 100960 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 132312 -> 132360 bytes sumfiles/ld.sum | 4 +- 30 files changed, 118 insertions(+), 122 deletions(-)