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 ac407681e3d 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gc [...] discards dad2d1dff07 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] discards cc9edfcee58 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards 9eef6655014 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards 367a8bcba5c 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards f165cd513e6 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards 2f8286e05f1 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards c8041bd69a9 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards d0f8fdf958a 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards f8a4c1787e9 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 2e430e4242f 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards 219adbc1269 212: force: #24: 1: Success after binutils: 2 commits discards fb9cfd6c773 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 8a25f8aafc1 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards b37fdaf4fcf 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards bd72f356a50 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards bf970344ce7 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 351cddc0cf2 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 335e7d66686 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 4f32b01b49f 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 7b1496a4d76 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 38861d54f9c 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards fb21f90a38d 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards a03a696582a 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards be9deb8db24 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 2147a03bf81 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards f9b7609bfd4 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 5986e8808bb 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 3f63d5fa1f4 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 4c1502dfa5c 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 6cc9e169b54 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards a57c9dc05e2 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 8ad222a486b 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 6cac9e2e195 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards 83ed7efd5f3 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards 84e372afb59 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards 4e614fc3673 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards 8712b2199fc 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 676b0d6795d 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards 80010a483be 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards 4571d83ddfe 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 6b2141a28a1 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards d7017e02bbf 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards d3a326e27c1 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 3b74d79165c 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards 93b59f7c805 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards fbb804ddebc 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards a427eb9b4a3 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards 8a5c0ed037e 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards 034da0f0d44 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards d10238118f9 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards 2e4f7c33b2e 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards 229b01a5574 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 07f08687078 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards eeab0c63239 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 3552abd186d 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards 679746e5ada 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards abc8e16f3cb 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards e399ecf923f 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 287484b2b2b 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards da7bcea9077 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards aa12660ad3a 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 78d6e662173 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards 06f296da415 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards b8982d4383b 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 480b53d72f6 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 7e4f8ca32ab 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards 0d85970c317 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards 3bc14dcd2d0 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 88ea2c06d92 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards 2b49191a597 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 8c53cbce87e 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards ed0fdac1060 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards f965faf0a08 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards 448c33bf86a 149: onsuccess: #684: 1: Success after linux: 10 commits discards 2e3bce7cb59 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 37fec3247e4 147: onsuccess: #681: 1: Success after gcc: 6 commits discards b85aa9ae533 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 99131fb743a 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards ba72ee4ab56 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards ae76367e7e0 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 0d7f80c24b5 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 82cb7a7b07f 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards f36cb89854e 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards b48a62a4a49 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards c6fece24a39 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards ac00e08ac24 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards bbd6f983210 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 8fe1cecab12 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 8dfd6941b91 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards a64e9229bb4 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 57f9fdefbc6 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 9a968397ac2 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards f809971da8b 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 88fe92377a2 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards af0afc3a923 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 5103aac4762 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 77f8c93bca8 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards e8958a158f3 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 012f04484f2 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 6d3176f3529 123: onsuccess: #655: 1: Success after binutils: 22 commits new 6c6a21553d8 123: onsuccess: #655: 1: Success after binutils: 22 commits new ae24b0e411e 124: onsuccess: #657: 1: Success after glibc: 2 commits new 00d49ad1efd 125: onsuccess: #658: 1: Success after linux: 3224 commits new 990823496f5 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new f1d7e315905 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new a225bb52ba8 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 8f68fbe08ee 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 9b312416259 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new be532a65b36 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new cbf6010fa8a 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new b69680270ff 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 4c978065741 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 6958585ba69 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 9cda1298b14 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new df2c56e2e4c 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new df3d99aec5e 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new b7e0436fa17 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new 43693ecd6e9 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 890f7ef4688 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new d5e6afbc903 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 77389352a7b 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 4e606e501ba 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 9ec72936c02 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new a0231e3776e 146: onsuccess: #680: 1: Success after binutils: 20 commits new a8b27f2e808 147: onsuccess: #681: 1: Success after gcc: 6 commits new 6ef9f92d9e9 148: onsuccess: #683: 1: Success after glibc: 9 commits new 4cfd68bb707 149: onsuccess: #684: 1: Success after linux: 10 commits new 959f51a73a4 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new c3ff339e91f 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 0fc13657320 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new aaac20bee39 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new c595f9d5e52 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new 9f830c70b09 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new 0f5a28e618e 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new d36860f3a5e 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new bc761bc099d 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new bbfab111bd0 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 0fd11a1a70e 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new ee80c04064b 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new 8befcf776fa 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new bc4fb0bc75a 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new 51499771db9 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new 91cf085e91b 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new 33acd80a97d 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new 8b9c83a25dc 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 4741d2dc5b5 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new d3135e6958c 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new fd46a597e8b 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new 43a754fa2bc 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new c75166b46eb 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new 4666ffb6b1f 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new c154c96d3bd 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 9eef387948d 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new b1c89f447d9 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new 8a989cb1a39 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new 8cc45facf58 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 7c9cd015007 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new f4ce8ab4a26 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 0fcd3ce86f1 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 43207719217 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new 85fc016012a 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new c41f49608f8 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 50a47cc62dc 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 8036fee1cc2 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new 391d9ed7663 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new f71e57f6eb4 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new f83a2ca114b 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 96b45215c81 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 6bc41d36a43 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 24a8a6d15a8 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 20ea4d699c9 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 8239ce32146 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 6bcaf737955 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 2af02000180 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new cb46b8a1a4b 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 64ef4743819 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 0cf8b230376 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 2c83920fef1 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new bf6bde1abf6 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new ffa5ab81b9b 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 01ea66116df 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new a88f1f4ebf6 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 0708acc0d07 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 9f2b659db0a 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new a59e0e201f5 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 53804f181a0 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 019ef4f3949 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 52a6ca7ddb2 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 8dd76ca9f75 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 783788d69e0 212: force: #24: 1: Success after binutils: 2 commits new 3853334c805 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 75e834ffc30 214: onsuccess: #26: 1: Success after binutils: 12 commits new c700926e3e5 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 349ad95ad5b 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 17611965cbf 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new f30f2dcdb99 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new 21f6c0c94f7 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new f133163ec76 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new 1ad5ea20609 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new ac7b8bf9452 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] new ad8ea0e5b00 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gc [...] new 83c85fd5b22 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gc [...]
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 (ac407681e3d) \ 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 2072 -> 2036 bytes 02-prepare_abe/console.log.xz | Bin 2524 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 35128 -> 35064 bytes 04-build_abe-gcc/console.log.xz | Bin 202888 -> 202648 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8508 -> 8372 bytes 07-build_abe-glibc/console.log.xz | Bin 241600 -> 243172 bytes 08-build_abe-gdb/console.log.xz | Bin 34512 -> 34824 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3840 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2184 -> 2208 bytes 11-check_regression/console.log.xz | Bin 5232 -> 4912 bytes 11-check_regression/results.compare | 8 ++-- 11-check_regression/results.compare2 | 6 +-- 12-update_baseline/console.log | 70 ++++++++++++++--------------- 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 | 57 +++++++++++------------ mail/changes-list-short.txt | 2 +- manifest.sh | 36 +++++++-------- sumfiles/binutils.log.xz | Bin 63100 -> 63000 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83976 -> 83956 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 122508 -> 122524 bytes sumfiles/ld.sum | 4 +- 29 files changed, 99 insertions(+), 102 deletions(-)