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 83c85fd5b22 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gc [...] discards ad8ea0e5b00 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gc [...] discards ac7b8bf9452 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] discards 1ad5ea20609 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards f133163ec76 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards 21f6c0c94f7 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards f30f2dcdb99 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards 17611965cbf 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 349ad95ad5b 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards c700926e3e5 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 75e834ffc30 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 3853334c805 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards 783788d69e0 212: force: #24: 1: Success after binutils: 2 commits discards 8dd76ca9f75 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 52a6ca7ddb2 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 019ef4f3949 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 53804f181a0 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards a59e0e201f5 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 9f2b659db0a 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 0708acc0d07 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards a88f1f4ebf6 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 01ea66116df 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards ffa5ab81b9b 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards bf6bde1abf6 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 2c83920fef1 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 0cf8b230376 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 64ef4743819 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards cb46b8a1a4b 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 2af02000180 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 6bcaf737955 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 8239ce32146 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 20ea4d699c9 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 24a8a6d15a8 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 6bc41d36a43 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 96b45215c81 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards f83a2ca114b 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards f71e57f6eb4 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards 391d9ed7663 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards 8036fee1cc2 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 50a47cc62dc 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards c41f49608f8 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards 85fc016012a 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 43207719217 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards 0fcd3ce86f1 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards f4ce8ab4a26 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 7c9cd015007 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards 8cc45facf58 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards 8a989cb1a39 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards b1c89f447d9 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards 9eef387948d 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards c154c96d3bd 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards 4666ffb6b1f 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards c75166b46eb 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards 43a754fa2bc 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards fd46a597e8b 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards d3135e6958c 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 4741d2dc5b5 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards 8b9c83a25dc 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards 33acd80a97d 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards 91cf085e91b 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 51499771db9 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards bc4fb0bc75a 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards 8befcf776fa 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards ee80c04064b 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards 0fd11a1a70e 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards bbfab111bd0 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards bc761bc099d 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards d36860f3a5e 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards 0f5a28e618e 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards 9f830c70b09 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards c595f9d5e52 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards aaac20bee39 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 0fc13657320 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards c3ff339e91f 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 959f51a73a4 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards 4cfd68bb707 149: onsuccess: #684: 1: Success after linux: 10 commits discards 6ef9f92d9e9 148: onsuccess: #683: 1: Success after glibc: 9 commits discards a8b27f2e808 147: onsuccess: #681: 1: Success after gcc: 6 commits discards a0231e3776e 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 9ec72936c02 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards 4e606e501ba 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 77389352a7b 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards d5e6afbc903 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 890f7ef4688 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards 43693ecd6e9 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards b7e0436fa17 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards df3d99aec5e 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards df2c56e2e4c 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 9cda1298b14 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 6958585ba69 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 4c978065741 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards b69680270ff 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards cbf6010fa8a 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards be532a65b36 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 9b312416259 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 8f68fbe08ee 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards a225bb52ba8 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards f1d7e315905 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 990823496f5 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 00d49ad1efd 125: onsuccess: #658: 1: Success after linux: 3224 commits discards ae24b0e411e 124: onsuccess: #657: 1: Success after glibc: 2 commits new a78bed22b87 124: onsuccess: #657: 1: Success after glibc: 2 commits new f9bfc1cfb47 125: onsuccess: #658: 1: Success after linux: 3224 commits new 84074b33af0 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 7708984b185 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new c8441788e98 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 508b685dca6 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 4291e805bb8 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 67961e97970 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 0366390cd95 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new d01d719cab0 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new e55f8090bfd 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new efdf7547c05 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 3879cbbb924 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new ba33cf98be3 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new c41da763e57 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 2b8241702d3 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new 7a4a27bd5f3 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 2939e812fcc 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new b8e0b942912 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new b5f50c7a8db 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 843268ec9ca 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new d6ffad1466a 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new 062696f35f4 146: onsuccess: #680: 1: Success after binutils: 20 commits new d79500085f2 147: onsuccess: #681: 1: Success after gcc: 6 commits new 5bbd06549de 148: onsuccess: #683: 1: Success after glibc: 9 commits new 66b91dfed7a 149: onsuccess: #684: 1: Success after linux: 10 commits new 06897d9d7a8 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new 4ba834cacf3 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new c3425788dbd 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new cfa86c731c3 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new c34f7b4dd51 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new e47876fe0be 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new 0a521acd07d 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new 8f9ff5e7c7f 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new f4dc3d789b3 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 29836e6fa71 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new c87c8e14e09 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new aaffd3892e5 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new be1b6f1fea7 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new e683604cc01 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new b2f5acbf9a8 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new 8c52a665039 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new 32f22f2be76 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new f3d99d8a505 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 45dcc8b0d91 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new c55a7787c3c 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 09e33224b00 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new 3bafdc7edf9 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new 2fe82c32faf 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new 982a4e44ce2 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new c3101800b53 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new f357427a791 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 655e0b348a5 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new aa166bc44bb 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new 7df937eb266 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 1c8be0a8b8d 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new d66b9742af5 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 8706922574a 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new f65e3f35c6d 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new 49bfbfe2e48 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new dff4dc479d8 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 5396845a2ab 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 91ab5c3e4ef 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new db0fb1d468c 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new bffe5ab40d1 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new f2e2b8eab67 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 0a47a64ef5e 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new fba9ad56082 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 021316163d9 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 6f626b772ba 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 4b60307afc5 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 7dae5ea7dc3 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 0bc050e3d0e 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 96d587f1f67 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new c6125acace6 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 7fed33629d7 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new cf2cc9d5ec9 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 0d850165d63 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new f3d9b373ed2 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 0f9b3a76f06 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 6e89a52d4f8 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new b1252b02fd2 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 52c740f52c2 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 47b7f199518 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new afca99c3285 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 39a8d88cd51 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new e77e8ab5fcd 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new c0788a3cb54 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 00d32adce0f 212: force: #24: 1: Success after binutils: 2 commits new 16969cb602c 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 73bad9b0f7c 214: onsuccess: #26: 1: Success after binutils: 12 commits new 75db6854d5c 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 711afa31ecf 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new e2a1f8c46f2 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 5abfc670c80 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new 3152c5e6e3f 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new 6c1726e7ba8 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new b82bdb21071 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new 706b4a87883 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] new a3fc1c47e4b 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gc [...] new 47416f33595 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gc [...] new a1903b9b4a8 225: onsuccess: #41: 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 (83c85fd5b22) \ 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 2036 -> 2104 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2532 bytes 03-build_abe-binutils/console.log.xz | Bin 35064 -> 35556 bytes 04-build_abe-gcc/console.log.xz | Bin 202648 -> 202368 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8372 -> 8400 bytes 07-build_abe-glibc/console.log.xz | Bin 243172 -> 240476 bytes 08-build_abe-gdb/console.log.xz | Bin 34824 -> 35408 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3844 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2208 -> 2944 bytes 11-check_regression/console.log.xz | Bin 4912 -> 5400 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 157 +++++++++++++++++++++++++++-- 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 | 53 +++++----- mail/changes-list-short.txt | 2 +- manifest.sh => mail/last_good.sh | 0 manifest.sh | 38 +++---- sumfiles/binutils.log.xz | Bin 63000 -> 63032 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83956 -> 150784 bytes sumfiles/gas.sum | 144 +++++++++++++++++++++++++- sumfiles/ld.log.xz | Bin 122524 -> 122556 bytes sumfiles/ld.sum | 4 +- 30 files changed, 386 insertions(+), 104 deletions(-) copy manifest.sh => mail/last_good.sh (100%)