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_gdb/master-aarch64 in repository toolchain/ci/base-artifacts.

discards e6975390dd 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards d91a828b3a 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards ae48d3fb09 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards 767f16ed7a 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards b2d96828d4 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards e64c87ae12 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards f7a9aafbfe 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards 2882a074b2 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards 27e9110d28 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards b139d39ac2 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards c47c188050 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards 674e5b6dc9 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards b34672e99e 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards 64a5a5e9a0 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards 963df6c1f5 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards 286bf0301b 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards d5e49ad156 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards 6ca50883e7 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards d2b2e392da 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards 9b8f671549 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards 51e7b7f2e5 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards 98ab17d010 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards fbb5ec4360 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards 0963a2f6e8 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards fac9c82112 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards 7dc6c7e11c 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards 3f0f3827a0 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards ccb2cd79a4 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards 3dc026d90e 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards 5887672912 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards 3511986287 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards f5e5a383ab 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards 6750c7f84e 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards 6c7b2c4b8f 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards 46f16a66e3 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards 6c293e521a 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards 88cc6c73e9 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards 3069d0de2b 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards 1ce80e37fb 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards 216894d08f 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards d1564b0b1f 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards e830f57932 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards d8e32b0a1f 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards ef79712e88 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards a6ce3810a2 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards e8af37429a 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards ebceb99e10 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards b609b11206 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards 41420e30a5 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 788c715af5 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards ec824a9957 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 5abd210a83 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 5a23913097 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 205220ebc3 120: onsuccess: #906: 1: Success after binutils: 29 commits discards f97acad3e9 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards d55bec1aa9 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards b8caa431b5 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards e20891d408 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards 601cac8295 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards 314f574004 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards c59647b89e 113: onsuccess: #898: 1: Success after linux: 3 commits discards c9605854d6 112: onsuccess: #896: 1: Success after binutils: 24 commits discards c2025ca2c0 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards a5e82b4cfb 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards df96e28185 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards 3420bc92f9 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 6bade425f8 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards 1aca8cb584 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 4f5870419d 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 849d8e5b0c 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 41ea6c75d5 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards e4c2eb2c0c 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 7662bd38df 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 1269290c95 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 0824fdb42d 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards b7d784e0f3 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards 52d00969b0 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards 79c3a69fd5 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards bfe3185a25 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 58f3a7dc93 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 2b66d8447a 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 7ab85745e8 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 8615326084 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 8026f0c2e7 90: onsuccess: #867: 1: Success after binutils: 4 commits discards c05a03934e 89: onsuccess: #864: 1: Success after binutils: 25 commits discards f390a32131 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards 373ea2e4e8 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards aad8a00a2e 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards dee5c2111e 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards bd95d18386 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 347f67bbb2 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards 3bfdcc6eb9 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards cb80f93401 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards 26f172ee8d 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards bbc4d1086e 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards f62605589e 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 7139fd4241 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 181348e844 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 3ea74469ee 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards b9efd70743 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 98ff306e7a 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new baa00db784 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new e35060f426 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new c699fdd4eb 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new efbc0eb77f 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 00a7e6f755 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new d65a54d2cb 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 4e3cb02591 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new e61ce8eea5 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 79467ac07f 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new b802f5b110 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new 0fb19e456c 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new c2858bdde5 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new 5110f8e6a1 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 9df7e3a6ec 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new a072fa9a5f 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 94f55f1027 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 9f05bb800e 89: onsuccess: #864: 1: Success after binutils: 25 commits new 85f1edb786 90: onsuccess: #867: 1: Success after binutils: 4 commits new 3fd65d53a8 91: onsuccess: #870: 1: Success after binutils: 5 commits new 89822c002e 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new e68d522bc6 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 2902931efd 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new bf7ac424b8 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new e9bbedb704 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new ee2bec8c73 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new c857ac3ae1 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 1a27196964 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new be6b425ef5 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 90c02d8c90 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 972a2cb9a9 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 10e57ce087 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new 88cca05523 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new c43e928d83 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new a601c14845 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new fc00e6f363 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new 09c6a523d2 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 5cad0646ef 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 8dbae88c16 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new beb8090a82 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new b3fce11d27 112: onsuccess: #896: 1: Success after binutils: 24 commits new 1ad09a3d5e 113: onsuccess: #898: 1: Success after linux: 3 commits new 56fa60d5e7 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new a2b0d5383d 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new 04ae9dce63 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new ea971ee1e6 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new 1a19f322f8 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 52309741fb 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new de6d372d11 120: onsuccess: #906: 1: Success after binutils: 29 commits new 2ba9bc3a70 121: onsuccess: #908: 1: Success after glibc: 2 commits new 2705e886ed 122: onsuccess: #909: 1: Success after linux: 2753 commits new 5a1c51ad72 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new c2b1c572b0 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new de647a87b2 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new dc88ee8347 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new d40cbf7519 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new c2b80aff3b 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 6d5121ec5e 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new 06bb41e759 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new 6fa3cc7059 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new 98f9a7f061 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new 9b8caebe8b 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new a3f66f5371 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new 9f3b64e204 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new 79ae7acdb1 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new da112bb2d3 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new a805b898af 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new 66d79788a7 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new 2465c64cb1 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new c2cc5a9435 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new ffb7c29170 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new e2aca5a54d 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new ef12fec9b9 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new 592659f400 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new 02c4b3ce3d 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new f6b8789332 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new 9f3070c019 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new 526b75b255 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new 741e0ea7e6 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new 32974fa165 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new ac700446e8 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 47eced02f8 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new 79f667c37a 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 86279ce97b 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new 92697f9a50 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new e40085b6f1 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new 68ebad0841 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 97d9423853 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new 50850dc485 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new 9ff59f3b5b 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new fa3e631072 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new 30d1672e35 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new 9460cc22df 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new 717d6741e5 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new 784b5ec6c7 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new b97839cbce 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new fe07993e3c 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new cf34b04b1d 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new 1318cdb1b1 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new 799e239af0 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new 833e2610fe 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new da7d44a7a9 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new 7f6dfda467 174: onsuccess: #967: 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 (e6975390dd) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...]

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 1772 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 39504 -> 38932 bytes 04-build_abe-gcc/console.log.xz | Bin 214716 -> 213920 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9160 -> 8536 bytes 07-build_abe-glibc/console.log.xz | Bin 244484 -> 244924 bytes 08-build_abe-gdb/console.log.xz | Bin 38884 -> 38580 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3896 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2608 -> 2216 bytes 11-check_regression/console.log.xz | Bin 15672 -> 18796 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 37 +- 11-check_regression/mail-body.txt | 145 +- 11-check_regression/results.compare | 69 +- 11-check_regression/results.compare2 | 6094 ++++++++++++------- 11-check_regression/results.regressions | 69 +- 12-update_baseline/console.log | 64 +- 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 | 147 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 69 +- sumfiles/gdb.log.xz | Bin 2028208 -> 1988872 bytes sumfiles/gdb.sum | 9805 ++++++++----------------------- 30 files changed, 6709 insertions(+), 9838 deletions(-)