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 57d60b2253cc 234: force: #94: 1: [TCWG CI] Success after baseline build [...] discards 0fd1839b1824 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: [...] discards 6d048737fa96 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 9347f0b1a6f6 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/g [...] discards 076cacf75103 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37 [...] discards 87cc37e1afad 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.900 [...] discards 8942b13eba22 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards 8af3d4ab54e1 227: force: #81: 1: [TCWG CI] Failure after baseline build [...] discards da51112bcbc7 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards d2f67294b933 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards d10e2a4b74ca 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards f5bb0a70fe07 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 6131c08731dc 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/g [...] discards 1574918dce63 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards f51fd1a03090 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards 20b646bf20bd 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 36ae1f833b14 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/g [...] discards 91c3ef5223a8 217: onsuccess: #53: 1: Success after binutils/gcc/linux/g [...] discards 5ae192febcda 216: onsuccess: #52: 1: Success after binutils/gcc/linux/g [...] discards deeb0d72e87e 215: onsuccess: #48: 1: Success after binutils/gcc/linux/g [...] discards 5020af92f8ba 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 8e001561b6c9 213: force: #46: 1: Success after gdb-13-branchpoint-1550- [...] discards 788310605013 212: force: #45: 1: Success after gdb: 22 commits discards 6d7ca1c5c2f7 211: onsuccess: #44: 1: Success after linux: 26 commits discards e8a571f66e92 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181- [...] discards ec830d3b00ef 209: force: #37: 1: Success after baseline build: no new commits discards 6f1e0a1f7a84 208: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards 0c9d2d61149a 207: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 77649fe05a7d 206: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 8c2481913d05 205: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards ec0f0442b501 204: force: #26: : Failure after baseline build: no new commits discards 4efc97ac73c0 203: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards ec6808631140 202: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 45283501aa9c 201: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards bb8955f7a91c 200: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards f0104cbe4a69 199: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 995518a3bb84 198: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 950ec8de1fcb 197: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards 670f83a771b4 196: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards 138b986040d0 195: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 05c10a286b53 194: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards e64f0cb64e9d 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 21d84496d91f 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 156c218f7954 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards d344e1115c23 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 721aeaba8c58 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 78e3f2a5cc0d 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards 66f848c93fe2 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 8ebca2e67458 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards b62b065244f2 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards d9b56a44511b 184: onsuccess: #977: 1: Success after binutils/gcc/linux/ [...] discards d0a067a867d2 183: onsuccess: #976: 1: Success after binutils/gcc/linux/ [...] discards ae5bdc7659fb 182: onsuccess: #975: 1: Success after binutils/gcc/linux/ [...] discards a3e1c8718f78 181: onsuccess: #974: 1: Success after binutils/gcc/linux/ [...] discards e9d69d6bf168 180: onsuccess: #973: 1: Success after binutils/gcc/linux/ [...] discards e9c535d45a4e 179: onsuccess: #972: 1: Success after binutils/gcc/linux/ [...] discards 1eaaed76b73a 178: onsuccess: #971: 1: Success after binutils/gcc/linux/ [...] discards c018bbdf3ed8 177: onsuccess: #970: 1: Success after binutils/gcc/linux/ [...] discards 754fe94735cf 176: onsuccess: #969: 1: Success after binutils/gcc/linux/ [...] discards 7fd8284ce401 175: onsuccess: #968: 1: Success after binutils/gcc/linux/ [...] discards 76604b58a277 174: onsuccess: #967: 1: Success after binutils/gcc/linux/ [...] discards aa355fff9fbf 173: onsuccess: #966: 1: Success after binutils/gcc/linux/ [...] discards 8a1e2de5f474 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/ [...] discards 92a220a40a0c 171: onsuccess: #964: 1: Success after binutils/gcc/linux/ [...] discards 3288ad6e688f 170: onsuccess: #963: 1: Success after binutils/gcc/linux/ [...] discards 6ab4df1c8a7e 169: onsuccess: #962: 1: Success after binutils/gcc/linux/ [...] discards 593c61a25bb4 168: onsuccess: #961: 1: Success after binutils/gcc/linux/ [...] discards acfba0e75a1f 167: onsuccess: #960: 1: Success after binutils/gcc/linux/ [...] discards 3bc37d9eb430 166: onsuccess: #959: 1: Success after binutils/gcc/linux/ [...] discards 2b04426dbad6 165: onsuccess: #958: 1: Success after binutils/gcc/linux/ [...] discards ca7c59dc0241 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/ [...] discards 84f809372f47 163: onsuccess: #956: 1: Success after binutils/gcc/linux/ [...] discards ef580b0dc143 162: onsuccess: #955: 1: Success after binutils/gcc/linux/ [...] discards 142a37720305 161: onsuccess: #954: 1: Success after binutils/gcc/linux/ [...] discards 64fc3c3cfd82 160: onsuccess: #953: 1: Success after binutils/gcc/linux/ [...] discards b6510d37c01b 159: onsuccess: #952: 1: Success after binutils/gcc/linux/ [...] discards db63f6a05b46 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 467aab023ed6 157: onsuccess: #950: 1: Success after binutils/gcc/linux/ [...] discards b57d1084bf9a 156: onsuccess: #949: 1: Success after binutils/gcc/linux/ [...] discards 0f5d73d7d80d 155: onsuccess: #948: 1: Success after binutils/gcc/linux/ [...] discards 30e3dc10e2fe 154: onsuccess: #947: 1: Success after binutils/gcc/linux/ [...] discards fd8a3d7bf034 153: onsuccess: #946: 1: Success after binutils/gcc/linux/ [...] discards 25377e2150dc 152: onsuccess: #945: 1: Success after binutils/gcc/linux/ [...] discards acbc3f59ed64 151: onsuccess: #944: 1: Success after binutils/gcc/linux/ [...] discards 1f06d5c71662 150: onsuccess: #943: 1: Success after binutils/gcc/linux/ [...] discards f4a4dcee7c1b 149: onsuccess: #942: 1: Success after binutils/gcc/linux/ [...] discards 2a2f4198f703 148: onsuccess: #941: 1: Success after binutils/gcc/linux/ [...] discards 2318188ddad0 147: onsuccess: #940: 1: Success after binutils/gcc/linux/ [...] discards d191f7f2d6b5 146: onsuccess: #939: 1: Success after binutils/gcc/linux/ [...] discards dc600b50fb03 145: onsuccess: #934: 1: Success after binutils/gcc/linux/ [...] discards 09da31a1ed6c 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/ [...] discards a9d48882192e 143: onsuccess: #931: 1: Success after binutils/gcc/linux/ [...] discards be565b73d940 142: onsuccess: #929: 1: Success after binutils/gcc/linux/ [...] discards ba5582e30ee6 141: onsuccess: #928: 1: Success after binutils/gcc/linux/ [...] discards 8ee89a22fc97 140: onsuccess: #927: 1: Success after binutils/gcc/linux/ [...] discards bce1dedaf3ec 139: onsuccess: #926: 1: Success after binutils/gcc/linux/ [...] discards 7705d02482a8 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 1 [...] discards 56827f87c11c 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 4 [...] discards ba505518abc5 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 1 [...] discards 11b9acb73606 135: onsuccess: #922: 1: Success after binutils/gcc/linux/ [...] discards 88b3dc6ca123 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 2 [...] new 056ff688466d 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 2 [...] new 9bc5d86bcbac 135: onsuccess: #922: 1: Success after binutils/gcc/linux/ [...] new 7b2216d3f901 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 1 [...] new 87c7393a66ef 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 4 [...] new 4f1667c62bdd 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 1 [...] new db1764c16160 139: onsuccess: #926: 1: Success after binutils/gcc/linux/ [...] new d0d2e67b9663 140: onsuccess: #927: 1: Success after binutils/gcc/linux/ [...] new 9d235596773d 141: onsuccess: #928: 1: Success after binutils/gcc/linux/ [...] new c2d2ad34d574 142: onsuccess: #929: 1: Success after binutils/gcc/linux/ [...] new e951af118590 143: onsuccess: #931: 1: Success after binutils/gcc/linux/ [...] new f241d2b47f65 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/ [...] new fbd105345734 145: onsuccess: #934: 1: Success after binutils/gcc/linux/ [...] new f094bdf9fdbd 146: onsuccess: #939: 1: Success after binutils/gcc/linux/ [...] new a17ae2f4fd29 147: onsuccess: #940: 1: Success after binutils/gcc/linux/ [...] new 3ef7ecfe3bd1 148: onsuccess: #941: 1: Success after binutils/gcc/linux/ [...] new 488392ddd3ef 149: onsuccess: #942: 1: Success after binutils/gcc/linux/ [...] new 27e003e0fe76 150: onsuccess: #943: 1: Success after binutils/gcc/linux/ [...] new 421f62cee5e6 151: onsuccess: #944: 1: Success after binutils/gcc/linux/ [...] new aa803cd8742e 152: onsuccess: #945: 1: Success after binutils/gcc/linux/ [...] new e30256f6583a 153: onsuccess: #946: 1: Success after binutils/gcc/linux/ [...] new 44698e752f91 154: onsuccess: #947: 1: Success after binutils/gcc/linux/ [...] new 17d61a18a123 155: onsuccess: #948: 1: Success after binutils/gcc/linux/ [...] new 4b9499b356bb 156: onsuccess: #949: 1: Success after binutils/gcc/linux/ [...] new 332760ab8716 157: onsuccess: #950: 1: Success after binutils/gcc/linux/ [...] new 7ee144797342 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new d45e2cbed91f 159: onsuccess: #952: 1: Success after binutils/gcc/linux/ [...] new 5ac70b0a8e25 160: onsuccess: #953: 1: Success after binutils/gcc/linux/ [...] new 720466e5a59a 161: onsuccess: #954: 1: Success after binutils/gcc/linux/ [...] new f47f08678528 162: onsuccess: #955: 1: Success after binutils/gcc/linux/ [...] new b1ddf1f326a7 163: onsuccess: #956: 1: Success after binutils/gcc/linux/ [...] new 1b3fb155263d 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/ [...] new c5cf20b87839 165: onsuccess: #958: 1: Success after binutils/gcc/linux/ [...] new 271a5c1a4568 166: onsuccess: #959: 1: Success after binutils/gcc/linux/ [...] new a5c88b8f56e2 167: onsuccess: #960: 1: Success after binutils/gcc/linux/ [...] new 736fb79b16fc 168: onsuccess: #961: 1: Success after binutils/gcc/linux/ [...] new 34a32beb0c5e 169: onsuccess: #962: 1: Success after binutils/gcc/linux/ [...] new 1e411f2c5926 170: onsuccess: #963: 1: Success after binutils/gcc/linux/ [...] new 98134668a253 171: onsuccess: #964: 1: Success after binutils/gcc/linux/ [...] new 289e3ea21360 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/ [...] new aadd9725f1a8 173: onsuccess: #966: 1: Success after binutils/gcc/linux/ [...] new 11a40691f9f4 174: onsuccess: #967: 1: Success after binutils/gcc/linux/ [...] new 695c6579edcf 175: onsuccess: #968: 1: Success after binutils/gcc/linux/ [...] new c5adbff9e5c2 176: onsuccess: #969: 1: Success after binutils/gcc/linux/ [...] new cc1e4bed03fd 177: onsuccess: #970: 1: Success after binutils/gcc/linux/ [...] new 4fcb1c0b9654 178: onsuccess: #971: 1: Success after binutils/gcc/linux/ [...] new 1f2b8a8a47e3 179: onsuccess: #972: 1: Success after binutils/gcc/linux/ [...] new a3e50228f977 180: onsuccess: #973: 1: Success after binutils/gcc/linux/ [...] new ba9183ba0dcd 181: onsuccess: #974: 1: Success after binutils/gcc/linux/ [...] new 62254330ae53 182: onsuccess: #975: 1: Success after binutils/gcc/linux/ [...] new e02f38065f66 183: onsuccess: #976: 1: Success after binutils/gcc/linux/ [...] new 20558ffb437b 184: onsuccess: #977: 1: Success after binutils/gcc/linux/ [...] new 1878d5fa2e09 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 1e94a01bfd2f 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new bb5431a934bd 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 0186d7239719 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new ff843a4cb463 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 28a1613ebe2e 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new d07b3bb9392f 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new ca14e99af674 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new fe81270fa339 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 14750a854ab9 194: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 0bf73d70b173 195: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 11c242871b73 196: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new f3e70145160f 197: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new a4673152f04d 198: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new fbc90c272ab0 199: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 51be66579246 200: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new f0831ff12d44 201: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 3a7314367641 202: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 351490b8e542 203: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 5cc39da57c6a 204: force: #26: : Failure after baseline build: no new commits new 80dce7490b6e 205: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 1c7b2ac30dea 206: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 99bbe784be69 207: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 67dfa58bc58f 208: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 5dc16be1cc6a 209: force: #37: 1: Success after baseline build: no new commits new 0cba3f6860ff 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181- [...] new d039d678b281 211: onsuccess: #44: 1: Success after linux: 26 commits new ad54eda600b7 212: force: #45: 1: Success after gdb: 22 commits new 80bb1edae2fa 213: force: #46: 1: Success after gdb-13-branchpoint-1550- [...] new b7e3663eb71f 214: onsuccess: #47: 1: Success after gdb: 21 commits new c855d7ce4d58 215: onsuccess: #48: 1: Success after binutils/gcc/linux/g [...] new c102cf204d39 216: onsuccess: #52: 1: Success after binutils/gcc/linux/g [...] new a1957bc79bc8 217: onsuccess: #53: 1: Success after binutils/gcc/linux/g [...] new 25cda42226f8 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/g [...] new 727dbb53ddd2 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new acd05c0022e9 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchp [...] new e36282ff20bb 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 00c0f63839cb 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/g [...] new 8e78ca121085 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 4cf2d1b0e119 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchp [...] new 91567ee9e86a 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new 266bc6187257 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new f8088ea932b5 227: force: #81: 1: [TCWG CI] Failure after baseline build [...] new abdda6074f15 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new a4ead46e74b7 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.900 [...] new 3d87449391b4 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37 [...] new 6649f8e79965 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/g [...] new 27f993a5c4bf 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new ff102b542010 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: [...] new 1101b98c3368 234: force: #94: 1: [TCWG CI] Success after baseline build [...] new 988d82de3371 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/g [...]

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 (57d60b2253cc) \ 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 2204 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2532 bytes 03-build_abe-binutils/console.log.xz | Bin 35292 -> 35444 bytes 04-build_abe-gcc/console.log.xz | Bin 204000 -> 203156 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9028 -> 8204 bytes 07-build_abe-glibc/console.log.xz | Bin 241236 -> 240808 bytes 08-build_abe-gdb/console.log.xz | Bin 34744 -> 35088 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3788 -> 3784 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2656 -> 3016 bytes 11-check_regression/console.log.xz | Bin 2464 -> 11324 bytes 11-check_regression/results.compare | 24 +- 11-check_regression/results.compare2 | 1072 ++++++++++++++++++++- 12-update_baseline/console.log | 72 +- 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 | 32 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 15 +- manifest.sh | 35 +- sumfiles/gdb.log.0.xz | Bin 1945556 -> 1983220 bytes sumfiles/gdb.log.1.xz | Bin 21948 -> 16780 bytes sumfiles/gdb.log.2.xz | Bin 5504 -> 0 bytes sumfiles/gdb.log.3.xz | Bin 5424 -> 0 bytes sumfiles/gdb.sum | 1700 ++++++++++++++------------------- sumfiles/gdb.sum.0 | 1700 ++++++++++++++------------------- sumfiles/gdb.sum.1 | 245 +---- sumfiles/gdb.sum.2 | 182 ---- sumfiles/gdb.sum.3 | 182 ---- 33 files changed, 2605 insertions(+), 2668 deletions(-) delete mode 100644 sumfiles/gdb.log.2.xz delete mode 100644 sumfiles/gdb.log.3.xz delete mode 100644 sumfiles/gdb.sum.2 delete mode 100644 sumfiles/gdb.sum.3