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 6e16a0c5ae9a 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/g [...] discards f767148c6a43 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/g [...] discards d4c77ecffa08 234: force: #94: 1: [TCWG CI] Success after baseline build [...] discards bcc199e0b340 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: [...] discards a96bc37a26a1 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 4a06b72159db 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/g [...] discards d21309e8d8b4 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37 [...] discards 3134a36cfdc0 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.900 [...] discards 91c264b68b25 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards 69c5d8b8638f 227: force: #81: 1: [TCWG CI] Failure after baseline build [...] discards 9dfd45abe648 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards 5964d2f8e5ae 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards e878340d42f9 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards 112637f2d729 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 072ccbde903d 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/g [...] discards 9c3a9c475db7 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards 82c1cafb569f 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards b6dada9b1f27 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards df63e9a01fdf 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/g [...] discards 63bc32a7b412 217: onsuccess: #53: 1: Success after binutils/gcc/linux/g [...] discards 275a6828ff1b 216: onsuccess: #52: 1: Success after binutils/gcc/linux/g [...] discards 2baffc466b64 215: onsuccess: #48: 1: Success after binutils/gcc/linux/g [...] discards 79cb04dab611 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 053e96400101 213: force: #46: 1: Success after gdb-13-branchpoint-1550- [...] discards 98a9b9152e1a 212: force: #45: 1: Success after gdb: 22 commits discards 51739bc9116f 211: onsuccess: #44: 1: Success after linux: 26 commits discards fc292ed25e32 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181- [...] discards 9e8fd89f8c57 209: force: #37: 1: Success after baseline build: no new commits discards 6fc809a20040 208: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards d5dcd8a338d8 207: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 619bef30c061 206: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 06d83793098f 205: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards 16217980fa82 204: force: #26: : Failure after baseline build: no new commits discards 4f09261b45c4 203: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards bc3fc1f6ba9e 202: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards cc7c3713b17c 201: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards fb07b752eeab 200: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 95f821b394e7 199: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 965fcd78ece5 198: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 1736d67da52d 197: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards d72c480e025b 196: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards 6e4fb6ce36bc 195: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 88a404323c34 194: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards bdc15f4263b2 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards a4cc9284caed 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 2ab11aa6d616 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards 62e1ec9f668b 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 7ab0e367f17f 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 878efac431a3 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards 7ef01c067d14 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 8f82b665d301 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards b43282a46c54 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 786a80e0f3e1 184: onsuccess: #977: 1: Success after binutils/gcc/linux/ [...] discards cc3377daf74c 183: onsuccess: #976: 1: Success after binutils/gcc/linux/ [...] discards 67047d7f52bf 182: onsuccess: #975: 1: Success after binutils/gcc/linux/ [...] discards 349feb01763e 181: onsuccess: #974: 1: Success after binutils/gcc/linux/ [...] discards 29f5da2fbea3 180: onsuccess: #973: 1: Success after binutils/gcc/linux/ [...] discards cb6083c3fe3e 179: onsuccess: #972: 1: Success after binutils/gcc/linux/ [...] discards a08561ce8a80 178: onsuccess: #971: 1: Success after binutils/gcc/linux/ [...] discards f64bfdd3d677 177: onsuccess: #970: 1: Success after binutils/gcc/linux/ [...] discards f3c3f7a3fdc5 176: onsuccess: #969: 1: Success after binutils/gcc/linux/ [...] discards ce9ff2635805 175: onsuccess: #968: 1: Success after binutils/gcc/linux/ [...] discards 9ea8d34b99af 174: onsuccess: #967: 1: Success after binutils/gcc/linux/ [...] discards 972e5db252f9 173: onsuccess: #966: 1: Success after binutils/gcc/linux/ [...] discards b5ef4512ecf5 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/ [...] discards a8c5d4232f35 171: onsuccess: #964: 1: Success after binutils/gcc/linux/ [...] discards 00ef547b2c36 170: onsuccess: #963: 1: Success after binutils/gcc/linux/ [...] discards 76ae7afd1ddc 169: onsuccess: #962: 1: Success after binutils/gcc/linux/ [...] discards 937daf1117ac 168: onsuccess: #961: 1: Success after binutils/gcc/linux/ [...] discards 982b967067db 167: onsuccess: #960: 1: Success after binutils/gcc/linux/ [...] discards 1ca9ceb4e4ae 166: onsuccess: #959: 1: Success after binutils/gcc/linux/ [...] discards 069683e4498d 165: onsuccess: #958: 1: Success after binutils/gcc/linux/ [...] discards 45c45215bf99 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/ [...] discards f1b572c4c52b 163: onsuccess: #956: 1: Success after binutils/gcc/linux/ [...] discards 81f925d0e936 162: onsuccess: #955: 1: Success after binutils/gcc/linux/ [...] discards bd6284753086 161: onsuccess: #954: 1: Success after binutils/gcc/linux/ [...] discards b6f524c1a596 160: onsuccess: #953: 1: Success after binutils/gcc/linux/ [...] discards 7258c1510e4f 159: onsuccess: #952: 1: Success after binutils/gcc/linux/ [...] discards c28f58796def 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 042b33a826da 157: onsuccess: #950: 1: Success after binutils/gcc/linux/ [...] discards ec7a9a4eb8af 156: onsuccess: #949: 1: Success after binutils/gcc/linux/ [...] discards 79ca5de0f6bf 155: onsuccess: #948: 1: Success after binutils/gcc/linux/ [...] discards 9e4492453e97 154: onsuccess: #947: 1: Success after binutils/gcc/linux/ [...] discards dc256db6641b 153: onsuccess: #946: 1: Success after binutils/gcc/linux/ [...] discards 88473bb22ceb 152: onsuccess: #945: 1: Success after binutils/gcc/linux/ [...] discards a3556b7caa96 151: onsuccess: #944: 1: Success after binutils/gcc/linux/ [...] discards d43baaae3616 150: onsuccess: #943: 1: Success after binutils/gcc/linux/ [...] discards 5f5797ff2895 149: onsuccess: #942: 1: Success after binutils/gcc/linux/ [...] discards 38a8c4de725a 148: onsuccess: #941: 1: Success after binutils/gcc/linux/ [...] discards f0853d0fb0df 147: onsuccess: #940: 1: Success after binutils/gcc/linux/ [...] discards 108c429fb0b3 146: onsuccess: #939: 1: Success after binutils/gcc/linux/ [...] discards 2ff36ca6c6ab 145: onsuccess: #934: 1: Success after binutils/gcc/linux/ [...] discards 8068528e31aa 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/ [...] discards 9d51de97b3e4 143: onsuccess: #931: 1: Success after binutils/gcc/linux/ [...] discards 7b764ce15fd1 142: onsuccess: #929: 1: Success after binutils/gcc/linux/ [...] discards dbbeb47c336b 141: onsuccess: #928: 1: Success after binutils/gcc/linux/ [...] discards fc8f25014902 140: onsuccess: #927: 1: Success after binutils/gcc/linux/ [...] discards 52d5e20f1f24 139: onsuccess: #926: 1: Success after binutils/gcc/linux/ [...] discards 21b126541551 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 1 [...] discards 8de4608dcd1f 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 4 [...] discards 86b0aeddf172 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 1 [...] new a474538ceb21 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 1 [...] new 249efbe9f644 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 4 [...] new f1ed012a44ea 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 1 [...] new 995f3a90e75a 139: onsuccess: #926: 1: Success after binutils/gcc/linux/ [...] new 0f7013e70c24 140: onsuccess: #927: 1: Success after binutils/gcc/linux/ [...] new 2e538c0ed722 141: onsuccess: #928: 1: Success after binutils/gcc/linux/ [...] new b6e6bd85aa1f 142: onsuccess: #929: 1: Success after binutils/gcc/linux/ [...] new 49f810882da7 143: onsuccess: #931: 1: Success after binutils/gcc/linux/ [...] new dc5842479fc8 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/ [...] new 6a852d30b7e2 145: onsuccess: #934: 1: Success after binutils/gcc/linux/ [...] new c06c05e091e5 146: onsuccess: #939: 1: Success after binutils/gcc/linux/ [...] new 063c0b836377 147: onsuccess: #940: 1: Success after binutils/gcc/linux/ [...] new 01500897af40 148: onsuccess: #941: 1: Success after binutils/gcc/linux/ [...] new 9d8c73932f19 149: onsuccess: #942: 1: Success after binutils/gcc/linux/ [...] new cf353bd028a6 150: onsuccess: #943: 1: Success after binutils/gcc/linux/ [...] new ec3b856d4c2b 151: onsuccess: #944: 1: Success after binutils/gcc/linux/ [...] new c3a2ea89b2ba 152: onsuccess: #945: 1: Success after binutils/gcc/linux/ [...] new d002454a153f 153: onsuccess: #946: 1: Success after binutils/gcc/linux/ [...] new a5bdee97604a 154: onsuccess: #947: 1: Success after binutils/gcc/linux/ [...] new 70a4f7bca928 155: onsuccess: #948: 1: Success after binutils/gcc/linux/ [...] new dc12911e6514 156: onsuccess: #949: 1: Success after binutils/gcc/linux/ [...] new 1187c4e89342 157: onsuccess: #950: 1: Success after binutils/gcc/linux/ [...] new 1ddc95566a1f 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new d4074d8bac81 159: onsuccess: #952: 1: Success after binutils/gcc/linux/ [...] new 199ec543de3e 160: onsuccess: #953: 1: Success after binutils/gcc/linux/ [...] new 22be7a7300fa 161: onsuccess: #954: 1: Success after binutils/gcc/linux/ [...] new 3a11deffe893 162: onsuccess: #955: 1: Success after binutils/gcc/linux/ [...] new 95274a10160f 163: onsuccess: #956: 1: Success after binutils/gcc/linux/ [...] new 48dc5cee30e3 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/ [...] new 2663fc965f6c 165: onsuccess: #958: 1: Success after binutils/gcc/linux/ [...] new 8dc7741ddf8b 166: onsuccess: #959: 1: Success after binutils/gcc/linux/ [...] new 5f0be6a8d9dc 167: onsuccess: #960: 1: Success after binutils/gcc/linux/ [...] new eaeb40cd481a 168: onsuccess: #961: 1: Success after binutils/gcc/linux/ [...] new a8c326fc18d6 169: onsuccess: #962: 1: Success after binutils/gcc/linux/ [...] new e4c12aa73c7a 170: onsuccess: #963: 1: Success after binutils/gcc/linux/ [...] new 7c6abda0a61d 171: onsuccess: #964: 1: Success after binutils/gcc/linux/ [...] new 964bb94da074 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/ [...] new efcb82940433 173: onsuccess: #966: 1: Success after binutils/gcc/linux/ [...] new 39f72e8f291e 174: onsuccess: #967: 1: Success after binutils/gcc/linux/ [...] new 39fb1db0cb88 175: onsuccess: #968: 1: Success after binutils/gcc/linux/ [...] new 58fd837665c6 176: onsuccess: #969: 1: Success after binutils/gcc/linux/ [...] new d1ffb8810393 177: onsuccess: #970: 1: Success after binutils/gcc/linux/ [...] new 6e0695ead8dc 178: onsuccess: #971: 1: Success after binutils/gcc/linux/ [...] new d6315651d60f 179: onsuccess: #972: 1: Success after binutils/gcc/linux/ [...] new 0f19587a522e 180: onsuccess: #973: 1: Success after binutils/gcc/linux/ [...] new 0292c40ad33c 181: onsuccess: #974: 1: Success after binutils/gcc/linux/ [...] new 58c84115eefb 182: onsuccess: #975: 1: Success after binutils/gcc/linux/ [...] new e679f0d8c94c 183: onsuccess: #976: 1: Success after binutils/gcc/linux/ [...] new 087646c24bfc 184: onsuccess: #977: 1: Success after binutils/gcc/linux/ [...] new fe489f8db23b 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new d84954df095c 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new f5ec329303b7 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new bdc2c3e9dbcf 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new 8bfc75df3b7e 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 9f8521abd557 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new b7f11223223c 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 8c106ab5e3c3 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new c560d87bf195 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 387626665585 194: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 7a6a67151a95 195: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 22c81a4d60b4 196: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new be64a00385c9 197: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 2bcf48ef9298 198: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 72e6c70f9d2f 199: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new b2ae3330df72 200: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 54fd421287fc 201: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new f3e40b92229d 202: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 3a779e836114 203: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 7f392c74c233 204: force: #26: : Failure after baseline build: no new commits new d5a2480bad15 205: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new b2ccfc414700 206: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 432d2290ec37 207: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 63d3c50e88d8 208: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new f8746e5bc78a 209: force: #37: 1: Success after baseline build: no new commits new f489e320a725 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181- [...] new 0a282bfac61d 211: onsuccess: #44: 1: Success after linux: 26 commits new 05e3631b6ffd 212: force: #45: 1: Success after gdb: 22 commits new aa192e1f9c26 213: force: #46: 1: Success after gdb-13-branchpoint-1550- [...] new e278c7d1403e 214: onsuccess: #47: 1: Success after gdb: 21 commits new 193cbf2cc384 215: onsuccess: #48: 1: Success after binutils/gcc/linux/g [...] new 922841760bce 216: onsuccess: #52: 1: Success after binutils/gcc/linux/g [...] new 8f965e276945 217: onsuccess: #53: 1: Success after binutils/gcc/linux/g [...] new 9ed828c95395 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/g [...] new 7cc3d9acc8f4 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 0df4927ea469 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchp [...] new 7ce08e9bdfd6 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 1205134bf619 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/g [...] new c5fce1522f52 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new a424f71ff862 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchp [...] new 05cbd2c9cd12 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new f1ee83d2f7f2 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new ab79fd752635 227: force: #81: 1: [TCWG CI] Failure after baseline build [...] new 6b331b0e4362 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new cf781935fa51 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.900 [...] new 4c7585e78ff3 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37 [...] new 7f1547871b4d 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/g [...] new 6356859df22e 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new 7c49b63b841b 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: [...] new 547fa75f373f 234: force: #94: 1: [TCWG CI] Success after baseline build [...] new 9c93e83209f2 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/g [...] new 900b38c6bad5 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/g [...] new f17dde660405 237: onsuccess: #97: 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 (6e16a0c5ae9a) \ 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 2032 -> 2048 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 35560 -> 34972 bytes 04-build_abe-gcc/console.log.xz | Bin 203232 -> 203544 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8704 -> 8688 bytes 07-build_abe-glibc/console.log.xz | Bin 241528 -> 240700 bytes 08-build_abe-gdb/console.log.xz | Bin 35336 -> 34808 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3784 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3240 -> 2712 bytes 11-check_regression/console.log.xz | Bin 6160 -> 5360 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 147 +++++++++------------------------- 12-update_baseline/console.log | 68 ++++++++-------- 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 | 57 +++++++------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 ++++----- manifest.sh | 38 ++++----- sumfiles/gdb.log.0.xz | Bin 1922600 -> 1992236 bytes sumfiles/gdb.log.1.xz | Bin 16780 -> 30208 bytes sumfiles/gdb.sum | 28 +++---- sumfiles/gdb.sum.0 | 24 +++--- sumfiles/gdb.sum.1 | 103 ++++++++++++++++++++++-- 29 files changed, 267 insertions(+), 254 deletions(-)