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 c98fd389ca21 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: [...] discards a68372d7f85b 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards d8e5d8e9d60f 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/g [...] discards bb3911fde8b6 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37 [...] discards 164f26197da2 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.900 [...] discards 41a668f4a3f6 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards e8166cd509a4 227: force: #81: 1: [TCWG CI] Failure after baseline build [...] discards 689830700837 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards 79470657747b 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards d15c883257f2 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards d3199563b474 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 124a55e93c1c 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/g [...] discards 9bb641c4a73c 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards 7b23403474db 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards 2ddfb22d1080 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards db8de1871063 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/g [...] discards bde89ce44324 217: onsuccess: #53: 1: Success after binutils/gcc/linux/g [...] discards f8987b58c3f1 216: onsuccess: #52: 1: Success after binutils/gcc/linux/g [...] discards bd2fcda259f5 215: onsuccess: #48: 1: Success after binutils/gcc/linux/g [...] discards aee3ba2b43d5 214: onsuccess: #47: 1: Success after gdb: 21 commits discards fbb67cd10afe 213: force: #46: 1: Success after gdb-13-branchpoint-1550- [...] discards 68f425523c03 212: force: #45: 1: Success after gdb: 22 commits discards 5c3473ea3673 211: onsuccess: #44: 1: Success after linux: 26 commits discards dd5947b73194 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181- [...] discards b99b84631337 209: force: #37: 1: Success after baseline build: no new commits discards cc9ef43e04ed 208: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards b317b76772c6 207: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 8034275b50e2 206: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards d72861888bca 205: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards 8482aec7d7f5 204: force: #26: : Failure after baseline build: no new commits discards 50c5b03d560a 203: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards b114dbaf8100 202: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards b537e207f7fd 201: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 21fc97d5277f 200: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards ff48de8c8a34 199: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards ed059b149318 198: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 874393c35dc4 197: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards 546fb9916370 196: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards 2f4b96423cb0 195: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards d3e9228153ac 194: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 158be3a408ec 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 4f38eaa59d39 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards c05d8dadf78e 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards 4ba3aef6c825 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards b0d757ee5860 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 8e04ca8e2d99 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards 78e6506d97a6 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 0ef06341fc62 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards 4a289ea78f11 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards e215f2ea7b56 184: onsuccess: #977: 1: Success after binutils/gcc/linux/ [...] discards bf8eafc6e434 183: onsuccess: #976: 1: Success after binutils/gcc/linux/ [...] discards d7e1505b429f 182: onsuccess: #975: 1: Success after binutils/gcc/linux/ [...] discards 94996cf1b04a 181: onsuccess: #974: 1: Success after binutils/gcc/linux/ [...] discards 2a12f3183a9a 180: onsuccess: #973: 1: Success after binutils/gcc/linux/ [...] discards de14562f815f 179: onsuccess: #972: 1: Success after binutils/gcc/linux/ [...] discards bf602d459adb 178: onsuccess: #971: 1: Success after binutils/gcc/linux/ [...] discards 7f710885bfa5 177: onsuccess: #970: 1: Success after binutils/gcc/linux/ [...] discards d30ac5abf31f 176: onsuccess: #969: 1: Success after binutils/gcc/linux/ [...] discards 7b33437b74d1 175: onsuccess: #968: 1: Success after binutils/gcc/linux/ [...] discards 242bba3610b4 174: onsuccess: #967: 1: Success after binutils/gcc/linux/ [...] discards a4776e96bde0 173: onsuccess: #966: 1: Success after binutils/gcc/linux/ [...] discards 7892c0e2631b 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/ [...] discards bea43ce7826d 171: onsuccess: #964: 1: Success after binutils/gcc/linux/ [...] discards cf460cede84a 170: onsuccess: #963: 1: Success after binutils/gcc/linux/ [...] discards 215b51a366bd 169: onsuccess: #962: 1: Success after binutils/gcc/linux/ [...] discards 315e711eba5e 168: onsuccess: #961: 1: Success after binutils/gcc/linux/ [...] discards 4bb6414cc60f 167: onsuccess: #960: 1: Success after binutils/gcc/linux/ [...] discards 02ccde8adfee 166: onsuccess: #959: 1: Success after binutils/gcc/linux/ [...] discards 9a390d42ca4d 165: onsuccess: #958: 1: Success after binutils/gcc/linux/ [...] discards 9b93db934bd8 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/ [...] discards a6ac83880c83 163: onsuccess: #956: 1: Success after binutils/gcc/linux/ [...] discards e282d475e1b2 162: onsuccess: #955: 1: Success after binutils/gcc/linux/ [...] discards fb46cdaf1dba 161: onsuccess: #954: 1: Success after binutils/gcc/linux/ [...] discards f00bdd805d2f 160: onsuccess: #953: 1: Success after binutils/gcc/linux/ [...] discards 611df0ff04a1 159: onsuccess: #952: 1: Success after binutils/gcc/linux/ [...] discards 23c2d3dc66c7 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 5a6fbfdd3586 157: onsuccess: #950: 1: Success after binutils/gcc/linux/ [...] discards 085d4c9025a8 156: onsuccess: #949: 1: Success after binutils/gcc/linux/ [...] discards 009dda8fcdfc 155: onsuccess: #948: 1: Success after binutils/gcc/linux/ [...] discards 58e2362e0279 154: onsuccess: #947: 1: Success after binutils/gcc/linux/ [...] discards 8618576727d1 153: onsuccess: #946: 1: Success after binutils/gcc/linux/ [...] discards 2966ce36ed0c 152: onsuccess: #945: 1: Success after binutils/gcc/linux/ [...] discards 1ba658452db7 151: onsuccess: #944: 1: Success after binutils/gcc/linux/ [...] discards 66b7f9c2b6ae 150: onsuccess: #943: 1: Success after binutils/gcc/linux/ [...] discards 94fc3653f23a 149: onsuccess: #942: 1: Success after binutils/gcc/linux/ [...] discards f386d11e603a 148: onsuccess: #941: 1: Success after binutils/gcc/linux/ [...] discards bd5ef690eada 147: onsuccess: #940: 1: Success after binutils/gcc/linux/ [...] discards bdae85645a91 146: onsuccess: #939: 1: Success after binutils/gcc/linux/ [...] discards 50f395ce7609 145: onsuccess: #934: 1: Success after binutils/gcc/linux/ [...] discards c05278e5277b 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/ [...] discards cc42d2d1178e 143: onsuccess: #931: 1: Success after binutils/gcc/linux/ [...] discards 37a07f5a9191 142: onsuccess: #929: 1: Success after binutils/gcc/linux/ [...] discards 498fa37b63e6 141: onsuccess: #928: 1: Success after binutils/gcc/linux/ [...] discards 53bd33e59ce6 140: onsuccess: #927: 1: Success after binutils/gcc/linux/ [...] discards 5f528a542544 139: onsuccess: #926: 1: Success after binutils/gcc/linux/ [...] discards 5e7df03c52e9 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 1 [...] discards 89e5f9d9bf77 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 4 [...] discards ba7d9d6de2a0 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 1 [...] discards aad408c663e2 135: onsuccess: #922: 1: Success after binutils/gcc/linux/ [...] discards de572fc2c340 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 2 [...] discards 798317f324b0 133: onsuccess: #920: 1: Success after binutils/gcc/linux/ [...] new dfa21b9d375c 133: onsuccess: #920: 1: Success after binutils/gcc/linux/ [...] new 88b3dc6ca123 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 2 [...] new 11b9acb73606 135: onsuccess: #922: 1: Success after binutils/gcc/linux/ [...] new ba505518abc5 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 1 [...] new 56827f87c11c 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 4 [...] new 7705d02482a8 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 1 [...] new bce1dedaf3ec 139: onsuccess: #926: 1: Success after binutils/gcc/linux/ [...] new 8ee89a22fc97 140: onsuccess: #927: 1: Success after binutils/gcc/linux/ [...] new ba5582e30ee6 141: onsuccess: #928: 1: Success after binutils/gcc/linux/ [...] new be565b73d940 142: onsuccess: #929: 1: Success after binutils/gcc/linux/ [...] new a9d48882192e 143: onsuccess: #931: 1: Success after binutils/gcc/linux/ [...] new 09da31a1ed6c 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/ [...] new dc600b50fb03 145: onsuccess: #934: 1: Success after binutils/gcc/linux/ [...] new d191f7f2d6b5 146: onsuccess: #939: 1: Success after binutils/gcc/linux/ [...] new 2318188ddad0 147: onsuccess: #940: 1: Success after binutils/gcc/linux/ [...] new 2a2f4198f703 148: onsuccess: #941: 1: Success after binutils/gcc/linux/ [...] new f4a4dcee7c1b 149: onsuccess: #942: 1: Success after binutils/gcc/linux/ [...] new 1f06d5c71662 150: onsuccess: #943: 1: Success after binutils/gcc/linux/ [...] new acbc3f59ed64 151: onsuccess: #944: 1: Success after binutils/gcc/linux/ [...] new 25377e2150dc 152: onsuccess: #945: 1: Success after binutils/gcc/linux/ [...] new fd8a3d7bf034 153: onsuccess: #946: 1: Success after binutils/gcc/linux/ [...] new 30e3dc10e2fe 154: onsuccess: #947: 1: Success after binutils/gcc/linux/ [...] new 0f5d73d7d80d 155: onsuccess: #948: 1: Success after binutils/gcc/linux/ [...] new b57d1084bf9a 156: onsuccess: #949: 1: Success after binutils/gcc/linux/ [...] new 467aab023ed6 157: onsuccess: #950: 1: Success after binutils/gcc/linux/ [...] new db63f6a05b46 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new b6510d37c01b 159: onsuccess: #952: 1: Success after binutils/gcc/linux/ [...] new 64fc3c3cfd82 160: onsuccess: #953: 1: Success after binutils/gcc/linux/ [...] new 142a37720305 161: onsuccess: #954: 1: Success after binutils/gcc/linux/ [...] new ef580b0dc143 162: onsuccess: #955: 1: Success after binutils/gcc/linux/ [...] new 84f809372f47 163: onsuccess: #956: 1: Success after binutils/gcc/linux/ [...] new ca7c59dc0241 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/ [...] new 2b04426dbad6 165: onsuccess: #958: 1: Success after binutils/gcc/linux/ [...] new 3bc37d9eb430 166: onsuccess: #959: 1: Success after binutils/gcc/linux/ [...] new acfba0e75a1f 167: onsuccess: #960: 1: Success after binutils/gcc/linux/ [...] new 593c61a25bb4 168: onsuccess: #961: 1: Success after binutils/gcc/linux/ [...] new 6ab4df1c8a7e 169: onsuccess: #962: 1: Success after binutils/gcc/linux/ [...] new 3288ad6e688f 170: onsuccess: #963: 1: Success after binutils/gcc/linux/ [...] new 92a220a40a0c 171: onsuccess: #964: 1: Success after binutils/gcc/linux/ [...] new 8a1e2de5f474 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/ [...] new aa355fff9fbf 173: onsuccess: #966: 1: Success after binutils/gcc/linux/ [...] new 76604b58a277 174: onsuccess: #967: 1: Success after binutils/gcc/linux/ [...] new 7fd8284ce401 175: onsuccess: #968: 1: Success after binutils/gcc/linux/ [...] new 754fe94735cf 176: onsuccess: #969: 1: Success after binutils/gcc/linux/ [...] new c018bbdf3ed8 177: onsuccess: #970: 1: Success after binutils/gcc/linux/ [...] new 1eaaed76b73a 178: onsuccess: #971: 1: Success after binutils/gcc/linux/ [...] new e9c535d45a4e 179: onsuccess: #972: 1: Success after binutils/gcc/linux/ [...] new e9d69d6bf168 180: onsuccess: #973: 1: Success after binutils/gcc/linux/ [...] new a3e1c8718f78 181: onsuccess: #974: 1: Success after binutils/gcc/linux/ [...] new ae5bdc7659fb 182: onsuccess: #975: 1: Success after binutils/gcc/linux/ [...] new d0a067a867d2 183: onsuccess: #976: 1: Success after binutils/gcc/linux/ [...] new d9b56a44511b 184: onsuccess: #977: 1: Success after binutils/gcc/linux/ [...] new b62b065244f2 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 8ebca2e67458 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new 66f848c93fe2 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 78e3f2a5cc0d 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new 721aeaba8c58 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new d344e1115c23 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 156c218f7954 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 21d84496d91f 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new e64f0cb64e9d 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 05c10a286b53 194: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 138b986040d0 195: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 670f83a771b4 196: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 950ec8de1fcb 197: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 995518a3bb84 198: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new f0104cbe4a69 199: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new bb8955f7a91c 200: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 45283501aa9c 201: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new ec6808631140 202: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 4efc97ac73c0 203: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new ec0f0442b501 204: force: #26: : Failure after baseline build: no new commits new 8c2481913d05 205: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 77649fe05a7d 206: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 0c9d2d61149a 207: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 6f1e0a1f7a84 208: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new ec830d3b00ef 209: force: #37: 1: Success after baseline build: no new commits new e8a571f66e92 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181- [...] new 6d7ca1c5c2f7 211: onsuccess: #44: 1: Success after linux: 26 commits new 788310605013 212: force: #45: 1: Success after gdb: 22 commits new 8e001561b6c9 213: force: #46: 1: Success after gdb-13-branchpoint-1550- [...] new 5020af92f8ba 214: onsuccess: #47: 1: Success after gdb: 21 commits new deeb0d72e87e 215: onsuccess: #48: 1: Success after binutils/gcc/linux/g [...] new 5ae192febcda 216: onsuccess: #52: 1: Success after binutils/gcc/linux/g [...] new 91c3ef5223a8 217: onsuccess: #53: 1: Success after binutils/gcc/linux/g [...] new 36ae1f833b14 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/g [...] new 20b646bf20bd 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new f51fd1a03090 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchp [...] new 1574918dce63 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 6131c08731dc 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/g [...] new f5bb0a70fe07 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new d10e2a4b74ca 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchp [...] new d2f67294b933 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new da51112bcbc7 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new 8af3d4ab54e1 227: force: #81: 1: [TCWG CI] Failure after baseline build [...] new 8942b13eba22 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new 87cc37e1afad 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.900 [...] new 076cacf75103 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37 [...] new 9347f0b1a6f6 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/g [...] new 6d048737fa96 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new 0fd1839b1824 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: [...] new 57d60b2253cc 234: force: #94: 1: [TCWG CI] Success after baseline build [...]

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 (c98fd389ca21) \ 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 2000 -> 2204 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2532 bytes 03-build_abe-binutils/console.log.xz | Bin 35204 -> 35292 bytes 04-build_abe-gcc/console.log.xz | Bin 204820 -> 204000 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9004 -> 9028 bytes 07-build_abe-glibc/console.log.xz | Bin 241200 -> 241236 bytes 08-build_abe-gdb/console.log.xz | Bin 34688 -> 34744 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3788 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2604 -> 2656 bytes 11-check_regression/console.log.xz | Bin 3796 -> 2464 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 102 +- 12-update_baseline/console.log | 48 +- dashboard/dashboard-generate.sh | 2 +- mail/changes-list-long.txt | 4 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 20 +- manifest.sh | 15 +- sumfiles/gdb.log.0.xz | Bin 2026176 -> 1945556 bytes sumfiles/gdb.log.1.xz | Bin 30048 -> 21948 bytes sumfiles/gdb.log.2.xz | Bin 14636 -> 5504 bytes sumfiles/gdb.log.3.xz | Bin 0 -> 5424 bytes sumfiles/gdb.sum | 1683 ++++++++++++++++++-------------- sumfiles/gdb.sum.0 | 1688 +++++++++++++++++++-------------- sumfiles/gdb.sum.1 | 340 +++++-- sumfiles/gdb.sum.2 | 268 ++++-- sumfiles/gdb.sum.3 | 182 ++++ 28 files changed, 2628 insertions(+), 1730 deletions(-) create mode 100644 sumfiles/gdb.log.3.xz create mode 100644 sumfiles/gdb.sum.3