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 8560eb6d9489 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards 00637862f4df 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards 28436b484744 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 17a44a6b83ef 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/g [...] discards ae69cc8f6e82 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards 56685f4c3e3f 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards a2357dfe12fe 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 58ffff54d4e3 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/g [...] discards bb6ea7ae0c5a 217: onsuccess: #53: 1: Success after binutils/gcc/linux/g [...] discards 5a569761bfca 216: onsuccess: #52: 1: Success after binutils/gcc/linux/g [...] discards bb231070e5be 215: onsuccess: #48: 1: Success after binutils/gcc/linux/g [...] discards 3045b69aac00 214: onsuccess: #47: 1: Success after gdb: 21 commits discards e0ec5697650e 213: force: #46: 1: Success after gdb-13-branchpoint-1550- [...] discards 2aea98f2ae41 212: force: #45: 1: Success after gdb: 22 commits discards d8ccd4df8de8 211: onsuccess: #44: 1: Success after linux: 26 commits discards 70fed945f2a8 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181- [...] discards 8f05f68fd4f5 209: force: #37: 1: Success after baseline build: no new commits discards 5141b07f613f 208: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards fc52621eda15 207: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 293223ecac71 206: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 3806469840ef 205: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards 93a3344b1d95 204: force: #26: : Failure after baseline build: no new commits discards 818b54e266d6 203: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards b0e95dc5987b 202: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 4fffaada80e7 201: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards b780cab815f8 200: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards cedea6b5163f 199: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards a0dc68b61f7f 198: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 305fbf2b3340 197: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards d9b361a7e2eb 196: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards ad6d2d5f25e7 195: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards b5ae5c8d890d 194: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 6fdfd624e1b6 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards bc55805ca192 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards e95eea553193 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards b8b4f103e8c5 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 5b7177496efc 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 5529fed6b2ef 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards 9af23eeaf5d3 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards c71416b7b2f3 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards d1b4fc293511 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 9fcaf3b3f212 184: onsuccess: #977: 1: Success after binutils/gcc/linux/ [...] discards 5a9f13876831 183: onsuccess: #976: 1: Success after binutils/gcc/linux/ [...] discards 38eb744b7f09 182: onsuccess: #975: 1: Success after binutils/gcc/linux/ [...] discards 9b06a10ef4e4 181: onsuccess: #974: 1: Success after binutils/gcc/linux/ [...] discards 146be5647f19 180: onsuccess: #973: 1: Success after binutils/gcc/linux/ [...] discards e3be33a28786 179: onsuccess: #972: 1: Success after binutils/gcc/linux/ [...] discards 41f390dacd48 178: onsuccess: #971: 1: Success after binutils/gcc/linux/ [...] discards ac408342b24e 177: onsuccess: #970: 1: Success after binutils/gcc/linux/ [...] discards 78c57cf9246e 176: onsuccess: #969: 1: Success after binutils/gcc/linux/ [...] discards 7a24a1fb31eb 175: onsuccess: #968: 1: Success after binutils/gcc/linux/ [...] discards a2046864bbe7 174: onsuccess: #967: 1: Success after binutils/gcc/linux/ [...] discards ce22f1efc6ff 173: onsuccess: #966: 1: Success after binutils/gcc/linux/ [...] discards 9b9978f50dfa 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/ [...] discards d69eb4ef20e4 171: onsuccess: #964: 1: Success after binutils/gcc/linux/ [...] discards 696f9957fa6e 170: onsuccess: #963: 1: Success after binutils/gcc/linux/ [...] discards 9591460ca115 169: onsuccess: #962: 1: Success after binutils/gcc/linux/ [...] discards 48b3db342ccf 168: onsuccess: #961: 1: Success after binutils/gcc/linux/ [...] discards a2b181b2b2b0 167: onsuccess: #960: 1: Success after binutils/gcc/linux/ [...] discards f26e2b9c6db1 166: onsuccess: #959: 1: Success after binutils/gcc/linux/ [...] discards b77b996e64ea 165: onsuccess: #958: 1: Success after binutils/gcc/linux/ [...] discards f8f977123702 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/ [...] discards a58b83546def 163: onsuccess: #956: 1: Success after binutils/gcc/linux/ [...] discards 9d98fee81e42 162: onsuccess: #955: 1: Success after binutils/gcc/linux/ [...] discards b3a5f661dc95 161: onsuccess: #954: 1: Success after binutils/gcc/linux/ [...] discards bd243d634f43 160: onsuccess: #953: 1: Success after binutils/gcc/linux/ [...] discards a7a735e31ec2 159: onsuccess: #952: 1: Success after binutils/gcc/linux/ [...] discards 98e75cd6ceb0 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 56fa1234d849 157: onsuccess: #950: 1: Success after binutils/gcc/linux/ [...] discards bcf4fb3507fd 156: onsuccess: #949: 1: Success after binutils/gcc/linux/ [...] discards d83f1ed6cd95 155: onsuccess: #948: 1: Success after binutils/gcc/linux/ [...] discards 05e0ccecce37 154: onsuccess: #947: 1: Success after binutils/gcc/linux/ [...] discards ff15c777e45f 153: onsuccess: #946: 1: Success after binutils/gcc/linux/ [...] discards fda3b2354d27 152: onsuccess: #945: 1: Success after binutils/gcc/linux/ [...] discards cd8c39ce9f85 151: onsuccess: #944: 1: Success after binutils/gcc/linux/ [...] discards 0c2dd3146e7d 150: onsuccess: #943: 1: Success after binutils/gcc/linux/ [...] discards 25375ffc84a7 149: onsuccess: #942: 1: Success after binutils/gcc/linux/ [...] discards 72f683d12c16 148: onsuccess: #941: 1: Success after binutils/gcc/linux/ [...] discards 80d5e884e8e7 147: onsuccess: #940: 1: Success after binutils/gcc/linux/ [...] discards 1fe061c4a6f4 146: onsuccess: #939: 1: Success after binutils/gcc/linux/ [...] discards d7a854b3a363 145: onsuccess: #934: 1: Success after binutils/gcc/linux/ [...] discards 94b5fb2f3ab7 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/ [...] discards 80fad2467316 143: onsuccess: #931: 1: Success after binutils/gcc/linux/ [...] discards e9811e7439ae 142: onsuccess: #929: 1: Success after binutils/gcc/linux/ [...] discards 7b2535ec64f9 141: onsuccess: #928: 1: Success after binutils/gcc/linux/ [...] discards 6bc94ce53670 140: onsuccess: #927: 1: Success after binutils/gcc/linux/ [...] discards 766cea62aa8a 139: onsuccess: #926: 1: Success after binutils/gcc/linux/ [...] discards e6746237f1ad 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 1 [...] discards 65d43bc4429d 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 4 [...] discards 9fea11f83029 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 1 [...] discards 15a3687ae2a5 135: onsuccess: #922: 1: Success after binutils/gcc/linux/ [...] discards c74dfadbf18d 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 2 [...] discards 3e2631fbce9a 133: onsuccess: #920: 1: Success after binutils/gcc/linux/ [...] discards 45ca10f8be86 132: onsuccess: #919: 1: Success after binutils/gcc/linux/ [...] discards 00b744fc3b64 131: onsuccess: #918: 1: Success after binutils/gcc/linux/ [...] discards 81b4f093bdac 130: onsuccess: #917: 1: Success after binutils/gcc/linux/ [...] discards 5573217e2004 129: onsuccess: #916: 1: Success after binutils/gcc/linux/ [...] discards 0702d5bffcf5 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/ [...] discards b3d4d2fbe2c3 127: onsuccess: #914: 1: Success after binutils/gcc/linux/ [...] discards 04fb696c134e 126: onsuccess: #913: 1: Success after binutils/gcc/linux/ [...] discards 872016116a41 125: onsuccess: #912: 1: Success after binutils/gcc/linux/ [...] new 5c5d0a60e2c8 125: onsuccess: #912: 1: Success after binutils/gcc/linux/ [...] new 28ab9227c2f4 126: onsuccess: #913: 1: Success after binutils/gcc/linux/ [...] new 12beff49cdde 127: onsuccess: #914: 1: Success after binutils/gcc/linux/ [...] new 22137b3d6a0b 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/ [...] new ce0988ffd118 129: onsuccess: #916: 1: Success after binutils/gcc/linux/ [...] new 64591970482b 130: onsuccess: #917: 1: Success after binutils/gcc/linux/ [...] new 98a0017b2e78 131: onsuccess: #918: 1: Success after binutils/gcc/linux/ [...] new e1d0a59e99cc 132: onsuccess: #919: 1: Success after binutils/gcc/linux/ [...] new 2b82cc980c23 133: onsuccess: #920: 1: Success after binutils/gcc/linux/ [...] new 2e5f45e542fe 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 2 [...] new b7e0118e8f8c 135: onsuccess: #922: 1: Success after binutils/gcc/linux/ [...] new 2258de9ca370 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 1 [...] new 66102c3bad20 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 4 [...] new 8eccb5c3c9a1 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 1 [...] new 179fa3111f01 139: onsuccess: #926: 1: Success after binutils/gcc/linux/ [...] new 588a62ab42cb 140: onsuccess: #927: 1: Success after binutils/gcc/linux/ [...] new 4f6a97971ebd 141: onsuccess: #928: 1: Success after binutils/gcc/linux/ [...] new 3433c2c054e5 142: onsuccess: #929: 1: Success after binutils/gcc/linux/ [...] new d08a1fd04596 143: onsuccess: #931: 1: Success after binutils/gcc/linux/ [...] new 2e2b5860ea8e 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/ [...] new 9cd92969b353 145: onsuccess: #934: 1: Success after binutils/gcc/linux/ [...] new d1ed24675f53 146: onsuccess: #939: 1: Success after binutils/gcc/linux/ [...] new 4105bf50fa26 147: onsuccess: #940: 1: Success after binutils/gcc/linux/ [...] new d7ca1a8984c9 148: onsuccess: #941: 1: Success after binutils/gcc/linux/ [...] new 16ccb48c7d65 149: onsuccess: #942: 1: Success after binutils/gcc/linux/ [...] new 9e431450e0df 150: onsuccess: #943: 1: Success after binutils/gcc/linux/ [...] new 3c3c4266feca 151: onsuccess: #944: 1: Success after binutils/gcc/linux/ [...] new 47d09b5dbc5d 152: onsuccess: #945: 1: Success after binutils/gcc/linux/ [...] new 3e8355255770 153: onsuccess: #946: 1: Success after binutils/gcc/linux/ [...] new 617cfd176d21 154: onsuccess: #947: 1: Success after binutils/gcc/linux/ [...] new b1ae5b9c3f37 155: onsuccess: #948: 1: Success after binutils/gcc/linux/ [...] new eb6ecc8cca69 156: onsuccess: #949: 1: Success after binutils/gcc/linux/ [...] new 222e7028b680 157: onsuccess: #950: 1: Success after binutils/gcc/linux/ [...] new 5346fd910a35 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new e037c8bb63f0 159: onsuccess: #952: 1: Success after binutils/gcc/linux/ [...] new 798a2bb6d152 160: onsuccess: #953: 1: Success after binutils/gcc/linux/ [...] new 16104e01bd85 161: onsuccess: #954: 1: Success after binutils/gcc/linux/ [...] new e3cb83365e9a 162: onsuccess: #955: 1: Success after binutils/gcc/linux/ [...] new 65c5b1df37cc 163: onsuccess: #956: 1: Success after binutils/gcc/linux/ [...] new 0740e4711158 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/ [...] new e3e96e59152f 165: onsuccess: #958: 1: Success after binutils/gcc/linux/ [...] new 425a456a7566 166: onsuccess: #959: 1: Success after binutils/gcc/linux/ [...] new 0432f827e5e5 167: onsuccess: #960: 1: Success after binutils/gcc/linux/ [...] new 4ce54df68913 168: onsuccess: #961: 1: Success after binutils/gcc/linux/ [...] new 735762ed701a 169: onsuccess: #962: 1: Success after binutils/gcc/linux/ [...] new 6b6d952a3758 170: onsuccess: #963: 1: Success after binutils/gcc/linux/ [...] new 3ee3584f430f 171: onsuccess: #964: 1: Success after binutils/gcc/linux/ [...] new a14937bf8916 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/ [...] new 001a23021ad0 173: onsuccess: #966: 1: Success after binutils/gcc/linux/ [...] new 6b068ac488b4 174: onsuccess: #967: 1: Success after binutils/gcc/linux/ [...] new ed79b1c7c7cc 175: onsuccess: #968: 1: Success after binutils/gcc/linux/ [...] new 9ce120df521a 176: onsuccess: #969: 1: Success after binutils/gcc/linux/ [...] new be82a18d57a1 177: onsuccess: #970: 1: Success after binutils/gcc/linux/ [...] new 0e799f8960e3 178: onsuccess: #971: 1: Success after binutils/gcc/linux/ [...] new 4ba734d0dc19 179: onsuccess: #972: 1: Success after binutils/gcc/linux/ [...] new de0a0f8b2e14 180: onsuccess: #973: 1: Success after binutils/gcc/linux/ [...] new 67589fa00ce3 181: onsuccess: #974: 1: Success after binutils/gcc/linux/ [...] new 607e2836e41b 182: onsuccess: #975: 1: Success after binutils/gcc/linux/ [...] new 65eaf4dcb577 183: onsuccess: #976: 1: Success after binutils/gcc/linux/ [...] new 56406fce0ca5 184: onsuccess: #977: 1: Success after binutils/gcc/linux/ [...] new 245e176bff50 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 2fccfe213484 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new ca9fc0a00299 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 2ff1b3b3bfd2 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new fba69e75159f 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new fa805abf68b9 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new ad854dce6918 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new f15dc7468f6c 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 76a3981530c5 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new aabab2d4ba6a 194: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new a41fa7d0a28c 195: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new b554aa3ebc7b 196: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 702b49ec4194 197: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new efccb11999c5 198: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 8ef0df2f0de3 199: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new a42c2cb7147e 200: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new facbd4cfc281 201: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new fe992cc87fa4 202: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new bb8083b9379f 203: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 078f9acdf077 204: force: #26: : Failure after baseline build: no new commits new ac5ba7da5e75 205: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 8deb9af545a0 206: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 2586a03a13b4 207: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new c6bc5b2b7d6b 208: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new f2aae89a33fe 209: force: #37: 1: Success after baseline build: no new commits new c0a25e464615 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181- [...] new 9d309d19f7f9 211: onsuccess: #44: 1: Success after linux: 26 commits new 31db5c0ed009 212: force: #45: 1: Success after gdb: 22 commits new 5ca02b245a9d 213: force: #46: 1: Success after gdb-13-branchpoint-1550- [...] new d5ec7bccda15 214: onsuccess: #47: 1: Success after gdb: 21 commits new 80dc3cee27c6 215: onsuccess: #48: 1: Success after binutils/gcc/linux/g [...] new 56df8997d0f8 216: onsuccess: #52: 1: Success after binutils/gcc/linux/g [...] new 46af1af55187 217: onsuccess: #53: 1: Success after binutils/gcc/linux/g [...] new b93217663011 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/g [...] new 1aed9124eae4 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new dc1fd4bd6693 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchp [...] new d74c5edfb68e 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new b903f2d8960c 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/g [...] new b81c7992dff0 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 0a2794fa4b55 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchp [...] new 55b65d9e4958 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new 8050d48267cc 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 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 (8560eb6d9489) \ 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 2024 -> 2044 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 35580 -> 35504 bytes 04-build_abe-gcc/console.log.xz | Bin 202388 -> 204240 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8652 -> 8720 bytes 07-build_abe-glibc/console.log.xz | Bin 240832 -> 242100 bytes 08-build_abe-gdb/console.log.xz | Bin 35172 -> 35404 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3832 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3148 -> 3116 bytes 11-check_regression/console.log.xz | Bin 3988 -> 3988 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 82 ++++++++++--------------- 12-update_baseline/console.log | 66 ++++++++++---------- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/changes-list-long.txt | 14 ++--- mail/changes-list-short.txt | 2 +- manifest.sh => mail/last_good.sh | 0 manifest.sh | 22 +++---- sumfiles/gdb.log.0.xz | Bin 2010260 -> 2016968 bytes sumfiles/gdb.log.1.xz | Bin 31100 -> 30412 bytes sumfiles/gdb.log.2.xz | Bin 15928 -> 0 bytes sumfiles/gdb.sum | 20 +++---- sumfiles/gdb.sum.0 | 22 +++---- sumfiles/gdb.sum.1 | 16 ++--- sumfiles/gdb.sum.2 | 110 ---------------------------------- 27 files changed, 116 insertions(+), 246 deletions(-) copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 sumfiles/gdb.log.2.xz delete mode 100644 sumfiles/gdb.sum.2