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 10af7021706 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 51397ec318e 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards 029e4c50123 212: force: #24: 1: Success after binutils: 2 commits discards 422a8110028 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 595626e4046 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 4655373d4ea 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards b59bf7e7fb2 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 02e6c41e4e9 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 98480832c40 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 25ceb198cb0 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 1dfc5763c8a 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 4990dba3071 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 62af3970cc6 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 0545660e7c3 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards fc0a01f06c7 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 2a66b34169c 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 01c82984de5 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 98116901bd4 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 84338d1f2f9 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards ebc2e4101e1 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 0e1bc8cdb21 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards c10ad2513d4 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 5011984f696 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 78dc008778b 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 2ad0b45ad72 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards cbf164bb953 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards 08b7881805e 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards 87cd0daf3d5 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards 6f4557cc609 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 1c901da95e3 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards be9483c5644 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards 711b42693eb 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards b8db38d209e 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards db641d84680 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards 3446a2c0d56 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 92e35330638 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards edcfba747d2 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards 51586a0e3fd 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 96609513715 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards 7054587238f 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards 4123f8b6d89 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards 5f1ae993473 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards 999a2b828cf 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards df09fd47fb7 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 50533a902bf 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 2fbb1a5dbb1 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 61adeb07a58 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards 8d574b66c43 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards c7cb3d6ba68 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards b1f45623c67 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards e0c417c45fc 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards 0c828908b6e 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards 68818eb0709 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 6472f74f6a4 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards ebb4cb9ecb1 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 92a4d3d72d5 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 80e5a0e3519 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 2d29cfd88e8 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards aa28f4e6df3 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards 840875f9ed1 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 98a5fdb37ca 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards 241db191392 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 9df74fae9e3 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards c4eecca5a25 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 025066de901 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards 6de25999706 149: onsuccess: #684: 1: Success after linux: 10 commits discards d13c53793ca 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 24ff4229145 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 37362cddc4e 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 0939ce19f13 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards c8624b7c189 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards f942ee68ffb 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards efde725deef 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 3d6808ef56f 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards 8917d998c9c 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards 73c586ab2b9 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards 2a220907f78 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 5a4c0426760 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards b502bb4a675 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards c126d951bf1 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 09883fd08ca 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards c95d71d0cea 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 1709654920d 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 02a3d0c6347 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards a4fdf8810db 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 70314b7896f 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 4f4045c3234 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards e5bcf0caa2d 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards f887834bf07 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 2514ca68eba 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 5e0d4912681 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 2c17786d4a5 123: onsuccess: #655: 1: Success after binutils: 22 commits discards db82c4e0beb 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards bbb78ad2b9b 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards dc7c60a85d0 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 4aed62677a9 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards a6dda4a5edf 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards a0c178f20cc 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 9a76600bffe 116: onsuccess: #647: 1: Success after linux: 3 commits discards f36c41967a8 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 90e3e1bca60 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 8b967671f11 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 902964da244 115: onsuccess: #645: 1: Success after binutils: 27 commits new 24b978de2d5 116: onsuccess: #647: 1: Success after linux: 3 commits new b0fc93ea0b2 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 54ef4d59eb7 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 11c8c7851dc 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new b3ff1c3c697 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new cf1219267c5 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new e6494150c6a 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new b2524b3874c 123: onsuccess: #655: 1: Success after binutils: 22 commits new 47a532a660a 124: onsuccess: #657: 1: Success after glibc: 2 commits new 2b27443b679 125: onsuccess: #658: 1: Success after linux: 3224 commits new 9c5d1b9424c 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new ef4c07b4bf4 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new dc6541fa0c8 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 2edb0c052f5 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 298d0121654 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new accd651ffa2 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 59589fc9293 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 4d9a62fd88b 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 0762836f758 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 1d2280c978b 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new a447774885b 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 15a95c0a347 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new 7fbb464ba01 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 2e3b8d5f038 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new 00980a7714d 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new e3d9e7f0c33 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new 636bec12a25 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 31cbb15b108 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 3e19522a6f1 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 14f4c063571 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new ac9e7bd8e5f 146: onsuccess: #680: 1: Success after binutils: 20 commits new 25582d0b195 147: onsuccess: #681: 1: Success after gcc: 6 commits new e36f8df7b75 148: onsuccess: #683: 1: Success after glibc: 9 commits new 2cf5d7eba13 149: onsuccess: #684: 1: Success after linux: 10 commits new 7aa0c7ff8e8 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new 5caddf4147f 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 4d094efde5a 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new 21ee9f4bfe7 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 12235e55120 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new 7bdf75386d1 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new 74d88e81b32 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new 11e58819994 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new ab5e46f56c5 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 6196cab5412 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 12edf85618e 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new f6029a60931 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new 29c267be1ff 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new aaafb40c35c 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new cb7cb33a828 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new 6b7a2a1e7e1 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new f804561ca47 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new bcee8e7b98f 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 7c3f6d485e6 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 972ed9f802a 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 88e107e419f 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new 71eb28fb3e0 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new 433dde68f51 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new 1e9decbc0d0 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new 3f2d827d5d5 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 071f4d2c5ff 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 4390b0b0f36 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new 09827205208 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new bf6fa23ed1c 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 78c0c25c4dc 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new 27bcfd31dd3 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new a1c985be215 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 878a6cd01fa 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new 75e6f69b3a8 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new 5215bd66be4 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 6a950e037fb 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new e5d3b5b6f9c 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new b07df5c16b0 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new 2bbc082b7ef 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new af2403a5e0e 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 18397b4495f 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new c4a4996ad30 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 96a8426ba28 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new b9d95ce39a7 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 70329e876c6 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 4e240e92ffb 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new f5497bf9154 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 03d2591ce2f 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 9ce6a8bcb67 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 2da2dcb0c75 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 040edc30327 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 7110150466c 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 7343923cb5e 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 66931a8e776 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new e39ad4764ee 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 4235efd8dfc 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new d95f81906db 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 93093f2d492 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 4d07001bc26 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 17a9967c43f 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 84e0a27938d 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 44026fc43fa 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new d4300a610a1 212: force: #24: 1: Success after binutils: 2 commits new fd0fc4e2cce 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 5192d0e05f5 214: onsuccess: #26: 1: Success after binutils: 12 commits new c459b4fb6f5 215: onsuccess: #27: 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 (10af7021706) \ 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 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 3448 -> 2484 bytes 03-build_abe-binutils/console.log.xz | Bin 39312 -> 34944 bytes 04-build_abe-gcc/console.log.xz | Bin 203992 -> 202768 bytes 06-build_abe-linux/console.log.xz | Bin 8556 -> 8536 bytes 07-build_abe-glibc/console.log.xz | Bin 243896 -> 242160 bytes 08-build_abe-gdb/console.log.xz | Bin 38992 -> 34664 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3784 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2652 -> 2100 bytes 11-check_regression/console.log.xz | Bin 3592 -> 5092 bytes 11-check_regression/mail-body.txt | 19 -------------- 11-check_regression/results.compare | 19 ++++++++++++-- 11-check_regression/results.compare2 | 21 ++++++++++----- 12-update_baseline/console.log | 40 ++++++++++++++--------------- 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 | 21 +-------------- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++++++----------- sumfiles/binutils.log.xz | Bin 62888 -> 63136 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83976 -> 83972 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122464 -> 122400 bytes sumfiles/ld.sum | 13 +++++----- 29 files changed, 89 insertions(+), 98 deletions(-)