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-aarch64 in repository toolchain/ci/base-artifacts.
discards 8416d5d20944 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] discards 9e213107e120 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards a2ef64840363 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards 5339edd78e2a 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards c54267efea9e 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards 3ffb057434d9 222: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 13e8f4135a06 221: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards 3e14b2949432 220: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards 39bcf1c93733 219: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards 5e782e88e8e1 218: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 7788c7ba84c3 217: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards 9decb6219dc2 216: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards fce842d7c0ca 215: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards 52464fe91346 214: onsuccess: #26: 1: Success after binutils: 12 commits discards c5f62bcb69a2 213: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] discards b7a79a4d098f 212: force: #24: 1: Success after binutils: 2 commits discards d1fac31991fa 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 7b7683ad2215 210: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 787f76bc7624 209: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards febc028b2acb 208: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 49632b6374c9 207: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards cf73b15bd8f2 206: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 6dc3edfdf5e6 205: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 381caee3170d 204: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 63bc921d172e 203: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards 70793a296438 202: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards ba80398f78db 201: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards ed87a3a8cbd8 200: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 30df575b0daf 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards c1f08ccfbb0a 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 773c25dfced8 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards 2068f026c1a4 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 005855cb0e56 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards cea0a89f143a 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards 0066b0346d75 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 63c07f9b792d 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards 4bdfd55a1645 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 50ff725c65a9 190: onsuccess: #726: 1: Success after binutils/gcc/linux/ [...] discards 6f7fc63779b0 189: onsuccess: #725: 1: Success after binutils/gcc/linux/ [...] discards 92f145eb4c17 188: onsuccess: #724: 1: Success after binutils/gcc/linux/ [...] discards 81284f7aad5f 187: onsuccess: #723: 1: Success after binutils/gcc/linux/ [...] discards 51da5668163e 186: onsuccess: #722: 1: Success after binutils/gcc/linux/ [...] discards 824b9089dd3b 185: onsuccess: #721: 1: Success after binutils/gcc/linux/ [...] discards ad3a8589244e 184: onsuccess: #720: 1: Success after binutils/gcc/linux/ [...] discards 75a9a31212a9 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 2 [...] discards 458bcb8aa9a9 182: onsuccess: #718: 1: Success after binutils/gcc/linux/ [...] discards 169c9319b025 181: onsuccess: #717: 1: Success after binutils/gcc/linux/ [...] discards 67456e628b1d 180: onsuccess: #716: 1: Success after binutils/gcc/linux/ [...] discards 8495442fab08 179: onsuccess: #715: 1: Success after binutils/gcc/linux/ [...] discards 54d3c1556597 178: onsuccess: #714: 1: Success after binutils/gcc/linux/ [...] discards 9bc8e7a3a92b 177: onsuccess: #712: 1: Success after binutils/gcc/linux/ [...] discards 21dc3d3c224f 176: onsuccess: #711: 1: Success after binutils/gcc/linux/ [...] discards e813917963d6 175: onsuccess: #710: 1: Success after binutils/gcc/linux/ [...] discards 006e8117eab3 174: onsuccess: #709: 1: Success after binutils/gcc/linux/ [...] discards 91fd820044a4 173: onsuccess: #708: 1: Success after binutils/gcc/linux/ [...] discards 8e1016efe922 172: onsuccess: #707: 1: Success after binutils/gcc/linux/ [...] discards 469804a47934 171: onsuccess: #706: 1: Success after binutils/gcc/linux/ [...] discards b36ea5c59894 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/ [...] discards 24d10553aeec 169: onsuccess: #704: 1: Success after binutils/gcc/linux/ [...] discards 7fca25c814ae 168: onsuccess: #703: 1: Success after binutils/gcc/linux/ [...] discards 455b4e21b46b 167: onsuccess: #702: 1: Success after binutils/gcc/linux/ [...] discards d517d077f098 166: onsuccess: #701: 1: Success after binutils/gcc/linux/ [...] discards 66de428ae787 165: onsuccess: #700: 1: Success after binutils/gcc/linux/ [...] discards f7d329932637 164: onsuccess: #699: 1: Success after binutils/gcc/linux/ [...] discards b974d32a0046 163: onsuccess: #698: 1: Success after binutils/gcc/linux/ [...] discards 8165b4e5aa62 162: onsuccess: #697: 1: Success after binutils/gcc/linux/ [...] discards 0828ddf68fd4 161: onsuccess: #696: 1: Success after binutils/gcc/linux/ [...] discards 9cb90b441863 160: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] discards 521c2f4a4008 159: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] discards c0d694bee4c7 158: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] discards 9c7c0356826b 157: onsuccess: #692: 1: Success after binutils/gcc/linux/ [...] discards 4ef3024f809b 156: onsuccess: #691: 1: Success after binutils/gcc/linux/ [...] discards ddc3c25c05a3 155: onsuccess: #690: 1: Success after binutils/gcc/linux/ [...] discards 144404859f25 154: onsuccess: #689: 1: Success after binutils/gcc/linux/ [...] discards ed42158ab63c 153: onsuccess: #688: 1: Success after binutils/gcc/linux/ [...] discards 702b929a8e54 152: onsuccess: #687: 1: Success after binutils/gcc/linux/ [...] discards b84a0a39979b 151: onsuccess: #686: 1: Success after binutils/gcc/linux/ [...] discards a741d418782e 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/ [...] discards e54d705f3bd5 149: onsuccess: #684: 1: Success after linux: 10 commits discards 9bc85fe0ad79 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 0114b8f100a6 147: onsuccess: #681: 1: Success after gcc: 6 commits discards c1a684330d71 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 57bdcf06e9b5 145: onsuccess: #678: 1: Success after binutils/gcc/linux/ [...] discards aaa47151e280 144: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] discards 03bd401b5c57 143: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] discards abbb5b2aa1f9 142: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] discards 6be71bef8335 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 1 [...] discards af3bec595c7f 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 2 [...] discards 013f308b01a4 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 2 [...] discards d0bfce806364 138: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] discards 325e82948eea 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 4 [...] discards b2ae219c6b53 136: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] discards 74921897bd04 135: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] discards 348e9ae3dd65 134: onsuccess: #667: 1: Success after binutils/gcc/linux/ [...] discards fe765c7ef6cb 133: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] discards 5b568092ff27 132: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] discards c97f30624f2e 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] discards 2f5d75b7f330 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] discards 1706cdd3ee2f 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] discards 9298017b822b 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] discards b2551d0e29ca 127: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new 35c4f87f08e1 127: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new 5cd0b3d954af 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new 9d3dfab39fc7 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new 2854a5b47fa3 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] new cc47ff57d7cd 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] new 689c28f217b2 132: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] new dffc92e3742e 133: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] new b5857c44b63b 134: onsuccess: #667: 1: Success after binutils/gcc/linux/ [...] new 1fa9517392d9 135: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] new ed50c619c728 136: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] new 59581f825063 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 4 [...] new 790ba1f66a49 138: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] new ec1856e1cb5e 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 2 [...] new 5e777a8f04d1 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 2 [...] new 1077a84494b8 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 1 [...] new 46146bd99358 142: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] new e89b63bf92d4 143: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] new 83da85c8ca87 144: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] new 5a727817fb4a 145: onsuccess: #678: 1: Success after binutils/gcc/linux/ [...] new c7dbf5f344e7 146: onsuccess: #680: 1: Success after binutils: 20 commits new 52ff11b1c6f8 147: onsuccess: #681: 1: Success after gcc: 6 commits new 80de2316a9ee 148: onsuccess: #683: 1: Success after glibc: 9 commits new f108bda37dd8 149: onsuccess: #684: 1: Success after linux: 10 commits new a6d73c187d74 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/ [...] new 5e2fc803e7c2 151: onsuccess: #686: 1: Success after binutils/gcc/linux/ [...] new dab667874fef 152: onsuccess: #687: 1: Success after binutils/gcc/linux/ [...] new 8cfa0a7a3dcf 153: onsuccess: #688: 1: Success after binutils/gcc/linux/ [...] new c555f331c482 154: onsuccess: #689: 1: Success after binutils/gcc/linux/ [...] new 27a979e37bb7 155: onsuccess: #690: 1: Success after binutils/gcc/linux/ [...] new 75b181b2845e 156: onsuccess: #691: 1: Success after binutils/gcc/linux/ [...] new ec05e3fcea36 157: onsuccess: #692: 1: Success after binutils/gcc/linux/ [...] new 5c8cc60279c9 158: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] new 8dd67d3436fa 159: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] new 8649ef5391df 160: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] new c4165a5df61a 161: onsuccess: #696: 1: Success after binutils/gcc/linux/ [...] new f91a0ae498d3 162: onsuccess: #697: 1: Success after binutils/gcc/linux/ [...] new e1490f6f2bdd 163: onsuccess: #698: 1: Success after binutils/gcc/linux/ [...] new cb74982baf15 164: onsuccess: #699: 1: Success after binutils/gcc/linux/ [...] new 280517072a81 165: onsuccess: #700: 1: Success after binutils/gcc/linux/ [...] new a5490fa8f20d 166: onsuccess: #701: 1: Success after binutils/gcc/linux/ [...] new 57b5143a2818 167: onsuccess: #702: 1: Success after binutils/gcc/linux/ [...] new 6d553a239c5c 168: onsuccess: #703: 1: Success after binutils/gcc/linux/ [...] new 1b8337d77bb2 169: onsuccess: #704: 1: Success after binutils/gcc/linux/ [...] new 4ae57ee91f52 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/ [...] new 07d8ca2dde96 171: onsuccess: #706: 1: Success after binutils/gcc/linux/ [...] new 7eccc0c8db24 172: onsuccess: #707: 1: Success after binutils/gcc/linux/ [...] new f7866ccb9e54 173: onsuccess: #708: 1: Success after binutils/gcc/linux/ [...] new f94e1d68dd2d 174: onsuccess: #709: 1: Success after binutils/gcc/linux/ [...] new 7bea3839f387 175: onsuccess: #710: 1: Success after binutils/gcc/linux/ [...] new 5167ff319e78 176: onsuccess: #711: 1: Success after binutils/gcc/linux/ [...] new 335374cd94b6 177: onsuccess: #712: 1: Success after binutils/gcc/linux/ [...] new d07fca7149a1 178: onsuccess: #714: 1: Success after binutils/gcc/linux/ [...] new 24b150b2a5fe 179: onsuccess: #715: 1: Success after binutils/gcc/linux/ [...] new 7faec62ead26 180: onsuccess: #716: 1: Success after binutils/gcc/linux/ [...] new b07d06e62d2f 181: onsuccess: #717: 1: Success after binutils/gcc/linux/ [...] new 28bdf678160e 182: onsuccess: #718: 1: Success after binutils/gcc/linux/ [...] new 547bd354453e 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 2 [...] new fad378af9df1 184: onsuccess: #720: 1: Success after binutils/gcc/linux/ [...] new 52eae46336a1 185: onsuccess: #721: 1: Success after binutils/gcc/linux/ [...] new 1ea629ca6d29 186: onsuccess: #722: 1: Success after binutils/gcc/linux/ [...] new aaf251232397 187: onsuccess: #723: 1: Success after binutils/gcc/linux/ [...] new f4c9971cb576 188: onsuccess: #724: 1: Success after binutils/gcc/linux/ [...] new 0600e5be600c 189: onsuccess: #725: 1: Success after binutils/gcc/linux/ [...] new c394e3bfb62b 190: onsuccess: #726: 1: Success after binutils/gcc/linux/ [...] new 663c8cbca821 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new f6417a8b0135 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new 8afba0af14e0 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new cfdb55372c1b 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new 879f3e162567 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 6a67e5d7348d 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 6f46f329ae4f 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 0af1a99f6352 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 1a4913ab3910 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 549a1095c64c 200: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new ba2a9a9d97d7 201: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new daa6c37b4353 202: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new e4f2ca958626 203: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 971d855cfd07 204: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 009732f7e383 205: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new cd73ca51f2b4 206: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 28533e842f30 207: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 7bf34a79f9b1 208: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 762d86c5a82e 209: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 476607b3d615 210: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new a9b70b3c0cd3 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 3a88d06044c6 212: force: #24: 1: Success after binutils: 2 commits new 01143c900a51 213: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] new a34ca75ac229 214: onsuccess: #26: 1: Success after binutils: 12 commits new 0dfec8bc5903 215: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 92ac6507ce77 216: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 157498951aac 217: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new c006043b0ce6 218: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 5625bd16f505 219: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new 3d0a625571a3 220: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 739079da9ec3 221: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new 051bedb094dc 222: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new 9b10e501c6af 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new fc11a232d4b1 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new f9f4df06261c 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 96de7517a9fc 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new 5b2ff4abe190 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] new c3479ea69927 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...]
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 (8416d5d20944) \ 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 2060 -> 2036 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2536 bytes 03-build_abe-binutils/console.log.xz | Bin 35072 -> 34864 bytes 04-build_abe-gcc/console.log.xz | Bin 203704 -> 203492 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8644 -> 8168 bytes 07-build_abe-glibc/console.log.xz | Bin 240648 -> 241320 bytes 08-build_abe-gdb/console.log.xz | Bin 34784 -> 34508 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3788 -> 3780 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2104 -> 2100 bytes 11-check_regression/console.log.xz | Bin 4512 -> 4952 bytes 11-check_regression/results.compare | 10 +++--- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 44 +++++++++++++------------- 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 | 48 +++++++++++++++++++---------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 +++++++++---------- manifest.sh | 36 +++++++++++----------- sumfiles/binutils.log.xz | Bin 62816 -> 62980 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150656 -> 150792 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122644 -> 122660 bytes sumfiles/ld.sum | 4 +-- 30 files changed, 107 insertions(+), 93 deletions(-)