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_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts.

discards fd1c21ecc51 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards e83f3decb4d 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 2d59eca7a82 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 7e7ae118a11 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards e7bfad794e1 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards ba770eb6412 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 9d540af3534 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards a0a2423be45 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards be9ef76dd5d 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards c717507e5ba 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards f97d260671b 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 2b7e61fd485 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 10b17718a44 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 3debd2c790f 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 298c9ec3647 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 9b129bbe3aa 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards f7dfbfd347b 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards ade8255bc67 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards bc8fa6b86eb 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 765aab56ec9 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] discards aa816b357e3 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards abda25f4427 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] discards f682ea5d9a5 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] discards e291b0e480c 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] discards 232c6eefff8 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] discards 00b5f3c6671 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] discards f698f68b9eb 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] discards 1cb9ba99eb4 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] discards de93ce5088f 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] discards c4a8185febc 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] discards 816b618b5dc 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] discards 0efd51a2f26 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 0c8eb8b0243 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 1f69e707089 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] discards fc41c45d28e 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards fe89a385a60 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards e67ecc11d00 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] discards b53bcb36af8 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards ecee30e9581 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards b8e2c6250c6 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] discards 1323c1ca5d8 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] discards 9b910b081fb 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards f17e646ce44 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 34663f31002 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] discards 8fc8dbe9b37 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 5590f37def7 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 8237c90bff4 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards f1dd598f687 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards 230864dc4bf 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] discards 8f8856ff929 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] discards 8e587f47e80 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] discards f5afdfc2d1c 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 89838c96a22 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards e2b4364f100 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] discards 0ef14d12633 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] discards 9ddef169845 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] discards aeab4d86de9 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards bb0686d6bc4 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] discards 0347e24c7a4 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards ea810e84b34 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] discards 8bef8a8db0d 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] discards 8ab48e851a8 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] discards 9fb28058e1c 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 6d316808b0c 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] discards 412c58263b3 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] discards b54171c4917 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] discards c246af61b2e 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] discards 0bb907fac1a 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards dabd3cd4ff8 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards fb0ab0c503c 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 28ec7af20e2 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] discards 9fbdd4c5f51 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards 590f3de3f27 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 019e21a74a2 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 32e9593bc3c 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] discards f9e26078a03 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] discards c532b3d1a29 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] discards b5e766bd508 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] discards 2c57a358ce0 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards 96bce0bee06 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards d6f412ac500 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] discards 7b44b230f12 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 7a985f64c34 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards efcd55e3c84 42: onsuccess: #53: 1: Success after linux: 3008 commits discards 5873c19629a 41: onsuccess: #51: 1: Success after binutils: 12 commits discards 8ab39a12330 40: onsuccess: #49: 1: Success after linux: 219 commits discards 2780f9ae544 39: onsuccess: #48: 1: Success after glibc: 2 commits discards 62ae643793b 38: onsuccess: #46: 1: Success after binutils: 26 commits discards 08ed0c243cb 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 97b9b859711 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 96991e88f1f 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 58d36ba73b7 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards fdd3255c075 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] discards b26ffc0767b 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 3b945bf2fb6 31: onsuccess: #38: 1: Success after linux: 12 commits discards 8af084cb230 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 762e381895d 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 047e7420b57 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards b545c04a748 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards f40224b7fc1 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 20035e4d236 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new 73c3c76e9b1 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new 18230b5a291 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 8efe27439ac 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 7a08251a29b 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 05b1c6b3688 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 826625ca8e2 30: onsuccess: #36: 1: Success after binutils: 18 commits new 5017447d08e 31: onsuccess: #38: 1: Success after linux: 12 commits new 788145a931a 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 191ed039c02 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] new c0be689b448 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 15a6fd29196 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new ba1a40c2e26 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 4d5e5254caf 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 8b35fdf1f2f 38: onsuccess: #46: 1: Success after binutils: 26 commits new 388cb54a214 39: onsuccess: #48: 1: Success after glibc: 2 commits new cf3722465a7 40: onsuccess: #49: 1: Success after linux: 219 commits new 25b4cc06c3f 41: onsuccess: #51: 1: Success after binutils: 12 commits new 5e2e95a7483 42: onsuccess: #53: 1: Success after linux: 3008 commits new d02adb7ccba 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new ab0a0dee42f 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new f978b931302 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] new ab8a89c4200 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new e6ed3555171 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new 1dbe4893a72 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] new a2a1b23d46b 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] new dc650121f02 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] new 7e5d1ccea8e 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] new cbfe7102b2b 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new a3808ab53af 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 5d81619a17e 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 123c075cf6c 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] new 9d59532ab68 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 1cc84766045 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new c9f6d0d53ba 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new d9a16973310 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] new 43fc455d18f 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] new 38af6c34353 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] new 4815c27de95 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] new 7eecf054e80 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 589056f65ed 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] new 0f178447a48 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] new c312e047a22 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] new 30793880f1d 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 972545aaf0d 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] new d516e7880a6 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new d079e33d08c 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] new 62f19875bf0 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] new 01932610fa9 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] new c9d4bd3aa65 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new ffb5eab14d9 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new d90bebcd3e7 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] new c95e0b36e08 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] new ecafe5b9c53 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] new c325597e25b 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 5219d1a6d74 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new b2401eeb054 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 3a50db02813 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 5955a788ac8 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] new c5a2993bd40 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 33e2b96782e 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 1fcaf8626dd 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] new 02197bad848 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] new 0461ec5d5a5 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 102b07c590a 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 585596c9d18 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] new 809238de55f 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new f87ce222ef9 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 1bfde0ccee4 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] new 8d53bf4c692 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 05af3204bfa 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 630bf0795d4 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] new 0f878ba05bf 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] new 1440b1c688a 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] new f78cbce655d 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] new eec4cf5b5f6 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] new 57e0b2d756e 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] new 4d87100aa60 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] new 88bb800d84d 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] new f8bfdbfca46 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] new 6a2ad6252fe 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] new 8b1a789ad8f 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new 4982e28001e 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] new bc073743683 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 08ffa3d5a99 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 05276e1d6ae 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new c4fd60b9509 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new be2e782a3ca 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new c5dc698712b 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 0d7cfb992e0 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 3a367c91209 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 5cb896ab557 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new c39a146b184 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 79801c68448 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new ce92d8243dd 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 61acc11b700 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 12db392322e 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 84ad1237216 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 152a307b82c 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 68ab1973726 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 9b4b015406b 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 27da5733953 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 82258019aa7 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...]

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 (fd1c21ecc51) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...]

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 1740 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 39320 -> 39080 bytes 04-build_abe-gcc/console.log.xz | Bin 205824 -> 203888 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8548 -> 8596 bytes 07-build_abe-glibc/console.log.xz | Bin 243916 -> 243948 bytes 08-build_abe-gdb/console.log.xz | Bin 38868 -> 38588 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3760 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3172 -> 2568 bytes 11-check_regression/console.log.xz | Bin 6212 -> 6100 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- 12-update_baseline/console.log | 38 +++++++++++++++++----------------- 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/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++++++++++----------------- sumfiles/gdb.log.xz | Bin 11896 -> 11916 bytes sumfiles/gdb.sum | 30 +++++++++++++-------------- 26 files changed, 67 insertions(+), 67 deletions(-)