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 22bcdca72944 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards e9c19f9bed03 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards 621be34b00d4 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards fc6e9018dfab 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards ba64dad01df2 222: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 7c544160e5d4 221: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards ecb336fa466a 220: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards 13258bd572bb 219: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards 6f7186d2c1f7 218: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 35a05c944f66 217: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards c137d2c24d20 216: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards b1cb544f7233 215: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards e5baa2a57808 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 6c0a229e327c 213: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] discards 7471f8f927b5 212: force: #24: 1: Success after binutils: 2 commits discards a0a77261af6b 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards fb8f8764a940 210: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 8439265ca1f9 209: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 5d54f8dd85d3 208: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 9d53d513718d 207: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 50665656aa0d 206: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards ff506c14123a 205: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 483b7c50ddcc 204: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 2c02ad76d6f8 203: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards a7a9a6dd7955 202: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards b78f49f50335 201: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 9ae870628dd9 200: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 6d997d48b880 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 5a791f692b5e 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 25cee20e1b5f 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards b8c3c986b998 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards e6126fe9c1db 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 6a4952fd92c6 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards 91b373c9e832 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 44fa27ebe7dd 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards ad47e65835c3 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards f80e05a4ebc4 190: onsuccess: #726: 1: Success after binutils/gcc/linux/ [...] discards c822c09bdc88 189: onsuccess: #725: 1: Success after binutils/gcc/linux/ [...] discards 83cfcdf4aa10 188: onsuccess: #724: 1: Success after binutils/gcc/linux/ [...] discards a37254db7cb4 187: onsuccess: #723: 1: Success after binutils/gcc/linux/ [...] discards dd1f7e45a1ae 186: onsuccess: #722: 1: Success after binutils/gcc/linux/ [...] discards b929b31f0311 185: onsuccess: #721: 1: Success after binutils/gcc/linux/ [...] discards 8ae64a14686b 184: onsuccess: #720: 1: Success after binutils/gcc/linux/ [...] discards 40c88845b870 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 2 [...] discards 0bb84065bc73 182: onsuccess: #718: 1: Success after binutils/gcc/linux/ [...] discards 9733f67971d1 181: onsuccess: #717: 1: Success after binutils/gcc/linux/ [...] discards 2811bf9646e8 180: onsuccess: #716: 1: Success after binutils/gcc/linux/ [...] discards 9c6bf28e34e8 179: onsuccess: #715: 1: Success after binutils/gcc/linux/ [...] discards fda6363bc5ed 178: onsuccess: #714: 1: Success after binutils/gcc/linux/ [...] discards dfd0595177b7 177: onsuccess: #712: 1: Success after binutils/gcc/linux/ [...] discards ba51cfb1aa63 176: onsuccess: #711: 1: Success after binutils/gcc/linux/ [...] discards 8b8ebd9159c7 175: onsuccess: #710: 1: Success after binutils/gcc/linux/ [...] discards c205ae92fa33 174: onsuccess: #709: 1: Success after binutils/gcc/linux/ [...] discards fc873720eccf 173: onsuccess: #708: 1: Success after binutils/gcc/linux/ [...] discards d2231b39c57f 172: onsuccess: #707: 1: Success after binutils/gcc/linux/ [...] discards c0b396734e19 171: onsuccess: #706: 1: Success after binutils/gcc/linux/ [...] discards 65bd90d78e96 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/ [...] discards 390195895b20 169: onsuccess: #704: 1: Success after binutils/gcc/linux/ [...] discards 8b85cbdbf70b 168: onsuccess: #703: 1: Success after binutils/gcc/linux/ [...] discards b9e94adf4459 167: onsuccess: #702: 1: Success after binutils/gcc/linux/ [...] discards e94c85e7f409 166: onsuccess: #701: 1: Success after binutils/gcc/linux/ [...] discards d3f47cf1fb5f 165: onsuccess: #700: 1: Success after binutils/gcc/linux/ [...] discards 27074672d9ff 164: onsuccess: #699: 1: Success after binutils/gcc/linux/ [...] discards 2805740df6b3 163: onsuccess: #698: 1: Success after binutils/gcc/linux/ [...] discards 78322ff1899d 162: onsuccess: #697: 1: Success after binutils/gcc/linux/ [...] discards cc6bed519f28 161: onsuccess: #696: 1: Success after binutils/gcc/linux/ [...] discards 9407f7531019 160: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] discards afc525c5bea4 159: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] discards ccbca671e21d 158: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] discards 8da4558a1add 157: onsuccess: #692: 1: Success after binutils/gcc/linux/ [...] discards 9d0314fc3ff3 156: onsuccess: #691: 1: Success after binutils/gcc/linux/ [...] discards 7d6dd4f0ae40 155: onsuccess: #690: 1: Success after binutils/gcc/linux/ [...] discards 729979446472 154: onsuccess: #689: 1: Success after binutils/gcc/linux/ [...] discards 96c18b97387b 153: onsuccess: #688: 1: Success after binutils/gcc/linux/ [...] discards 4f5d4315d8a1 152: onsuccess: #687: 1: Success after binutils/gcc/linux/ [...] discards 470d7d1e2563 151: onsuccess: #686: 1: Success after binutils/gcc/linux/ [...] discards 1ae13cb11aa6 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/ [...] discards 3d7aa492fcce 149: onsuccess: #684: 1: Success after linux: 10 commits discards 60b32882f4b5 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 9ca22acdfcd4 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 79dbbc438675 146: onsuccess: #680: 1: Success after binutils: 20 commits discards d6b65f039f71 145: onsuccess: #678: 1: Success after binutils/gcc/linux/ [...] discards 7eed9855e447 144: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] discards 05911190ffa1 143: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] discards 183e0bbed0be 142: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] discards 8cb515d70d0a 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 1 [...] discards f8122c5f9d54 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 2 [...] discards 20d6a67792ec 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 2 [...] discards 8b3aa950eb42 138: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] discards 8dccce2fe855 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 4 [...] discards 8992ec749a04 136: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] discards 61ee2c65128b 135: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] discards c060e720cc1e 134: onsuccess: #667: 1: Success after binutils/gcc/linux/ [...] discards f22532fbc70d 133: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] discards 4c67973cd002 132: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] discards 82db390c850b 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] discards 371c14ef2009 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] discards cae20cf216b7 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] discards 8abacdcdbfa7 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] discards 13959ba9d0d5 127: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] discards 6286f409f9ec 126: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] new 03708cff0b88 126: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] new b2551d0e29ca 127: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new 9298017b822b 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new 1706cdd3ee2f 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new 2f5d75b7f330 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] new c97f30624f2e 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] new 5b568092ff27 132: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] new fe765c7ef6cb 133: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] new 348e9ae3dd65 134: onsuccess: #667: 1: Success after binutils/gcc/linux/ [...] new 74921897bd04 135: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] new b2ae219c6b53 136: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] new 325e82948eea 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 4 [...] new d0bfce806364 138: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] new 013f308b01a4 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 2 [...] new af3bec595c7f 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 2 [...] new 6be71bef8335 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 1 [...] new abbb5b2aa1f9 142: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] new 03bd401b5c57 143: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] new aaa47151e280 144: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] new 57bdcf06e9b5 145: onsuccess: #678: 1: Success after binutils/gcc/linux/ [...] new c1a684330d71 146: onsuccess: #680: 1: Success after binutils: 20 commits new 0114b8f100a6 147: onsuccess: #681: 1: Success after gcc: 6 commits new 9bc85fe0ad79 148: onsuccess: #683: 1: Success after glibc: 9 commits new e54d705f3bd5 149: onsuccess: #684: 1: Success after linux: 10 commits new a741d418782e 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/ [...] new b84a0a39979b 151: onsuccess: #686: 1: Success after binutils/gcc/linux/ [...] new 702b929a8e54 152: onsuccess: #687: 1: Success after binutils/gcc/linux/ [...] new ed42158ab63c 153: onsuccess: #688: 1: Success after binutils/gcc/linux/ [...] new 144404859f25 154: onsuccess: #689: 1: Success after binutils/gcc/linux/ [...] new ddc3c25c05a3 155: onsuccess: #690: 1: Success after binutils/gcc/linux/ [...] new 4ef3024f809b 156: onsuccess: #691: 1: Success after binutils/gcc/linux/ [...] new 9c7c0356826b 157: onsuccess: #692: 1: Success after binutils/gcc/linux/ [...] new c0d694bee4c7 158: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] new 521c2f4a4008 159: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] new 9cb90b441863 160: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] new 0828ddf68fd4 161: onsuccess: #696: 1: Success after binutils/gcc/linux/ [...] new 8165b4e5aa62 162: onsuccess: #697: 1: Success after binutils/gcc/linux/ [...] new b974d32a0046 163: onsuccess: #698: 1: Success after binutils/gcc/linux/ [...] new f7d329932637 164: onsuccess: #699: 1: Success after binutils/gcc/linux/ [...] new 66de428ae787 165: onsuccess: #700: 1: Success after binutils/gcc/linux/ [...] new d517d077f098 166: onsuccess: #701: 1: Success after binutils/gcc/linux/ [...] new 455b4e21b46b 167: onsuccess: #702: 1: Success after binutils/gcc/linux/ [...] new 7fca25c814ae 168: onsuccess: #703: 1: Success after binutils/gcc/linux/ [...] new 24d10553aeec 169: onsuccess: #704: 1: Success after binutils/gcc/linux/ [...] new b36ea5c59894 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/ [...] new 469804a47934 171: onsuccess: #706: 1: Success after binutils/gcc/linux/ [...] new 8e1016efe922 172: onsuccess: #707: 1: Success after binutils/gcc/linux/ [...] new 91fd820044a4 173: onsuccess: #708: 1: Success after binutils/gcc/linux/ [...] new 006e8117eab3 174: onsuccess: #709: 1: Success after binutils/gcc/linux/ [...] new e813917963d6 175: onsuccess: #710: 1: Success after binutils/gcc/linux/ [...] new 21dc3d3c224f 176: onsuccess: #711: 1: Success after binutils/gcc/linux/ [...] new 9bc8e7a3a92b 177: onsuccess: #712: 1: Success after binutils/gcc/linux/ [...] new 54d3c1556597 178: onsuccess: #714: 1: Success after binutils/gcc/linux/ [...] new 8495442fab08 179: onsuccess: #715: 1: Success after binutils/gcc/linux/ [...] new 67456e628b1d 180: onsuccess: #716: 1: Success after binutils/gcc/linux/ [...] new 169c9319b025 181: onsuccess: #717: 1: Success after binutils/gcc/linux/ [...] new 458bcb8aa9a9 182: onsuccess: #718: 1: Success after binutils/gcc/linux/ [...] new 75a9a31212a9 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 2 [...] new ad3a8589244e 184: onsuccess: #720: 1: Success after binutils/gcc/linux/ [...] new 824b9089dd3b 185: onsuccess: #721: 1: Success after binutils/gcc/linux/ [...] new 51da5668163e 186: onsuccess: #722: 1: Success after binutils/gcc/linux/ [...] new 81284f7aad5f 187: onsuccess: #723: 1: Success after binutils/gcc/linux/ [...] new 92f145eb4c17 188: onsuccess: #724: 1: Success after binutils/gcc/linux/ [...] new 6f7fc63779b0 189: onsuccess: #725: 1: Success after binutils/gcc/linux/ [...] new 50ff725c65a9 190: onsuccess: #726: 1: Success after binutils/gcc/linux/ [...] new 4bdfd55a1645 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 63c07f9b792d 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new 0066b0346d75 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new cea0a89f143a 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new 005855cb0e56 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 2068f026c1a4 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 773c25dfced8 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new c1f08ccfbb0a 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 30df575b0daf 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new ed87a3a8cbd8 200: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new ba80398f78db 201: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 70793a296438 202: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 63bc921d172e 203: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 381caee3170d 204: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 6dc3edfdf5e6 205: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new cf73b15bd8f2 206: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 49632b6374c9 207: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new febc028b2acb 208: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 787f76bc7624 209: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 7b7683ad2215 210: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new d1fac31991fa 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new b7a79a4d098f 212: force: #24: 1: Success after binutils: 2 commits new c5f62bcb69a2 213: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] new 52464fe91346 214: onsuccess: #26: 1: Success after binutils: 12 commits new fce842d7c0ca 215: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 9decb6219dc2 216: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 7788c7ba84c3 217: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new 5e782e88e8e1 218: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 39bcf1c93733 219: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new 3e14b2949432 220: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 13e8f4135a06 221: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new 3ffb057434d9 222: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new c54267efea9e 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 5339edd78e2a 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new a2ef64840363 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 9e213107e120 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new 8416d5d20944 227: onsuccess: #43: 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 (22bcdca72944) \ 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 2092 -> 2060 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2520 bytes 03-build_abe-binutils/console.log.xz | Bin 35004 -> 35072 bytes 04-build_abe-gcc/console.log.xz | Bin 204000 -> 203704 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8880 -> 8644 bytes 07-build_abe-glibc/console.log.xz | Bin 240516 -> 240648 bytes 08-build_abe-gdb/console.log.xz | Bin 34692 -> 34784 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3788 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2100 -> 2104 bytes 11-check_regression/console.log.xz | Bin 4984 -> 4512 bytes 11-check_regression/results.compare | 8 +++--- 11-check_regression/results.compare2 | 20 ++++---------- 12-update_baseline/console.log | 42 ++++++++++++++-------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 43 ++++++++++++----------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 36 ++++++++++++------------ manifest.sh | 32 ++++++++++----------- sumfiles/binutils.log.xz | Bin 63000 -> 62816 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150812 -> 150656 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122632 -> 122644 bytes sumfiles/ld.sum | 4 +-- 29 files changed, 93 insertions(+), 110 deletions(-)