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 c459b4fb6f5 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 5192d0e05f5 214: onsuccess: #26: 1: Success after binutils: 12 commits discards fd0fc4e2cce 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards d4300a610a1 212: force: #24: 1: Success after binutils: 2 commits discards 44026fc43fa 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 84e0a27938d 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 17a9967c43f 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 4d07001bc26 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 93093f2d492 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards d95f81906db 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 4235efd8dfc 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards e39ad4764ee 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 66931a8e776 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 7343923cb5e 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 7110150466c 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 040edc30327 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 2da2dcb0c75 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 9ce6a8bcb67 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 03d2591ce2f 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards f5497bf9154 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 4e240e92ffb 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 70329e876c6 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards b9d95ce39a7 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 96a8426ba28 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards c4a4996ad30 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 18397b4495f 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards af2403a5e0e 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards 2bbc082b7ef 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards b07df5c16b0 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards e5d3b5b6f9c 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 6a950e037fb 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards 5215bd66be4 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards 75e6f69b3a8 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 878a6cd01fa 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards a1c985be215 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards 27bcfd31dd3 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 78c0c25c4dc 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards bf6fa23ed1c 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards 09827205208 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 4390b0b0f36 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards 071f4d2c5ff 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards 3f2d827d5d5 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards 1e9decbc0d0 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards 433dde68f51 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards 71eb28fb3e0 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 88e107e419f 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 972ed9f802a 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 7c3f6d485e6 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards bcee8e7b98f 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards f804561ca47 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards 6b7a2a1e7e1 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards cb7cb33a828 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards aaafb40c35c 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards 29c267be1ff 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards f6029a60931 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards 12edf85618e 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 6196cab5412 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards ab5e46f56c5 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 11e58819994 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards 74d88e81b32 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards 7bdf75386d1 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 12235e55120 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards 21ee9f4bfe7 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 4d094efde5a 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards 5caddf4147f 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 7aa0c7ff8e8 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards 2cf5d7eba13 149: onsuccess: #684: 1: Success after linux: 10 commits discards e36f8df7b75 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 25582d0b195 147: onsuccess: #681: 1: Success after gcc: 6 commits discards ac9e7bd8e5f 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 14f4c063571 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards 3e19522a6f1 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 31cbb15b108 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 636bec12a25 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards e3d9e7f0c33 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards 00980a7714d 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards 2e3b8d5f038 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards 7fbb464ba01 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 15a95c0a347 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards a447774885b 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 1d2280c978b 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 0762836f758 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards 4d9a62fd88b 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 59589fc9293 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards accd651ffa2 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 298d0121654 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 2edb0c052f5 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards dc6541fa0c8 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards ef4c07b4bf4 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 9c5d1b9424c 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 2b27443b679 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 47a532a660a 124: onsuccess: #657: 1: Success after glibc: 2 commits discards b2524b3874c 123: onsuccess: #655: 1: Success after binutils: 22 commits discards e6494150c6a 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards cf1219267c5 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards b3ff1c3c697 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 11c8c7851dc 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 54ef4d59eb7 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards b0fc93ea0b2 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 24b978de2d5 116: onsuccess: #647: 1: Success after linux: 3 commits discards 902964da244 115: onsuccess: #645: 1: Success after binutils: 27 commits new cc236af1e24 115: onsuccess: #645: 1: Success after binutils: 27 commits new 6a382941ab0 116: onsuccess: #647: 1: Success after linux: 3 commits new 98c412b0f43 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 093510d0d63 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 4e6af8f7435 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 55784028e70 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new c287b4460dc 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 9e5f0d37403 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new d44e02968ad 123: onsuccess: #655: 1: Success after binutils: 22 commits new 75b803ec916 124: onsuccess: #657: 1: Success after glibc: 2 commits new 7e6f4ef30c7 125: onsuccess: #658: 1: Success after linux: 3224 commits new 4d9b4290a06 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 5c0f52dafc5 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 4454e637cdd 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new c2edf3c0df3 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new dc88882b6e4 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 597dc838e3c 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 14eed913429 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 50b38fd671d 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 24984ed33a3 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 19b2460a34c 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 57672e4b1e1 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 36b9a329344 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new 43558d777b5 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 26c81971263 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new 74bada3ef7e 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 45cd974570c 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new a9289c06d3d 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 3798b6892ec 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 3c0f639295c 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new dbbda113059 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new 3d17d636c45 146: onsuccess: #680: 1: Success after binutils: 20 commits new aa26d104b04 147: onsuccess: #681: 1: Success after gcc: 6 commits new 058574d1b9f 148: onsuccess: #683: 1: Success after glibc: 9 commits new 87c657bd1a5 149: onsuccess: #684: 1: Success after linux: 10 commits new 6c58167028d 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new 4ee024a6e53 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 781c42b2e65 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new 0ea6271083c 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 4ebb71e446e 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new 6d6074b3245 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new 77c427fdfc5 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new 32bbaa3ff2f 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new 05e404020b4 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 203b04db372 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new f1a803b6d5a 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 72a4eed47ab 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new d9623fda1d7 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new 033b90367a2 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new 91743060a62 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new 1d03142f52c 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new 9e9ede05776 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new a806ae4b6ff 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 4483ddf145d 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 11eb7700d30 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 4199e09cf0c 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new f5e217144c7 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new c6e8478f880 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new eab11a33ed1 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new 77320e6c5fd 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new ce898fc2603 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new a171caff91d 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new 795e739f0b6 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new 1e343b6c020 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new dd710b7627f 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new f20c4a5d724 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 111acde9af3 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new dffcbb41b59 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new 252654c198f 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new 6f7d97d3117 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 6e32ca20af4 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 7e23baa069d 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new d82e6a41576 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new edd01b48cfd 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new c13beb0a482 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 4edf23447b8 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 58fad1c6361 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 0c1272e8f05 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 720afc686d0 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 39316cc251a 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 40116ddac97 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 96e23bda678 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 0b9cc3ba592 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 071a40f8e53 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new ceb7c1e3cd9 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new fdd6a58ef19 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new a7433ddcf23 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new b366c1239e0 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new c845bc4301a 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 565bcca7aad 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new f987b629b4d 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new fa9074a7aa9 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 2ecc2c6c078 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new daffc477129 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 8ae06ef963a 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new c423d989f6a 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new ce6809770bd 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 29f0c75ed2f 212: force: #24: 1: Success after binutils: 2 commits new 85bd1f6478a 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 931d738cf54 214: onsuccess: #26: 1: Success after binutils: 12 commits new 2fff4d463d2 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new f449011b4c6 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...]

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 (c459b4fb6f5) \ 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 1760 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2484 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 34944 -> 35312 bytes 04-build_abe-gcc/console.log.xz | Bin 202768 -> 203940 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8536 -> 8200 bytes 07-build_abe-glibc/console.log.xz | Bin 242160 -> 242252 bytes 08-build_abe-gdb/console.log.xz | Bin 34664 -> 34916 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3836 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2100 -> 2344 bytes 11-check_regression/console.log.xz | Bin 5092 -> 4816 bytes 11-check_regression/results.compare | 25 ++++------------- 11-check_regression/results.compare2 | 23 +++++----------- 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/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++++------------ sumfiles/binutils.log.xz | Bin 63136 -> 62632 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83972 -> 83968 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122400 -> 122464 bytes sumfiles/ld.sum | 4 +-- 29 files changed, 63 insertions(+), 87 deletions(-)