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 f17dde6604 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards 900b38c6ba 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards 9c93e83209 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 547fa75f37 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 7c49b63b84 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards 6356859df2 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 7f1547871b 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards 4c7585e78f 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards cf781935fa 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards 6b331b0e43 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards ab79fd7526 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards f1ee83d2f7 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards 05cbd2c9cd 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards a424f71ff8 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards c5fce1522f 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 1205134bf6 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards 7ce08e9bdf 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards 0df4927ea4 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 7cc3d9acc8 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 9ed828c953 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards 8f965e2769 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards 922841760b 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards 193cbf2cc3 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards e278c7d140 214: onsuccess: #47: 1: Success after gdb: 21 commits discards aa192e1f9c 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards 05e3631b6f 212: force: #45: 1: Success after gdb: 22 commits discards 0a282bfac6 211: onsuccess: #44: 1: Success after linux: 26 commits discards f489e320a7 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards f8746e5bc7 209: force: #37: 1: Success after baseline build: no new commits discards 63d3c50e88 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 432d2290ec 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards b2ccfc4147 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards d5a2480bad 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 7f392c74c2 204: force: #26: : Failure after baseline build: no new commits discards 3a779e8361 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards f3e40b9222 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 54fd421287 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards b2ae3330df 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 72e6c70f9d 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 2bcf48ef92 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards be64a00385 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 22c81a4d60 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 7a6a67151a 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 3876266655 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards c560d87bf1 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 8c106ab5e3 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards b7f1122322 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 9f8521abd5 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 8bfc75df3b 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards bdc2c3e9db 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards f5ec329303 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards d84954df09 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards fe489f8db2 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 087646c24b 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards e679f0d8c9 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards 58c84115ee 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards 0292c40ad3 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards 0f19587a52 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards d6315651d6 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards 6e0695ead8 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards d1ffb88103 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards 58fd837665 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards 39fb1db0cb 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards 39f72e8f29 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards efcb829404 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards 964bb94da0 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards 7c6abda0a6 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards e4c12aa73c 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards a8c326fc18 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards eaeb40cd48 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards 5f0be6a8d9 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards 8dc7741ddf 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards 2663fc965f 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards 48dc5cee30 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards 95274a1016 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards 3a11deffe8 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards 22be7a7300 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards 199ec543de 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards d4074d8bac 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards 1ddc95566a 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 1187c4e893 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards dc12911e65 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards 70a4f7bca9 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards a5bdee9760 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards d002454a15 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards c3a2ea89b2 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards ec3b856d4c 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards cf353bd028 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards 9d8c73932f 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards 01500897af 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards 063c0b8363 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards c06c05e091 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards 6a852d30b7 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards dc5842479f 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards 49f810882d 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards b6e6bd85aa 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards 2e538c0ed7 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards 0f7013e70c 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards 995f3a90e7 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards f1ed012a44 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards 249efbe9f6 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new b600265f80 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new ce08911873 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new 5e27a90085 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new 75068346e5 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new bdf7c89d6a 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new 259f2d6d96 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new 88bc15c2cf 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new cc12614154 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new 6e63138e82 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new a6dba53d49 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 7172d78386 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new 3a8165c0fe 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new 3ba07c232f 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new 56ac12edab 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new 1956cb2aa2 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 7271ab62af 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new e75431eb4d 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new 4cd20da155 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 6982379e33 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new bcf6399eed 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new 16ee7dce84 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new 14e3deeec8 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new b3f1486c7b 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new 1986e624b8 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new 2db854c4f3 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 2fd10dc68a 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new 1a0e437cda 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new db56c82d26 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new fec9376373 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new 335d1448d0 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new b315efc786 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new 655ccd88db 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new 48c8e6e6e4 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new d17ad3bd50 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new b9194ff93b 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new 590d9be5b6 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 769a79086f 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new fb0690f16a 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new dd8b94cb65 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new 7e1fd0d2f2 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new 5c19311a60 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new 0115e0b985 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new 3283059b52 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new 4e277ab64c 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new ea7b9d5461 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new 643a35afb5 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new ef01219d55 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new 50c525f775 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new adeed98b46 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new b44d630df2 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 0efe95ae22 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 3e0267cd65 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 68a0b68dff 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new d64cd70806 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new ab48ef9e3a 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new b2a48e8f11 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 2a71668f19 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 4d6688f45d 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 5f85297a41 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new ce0d917d77 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new f0cca30f68 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 8c0c534b42 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new f254dd0d42 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new b2e40b2cab 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new b6a54aa490 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 2da610e251 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 9161f1bd4c 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new b6098ce170 204: force: #26: : Failure after baseline build: no new commits new 1afeac8908 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new c5e3496eb9 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 968c7d5011 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new fe5f4c9d0f 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 52e08173b5 209: force: #37: 1: Success after baseline build: no new commits new 4fb2860a79 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new e67187eec7 211: onsuccess: #44: 1: Success after linux: 26 commits new 3d919b884f 212: force: #45: 1: Success after gdb: 22 commits new 7827a62315 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new 4097a3e827 214: onsuccess: #47: 1: Success after gdb: 21 commits new f3e1bdda88 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new 201bfa19d3 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new 5c1c8a229e 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new 6bdbd3eb12 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new 955bb3d1f9 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 5facca9f29 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 6afa0a4758 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 76a1c9f4e3 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new e65904114b 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 355b7f35ec 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new fd6c54b5f7 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new 19d22b87f3 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new d5f0f8e60c 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new 66ec1c200b 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new 09fdae1908 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new cc22bb38dc 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new c2524d6615 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new a328a1fef1 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new 944cfaa307 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new ecd6c25104 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 27d57b649f 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new 19bc4e5593 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new 190c4fcdba 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new 90dd4d8a0f 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits
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 (f17dde6604) \ 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 2048 -> 2040 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 34972 -> 35204 bytes 04-build_abe-gcc/console.log.xz | Bin 203544 -> 203700 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8688 -> 8892 bytes 07-build_abe-glibc/console.log.xz | Bin 240700 -> 240900 bytes 08-build_abe-gdb/console.log.xz | Bin 34808 -> 34940 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3824 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2712 -> 3004 bytes 11-check_regression/console.log.xz | Bin 5360 -> 4356 bytes 11-check_regression/results.compare | 28 ++++++++- 11-check_regression/results.compare2 | 107 +++++++++++++++++++++++----------- 12-update_baseline/console.log | 68 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- mail/changes-list-long.txt | 36 +++--------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 ++++++------ manifest.sh | 28 ++++----- sumfiles/gdb.log.0.xz | Bin 1992236 -> 2037736 bytes sumfiles/gdb.log.1.xz | Bin 30208 -> 27580 bytes sumfiles/gdb.sum | 47 ++++++++------- sumfiles/gdb.sum.0 | 47 +++++++-------- sumfiles/gdb.sum.1 | 60 +++++-------------- 25 files changed, 237 insertions(+), 228 deletions(-)