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 7ecc1574e85f 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.900 [...] discards 2b3e49de12a1 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards d8d8bcbef2d1 227: force: #81: 1: [TCWG CI] Failure after baseline build [...] discards 23b4c978eb03 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards 5a031576649d 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards 4693983d28e9 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards 839ffd04f3fd 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 1a80bc87a160 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/g [...] discards ee5e90389884 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards 6ce77e251927 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards 2be84e0c7414 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 8af88ee8df2b 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/g [...] discards e98c0e8748ad 217: onsuccess: #53: 1: Success after binutils/gcc/linux/g [...] discards 9685e5391f32 216: onsuccess: #52: 1: Success after binutils/gcc/linux/g [...] discards 1b9836f4da8e 215: onsuccess: #48: 1: Success after binutils/gcc/linux/g [...] discards 6053efd77ae3 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 42b4c98a2cb4 213: force: #46: 1: Success after gdb-13-branchpoint-1550- [...] discards 9d106def91ec 212: force: #45: 1: Success after gdb: 22 commits discards 5af530afb69e 211: onsuccess: #44: 1: Success after linux: 26 commits discards 79a26079be0b 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181- [...] discards 7fd204e3b71b 209: force: #37: 1: Success after baseline build: no new commits discards 2b97604b8cda 208: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards ada70eb46777 207: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 8d530a0421ad 206: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 3b8bd7ea5209 205: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards 2a8757120581 204: force: #26: : Failure after baseline build: no new commits discards c9e6a3537883 203: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 9f8d538c715f 202: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 30c5c636d427 201: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards a3a55313b5eb 200: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards f881a021feaf 199: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards adaff965424b 198: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 59f12fb10c0d 197: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards 05e9083f514c 196: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards ba04a9a2cdc2 195: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 83ca4de00c5c 194: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 990a27225eed 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 5ac0aa10f5a4 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 7c8032a5156a 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards 51ff15636cbf 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 3edd21631015 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 7f47352985a0 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards 0ca5adde29ae 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 5af33df8d140 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards 939068335f2a 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 543a4fd46cb4 184: onsuccess: #977: 1: Success after binutils/gcc/linux/ [...] discards 34afe9c6e5ab 183: onsuccess: #976: 1: Success after binutils/gcc/linux/ [...] discards 8a32f0884133 182: onsuccess: #975: 1: Success after binutils/gcc/linux/ [...] discards e5c782a23fb3 181: onsuccess: #974: 1: Success after binutils/gcc/linux/ [...] discards dd5b10edb04c 180: onsuccess: #973: 1: Success after binutils/gcc/linux/ [...] discards 03722e53aa40 179: onsuccess: #972: 1: Success after binutils/gcc/linux/ [...] discards c23a0b97d344 178: onsuccess: #971: 1: Success after binutils/gcc/linux/ [...] discards f891305674ac 177: onsuccess: #970: 1: Success after binutils/gcc/linux/ [...] discards e81959c49923 176: onsuccess: #969: 1: Success after binutils/gcc/linux/ [...] discards bf43b75a04a8 175: onsuccess: #968: 1: Success after binutils/gcc/linux/ [...] discards 18a0a1601a26 174: onsuccess: #967: 1: Success after binutils/gcc/linux/ [...] discards 686be765f250 173: onsuccess: #966: 1: Success after binutils/gcc/linux/ [...] discards 6629081f18e1 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/ [...] discards 8645035098a4 171: onsuccess: #964: 1: Success after binutils/gcc/linux/ [...] discards 5b2b0dd8e4eb 170: onsuccess: #963: 1: Success after binutils/gcc/linux/ [...] discards e8f5e4266e53 169: onsuccess: #962: 1: Success after binutils/gcc/linux/ [...] discards e55518160372 168: onsuccess: #961: 1: Success after binutils/gcc/linux/ [...] discards 6f3105b22c52 167: onsuccess: #960: 1: Success after binutils/gcc/linux/ [...] discards a236efcacde7 166: onsuccess: #959: 1: Success after binutils/gcc/linux/ [...] discards a437e1285dfb 165: onsuccess: #958: 1: Success after binutils/gcc/linux/ [...] discards a9f8eaeb1107 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/ [...] discards 4a439ee48ee7 163: onsuccess: #956: 1: Success after binutils/gcc/linux/ [...] discards 1ace0f123bbc 162: onsuccess: #955: 1: Success after binutils/gcc/linux/ [...] discards fff8aa701cfd 161: onsuccess: #954: 1: Success after binutils/gcc/linux/ [...] discards 786c61dbc15f 160: onsuccess: #953: 1: Success after binutils/gcc/linux/ [...] discards 70a6fdf0a6b2 159: onsuccess: #952: 1: Success after binutils/gcc/linux/ [...] discards 2e29b22a6e58 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards e79783c7fa25 157: onsuccess: #950: 1: Success after binutils/gcc/linux/ [...] discards 347c10dded7d 156: onsuccess: #949: 1: Success after binutils/gcc/linux/ [...] discards 8523afc74e1c 155: onsuccess: #948: 1: Success after binutils/gcc/linux/ [...] discards 1ed78ffc4996 154: onsuccess: #947: 1: Success after binutils/gcc/linux/ [...] discards 0f4a3d20c172 153: onsuccess: #946: 1: Success after binutils/gcc/linux/ [...] discards d72100dc8913 152: onsuccess: #945: 1: Success after binutils/gcc/linux/ [...] discards 42bbe56133fa 151: onsuccess: #944: 1: Success after binutils/gcc/linux/ [...] discards d822aa57fbe6 150: onsuccess: #943: 1: Success after binutils/gcc/linux/ [...] discards fc6eee693e2e 149: onsuccess: #942: 1: Success after binutils/gcc/linux/ [...] discards 89f579dc7189 148: onsuccess: #941: 1: Success after binutils/gcc/linux/ [...] discards 9200a6fc3076 147: onsuccess: #940: 1: Success after binutils/gcc/linux/ [...] discards 253cc446fca0 146: onsuccess: #939: 1: Success after binutils/gcc/linux/ [...] discards 890484fc79dd 145: onsuccess: #934: 1: Success after binutils/gcc/linux/ [...] discards 468f793666d3 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/ [...] discards 0ae7cd229af2 143: onsuccess: #931: 1: Success after binutils/gcc/linux/ [...] discards ea1085747924 142: onsuccess: #929: 1: Success after binutils/gcc/linux/ [...] discards 8359791166ec 141: onsuccess: #928: 1: Success after binutils/gcc/linux/ [...] discards 82fe22aac55c 140: onsuccess: #927: 1: Success after binutils/gcc/linux/ [...] discards 5536e00e3b46 139: onsuccess: #926: 1: Success after binutils/gcc/linux/ [...] discards cab21e0a1f12 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 1 [...] discards 753e3aaba1bd 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 4 [...] discards 07a11cd5a27a 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 1 [...] discards 98e105ac577c 135: onsuccess: #922: 1: Success after binutils/gcc/linux/ [...] discards 82d020e7845c 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 2 [...] discards f8cccfc19e90 133: onsuccess: #920: 1: Success after binutils/gcc/linux/ [...] discards 67199cfd71eb 132: onsuccess: #919: 1: Success after binutils/gcc/linux/ [...] discards 4d3a1fac313a 131: onsuccess: #918: 1: Success after binutils/gcc/linux/ [...] discards ab1d9fad2462 130: onsuccess: #917: 1: Success after binutils/gcc/linux/ [...] discards 88b47c34dd85 129: onsuccess: #916: 1: Success after binutils/gcc/linux/ [...] new d23a4062bfd4 129: onsuccess: #916: 1: Success after binutils/gcc/linux/ [...] new 696ea056a8ec 130: onsuccess: #917: 1: Success after binutils/gcc/linux/ [...] new 5473f11d9cd1 131: onsuccess: #918: 1: Success after binutils/gcc/linux/ [...] new 930ef876c218 132: onsuccess: #919: 1: Success after binutils/gcc/linux/ [...] new c8873800b7c9 133: onsuccess: #920: 1: Success after binutils/gcc/linux/ [...] new 60697fdd7799 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 2 [...] new 8e4d2acfd36a 135: onsuccess: #922: 1: Success after binutils/gcc/linux/ [...] new 4a23770a94fc 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 1 [...] new aa49813e71f0 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 4 [...] new 0ea1ba522ef6 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 1 [...] new 04411fa584a6 139: onsuccess: #926: 1: Success after binutils/gcc/linux/ [...] new c6b06ba9a537 140: onsuccess: #927: 1: Success after binutils/gcc/linux/ [...] new 1c3f2e1afa4f 141: onsuccess: #928: 1: Success after binutils/gcc/linux/ [...] new 3805a5ad8c36 142: onsuccess: #929: 1: Success after binutils/gcc/linux/ [...] new 427b68d8b157 143: onsuccess: #931: 1: Success after binutils/gcc/linux/ [...] new c5129c94d5e2 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/ [...] new 55b8e3b343bb 145: onsuccess: #934: 1: Success after binutils/gcc/linux/ [...] new 7df3386fe1ef 146: onsuccess: #939: 1: Success after binutils/gcc/linux/ [...] new c029d2fc06e9 147: onsuccess: #940: 1: Success after binutils/gcc/linux/ [...] new 3fc27b747de1 148: onsuccess: #941: 1: Success after binutils/gcc/linux/ [...] new 07cf91980560 149: onsuccess: #942: 1: Success after binutils/gcc/linux/ [...] new dff0bdbbeebe 150: onsuccess: #943: 1: Success after binutils/gcc/linux/ [...] new c0e2fd7a440f 151: onsuccess: #944: 1: Success after binutils/gcc/linux/ [...] new 84496b21c7e5 152: onsuccess: #945: 1: Success after binutils/gcc/linux/ [...] new a31612193b5f 153: onsuccess: #946: 1: Success after binutils/gcc/linux/ [...] new 12c2c464fe2a 154: onsuccess: #947: 1: Success after binutils/gcc/linux/ [...] new 90972bdad0e7 155: onsuccess: #948: 1: Success after binutils/gcc/linux/ [...] new 9f588af6804f 156: onsuccess: #949: 1: Success after binutils/gcc/linux/ [...] new 931a13b31133 157: onsuccess: #950: 1: Success after binutils/gcc/linux/ [...] new ac61e37b8764 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new cce937e442eb 159: onsuccess: #952: 1: Success after binutils/gcc/linux/ [...] new b3e35e4cda87 160: onsuccess: #953: 1: Success after binutils/gcc/linux/ [...] new 03829f1a98c9 161: onsuccess: #954: 1: Success after binutils/gcc/linux/ [...] new 9be45ff68768 162: onsuccess: #955: 1: Success after binutils/gcc/linux/ [...] new f0d820131c24 163: onsuccess: #956: 1: Success after binutils/gcc/linux/ [...] new ac140cfc7685 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/ [...] new b9dcb8158aa6 165: onsuccess: #958: 1: Success after binutils/gcc/linux/ [...] new 51f3b78e1900 166: onsuccess: #959: 1: Success after binutils/gcc/linux/ [...] new 3b1c374186b5 167: onsuccess: #960: 1: Success after binutils/gcc/linux/ [...] new 88e59670c428 168: onsuccess: #961: 1: Success after binutils/gcc/linux/ [...] new b54779a5cb98 169: onsuccess: #962: 1: Success after binutils/gcc/linux/ [...] new 3ee7d0f9740a 170: onsuccess: #963: 1: Success after binutils/gcc/linux/ [...] new 7d390221e439 171: onsuccess: #964: 1: Success after binutils/gcc/linux/ [...] new 3f88a817804a 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/ [...] new 1d00c42364c6 173: onsuccess: #966: 1: Success after binutils/gcc/linux/ [...] new 7bb882661111 174: onsuccess: #967: 1: Success after binutils/gcc/linux/ [...] new 5aeddec8614b 175: onsuccess: #968: 1: Success after binutils/gcc/linux/ [...] new ecf790468125 176: onsuccess: #969: 1: Success after binutils/gcc/linux/ [...] new 4673426faf93 177: onsuccess: #970: 1: Success after binutils/gcc/linux/ [...] new 1c91cb212b03 178: onsuccess: #971: 1: Success after binutils/gcc/linux/ [...] new 7647ae70c686 179: onsuccess: #972: 1: Success after binutils/gcc/linux/ [...] new 7aa4a5691d40 180: onsuccess: #973: 1: Success after binutils/gcc/linux/ [...] new e564ff459ed1 181: onsuccess: #974: 1: Success after binutils/gcc/linux/ [...] new ed1189dba5fb 182: onsuccess: #975: 1: Success after binutils/gcc/linux/ [...] new eb2685b2e7e0 183: onsuccess: #976: 1: Success after binutils/gcc/linux/ [...] new a41c4cdd05ed 184: onsuccess: #977: 1: Success after binutils/gcc/linux/ [...] new df2b2ea30881 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 5128274ee474 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new 77295ea2f513 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 6b74dc11844f 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new cd15d7c24399 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 92c57f33d944 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new b32257f16cdf 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 1424e03d5ede 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 0702f285b704 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 31bc7c4c1b18 194: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 56f5e9fc3108 195: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new ccd8eb6c2610 196: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new d68e22259f5a 197: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 7da0f04ce519 198: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 73caf3bc8836 199: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new ecbce21a0565 200: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 5792c8c3dba0 201: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 9ff63fa34881 202: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 0f6616155743 203: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 5e3005e47222 204: force: #26: : Failure after baseline build: no new commits new 63aff7bd8c2d 205: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 35825806279e 206: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new df3f61e3ff8a 207: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 5225d2ebb30c 208: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new a82c924399b9 209: force: #37: 1: Success after baseline build: no new commits new 4ae234ce0744 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181- [...] new f0c88a226b42 211: onsuccess: #44: 1: Success after linux: 26 commits new 785c5c9613aa 212: force: #45: 1: Success after gdb: 22 commits new de396a10fc88 213: force: #46: 1: Success after gdb-13-branchpoint-1550- [...] new 1716a9a60cc2 214: onsuccess: #47: 1: Success after gdb: 21 commits new 8253b589b328 215: onsuccess: #48: 1: Success after binutils/gcc/linux/g [...] new 725c2b437c53 216: onsuccess: #52: 1: Success after binutils/gcc/linux/g [...] new 0a3a621b95da 217: onsuccess: #53: 1: Success after binutils/gcc/linux/g [...] new 91ffc850e0d5 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/g [...] new a903aece1073 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new fecf92b4a5b7 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchp [...] new 969237d47acf 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 381552e1aae0 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/g [...] new b6f8e001a224 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new f1f8259d0fbb 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchp [...] new 036a2ed80e53 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new 0b8c4617d2b5 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new c064e0b4fab5 227: force: #81: 1: [TCWG CI] Failure after baseline build [...] new 7baa31113d96 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new 669dc019a601 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.900 [...] new 76c0b38ad248 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37 [...]
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 (7ecc1574e85f) \ 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 1980 -> 2108 bytes 02-prepare_abe/console.log.xz | Bin 2492 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 35756 -> 35580 bytes 04-build_abe-gcc/console.log.xz | Bin 204128 -> 203948 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8680 -> 8696 bytes 07-build_abe-glibc/console.log.xz | Bin 240872 -> 241360 bytes 08-build_abe-gdb/console.log.xz | Bin 35292 -> 35480 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3792 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3196 -> 3240 bytes 11-check_regression/console.log.xz | Bin 2900 -> 3652 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 76 +++++++++++++++++++++++++++++++++- 12-update_baseline/console.log | 50 +++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/glibc_rev | 2 +- mail/changes-list-long.txt | 8 ++-- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 14 +++---- manifest.sh | 16 +++---- sumfiles/gdb.log.0.xz | Bin 1938664 -> 1942044 bytes sumfiles/gdb.log.1.xz | Bin 22164 -> 22164 bytes sumfiles/gdb.log.2.xz | Bin 5708 -> 5428 bytes sumfiles/gdb.log.3.xz | Bin 5660 -> 5252 bytes sumfiles/gdb.sum | 14 +++---- sumfiles/gdb.sum.0 | 14 +++---- sumfiles/gdb.sum.1 | 4 +- sumfiles/gdb.sum.2 | 4 +- sumfiles/gdb.sum.3 | 4 +- 29 files changed, 144 insertions(+), 70 deletions(-)