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 8050d48267cc 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards 55b65d9e4958 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards 0a2794fa4b55 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards b81c7992dff0 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards b903f2d8960c 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/g [...] discards d74c5edfb68e 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards dc1fd4bd6693 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards 1aed9124eae4 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards b93217663011 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/g [...] discards 46af1af55187 217: onsuccess: #53: 1: Success after binutils/gcc/linux/g [...] discards 56df8997d0f8 216: onsuccess: #52: 1: Success after binutils/gcc/linux/g [...] discards 80dc3cee27c6 215: onsuccess: #48: 1: Success after binutils/gcc/linux/g [...] discards d5ec7bccda15 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 5ca02b245a9d 213: force: #46: 1: Success after gdb-13-branchpoint-1550- [...] discards 31db5c0ed009 212: force: #45: 1: Success after gdb: 22 commits discards 9d309d19f7f9 211: onsuccess: #44: 1: Success after linux: 26 commits discards c0a25e464615 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181- [...] discards f2aae89a33fe 209: force: #37: 1: Success after baseline build: no new commits discards c6bc5b2b7d6b 208: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards 2586a03a13b4 207: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 8deb9af545a0 206: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards ac5ba7da5e75 205: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards 078f9acdf077 204: force: #26: : Failure after baseline build: no new commits discards bb8083b9379f 203: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards fe992cc87fa4 202: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards facbd4cfc281 201: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards a42c2cb7147e 200: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 8ef0df2f0de3 199: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards efccb11999c5 198: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 702b49ec4194 197: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards b554aa3ebc7b 196: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards a41fa7d0a28c 195: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards aabab2d4ba6a 194: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 76a3981530c5 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards f15dc7468f6c 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards ad854dce6918 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards fa805abf68b9 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards fba69e75159f 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 2ff1b3b3bfd2 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards ca9fc0a00299 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 2fccfe213484 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards 245e176bff50 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 56406fce0ca5 184: onsuccess: #977: 1: Success after binutils/gcc/linux/ [...] discards 65eaf4dcb577 183: onsuccess: #976: 1: Success after binutils/gcc/linux/ [...] discards 607e2836e41b 182: onsuccess: #975: 1: Success after binutils/gcc/linux/ [...] discards 67589fa00ce3 181: onsuccess: #974: 1: Success after binutils/gcc/linux/ [...] discards de0a0f8b2e14 180: onsuccess: #973: 1: Success after binutils/gcc/linux/ [...] discards 4ba734d0dc19 179: onsuccess: #972: 1: Success after binutils/gcc/linux/ [...] discards 0e799f8960e3 178: onsuccess: #971: 1: Success after binutils/gcc/linux/ [...] discards be82a18d57a1 177: onsuccess: #970: 1: Success after binutils/gcc/linux/ [...] discards 9ce120df521a 176: onsuccess: #969: 1: Success after binutils/gcc/linux/ [...] discards ed79b1c7c7cc 175: onsuccess: #968: 1: Success after binutils/gcc/linux/ [...] discards 6b068ac488b4 174: onsuccess: #967: 1: Success after binutils/gcc/linux/ [...] discards 001a23021ad0 173: onsuccess: #966: 1: Success after binutils/gcc/linux/ [...] discards a14937bf8916 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/ [...] discards 3ee3584f430f 171: onsuccess: #964: 1: Success after binutils/gcc/linux/ [...] discards 6b6d952a3758 170: onsuccess: #963: 1: Success after binutils/gcc/linux/ [...] discards 735762ed701a 169: onsuccess: #962: 1: Success after binutils/gcc/linux/ [...] discards 4ce54df68913 168: onsuccess: #961: 1: Success after binutils/gcc/linux/ [...] discards 0432f827e5e5 167: onsuccess: #960: 1: Success after binutils/gcc/linux/ [...] discards 425a456a7566 166: onsuccess: #959: 1: Success after binutils/gcc/linux/ [...] discards e3e96e59152f 165: onsuccess: #958: 1: Success after binutils/gcc/linux/ [...] discards 0740e4711158 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/ [...] discards 65c5b1df37cc 163: onsuccess: #956: 1: Success after binutils/gcc/linux/ [...] discards e3cb83365e9a 162: onsuccess: #955: 1: Success after binutils/gcc/linux/ [...] discards 16104e01bd85 161: onsuccess: #954: 1: Success after binutils/gcc/linux/ [...] discards 798a2bb6d152 160: onsuccess: #953: 1: Success after binutils/gcc/linux/ [...] discards e037c8bb63f0 159: onsuccess: #952: 1: Success after binutils/gcc/linux/ [...] discards 5346fd910a35 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 222e7028b680 157: onsuccess: #950: 1: Success after binutils/gcc/linux/ [...] discards eb6ecc8cca69 156: onsuccess: #949: 1: Success after binutils/gcc/linux/ [...] discards b1ae5b9c3f37 155: onsuccess: #948: 1: Success after binutils/gcc/linux/ [...] discards 617cfd176d21 154: onsuccess: #947: 1: Success after binutils/gcc/linux/ [...] discards 3e8355255770 153: onsuccess: #946: 1: Success after binutils/gcc/linux/ [...] discards 47d09b5dbc5d 152: onsuccess: #945: 1: Success after binutils/gcc/linux/ [...] discards 3c3c4266feca 151: onsuccess: #944: 1: Success after binutils/gcc/linux/ [...] discards 9e431450e0df 150: onsuccess: #943: 1: Success after binutils/gcc/linux/ [...] discards 16ccb48c7d65 149: onsuccess: #942: 1: Success after binutils/gcc/linux/ [...] discards d7ca1a8984c9 148: onsuccess: #941: 1: Success after binutils/gcc/linux/ [...] discards 4105bf50fa26 147: onsuccess: #940: 1: Success after binutils/gcc/linux/ [...] discards d1ed24675f53 146: onsuccess: #939: 1: Success after binutils/gcc/linux/ [...] discards 9cd92969b353 145: onsuccess: #934: 1: Success after binutils/gcc/linux/ [...] discards 2e2b5860ea8e 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/ [...] discards d08a1fd04596 143: onsuccess: #931: 1: Success after binutils/gcc/linux/ [...] discards 3433c2c054e5 142: onsuccess: #929: 1: Success after binutils/gcc/linux/ [...] discards 4f6a97971ebd 141: onsuccess: #928: 1: Success after binutils/gcc/linux/ [...] discards 588a62ab42cb 140: onsuccess: #927: 1: Success after binutils/gcc/linux/ [...] discards 179fa3111f01 139: onsuccess: #926: 1: Success after binutils/gcc/linux/ [...] discards 8eccb5c3c9a1 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 1 [...] discards 66102c3bad20 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 4 [...] discards 2258de9ca370 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 1 [...] discards b7e0118e8f8c 135: onsuccess: #922: 1: Success after binutils/gcc/linux/ [...] discards 2e5f45e542fe 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 2 [...] discards 2b82cc980c23 133: onsuccess: #920: 1: Success after binutils/gcc/linux/ [...] discards e1d0a59e99cc 132: onsuccess: #919: 1: Success after binutils/gcc/linux/ [...] discards 98a0017b2e78 131: onsuccess: #918: 1: Success after binutils/gcc/linux/ [...] discards 64591970482b 130: onsuccess: #917: 1: Success after binutils/gcc/linux/ [...] discards ce0988ffd118 129: onsuccess: #916: 1: Success after binutils/gcc/linux/ [...] discards 22137b3d6a0b 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/ [...] discards 12beff49cdde 127: onsuccess: #914: 1: Success after binutils/gcc/linux/ [...] discards 28ab9227c2f4 126: onsuccess: #913: 1: Success after binutils/gcc/linux/ [...] new dbbee751f7e0 126: onsuccess: #913: 1: Success after binutils/gcc/linux/ [...] new 0752416f536e 127: onsuccess: #914: 1: Success after binutils/gcc/linux/ [...] new 40204d1e5385 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/ [...] new 00524e887534 129: onsuccess: #916: 1: Success after binutils/gcc/linux/ [...] new f868d1fd0bdd 130: onsuccess: #917: 1: Success after binutils/gcc/linux/ [...] new 801844726f7a 131: onsuccess: #918: 1: Success after binutils/gcc/linux/ [...] new b4820af688bd 132: onsuccess: #919: 1: Success after binutils/gcc/linux/ [...] new 3134af289a2a 133: onsuccess: #920: 1: Success after binutils/gcc/linux/ [...] new 03a515487be0 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 2 [...] new 2ea29ae8a360 135: onsuccess: #922: 1: Success after binutils/gcc/linux/ [...] new 110ead664bbf 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 1 [...] new 281a44be2861 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 4 [...] new ca560c2c6359 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 1 [...] new 94db141305b3 139: onsuccess: #926: 1: Success after binutils/gcc/linux/ [...] new ba51759aac87 140: onsuccess: #927: 1: Success after binutils/gcc/linux/ [...] new 8ee2d401f16a 141: onsuccess: #928: 1: Success after binutils/gcc/linux/ [...] new 62b572a85838 142: onsuccess: #929: 1: Success after binutils/gcc/linux/ [...] new 786368bdd607 143: onsuccess: #931: 1: Success after binutils/gcc/linux/ [...] new 12d1a19959b4 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/ [...] new d504679bc294 145: onsuccess: #934: 1: Success after binutils/gcc/linux/ [...] new 60965e133ced 146: onsuccess: #939: 1: Success after binutils/gcc/linux/ [...] new e38141a2d712 147: onsuccess: #940: 1: Success after binutils/gcc/linux/ [...] new fd606506b967 148: onsuccess: #941: 1: Success after binutils/gcc/linux/ [...] new 8d870f4f0b97 149: onsuccess: #942: 1: Success after binutils/gcc/linux/ [...] new b0e63096170f 150: onsuccess: #943: 1: Success after binutils/gcc/linux/ [...] new 184d78e0a0b3 151: onsuccess: #944: 1: Success after binutils/gcc/linux/ [...] new 289faf37971c 152: onsuccess: #945: 1: Success after binutils/gcc/linux/ [...] new e47b1263148c 153: onsuccess: #946: 1: Success after binutils/gcc/linux/ [...] new 937e9badbe99 154: onsuccess: #947: 1: Success after binutils/gcc/linux/ [...] new 9babdf2a8268 155: onsuccess: #948: 1: Success after binutils/gcc/linux/ [...] new fa6cc9cb727c 156: onsuccess: #949: 1: Success after binutils/gcc/linux/ [...] new 17b9e31b1753 157: onsuccess: #950: 1: Success after binutils/gcc/linux/ [...] new dfc4e2613782 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new f964cdb9e848 159: onsuccess: #952: 1: Success after binutils/gcc/linux/ [...] new 318f10fedadd 160: onsuccess: #953: 1: Success after binutils/gcc/linux/ [...] new 5d3d16a0a0dc 161: onsuccess: #954: 1: Success after binutils/gcc/linux/ [...] new bab45b4ac16f 162: onsuccess: #955: 1: Success after binutils/gcc/linux/ [...] new dc2c356d6a01 163: onsuccess: #956: 1: Success after binutils/gcc/linux/ [...] new 74d946ee4d65 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/ [...] new f2ee9269f2e1 165: onsuccess: #958: 1: Success after binutils/gcc/linux/ [...] new ad96144d013c 166: onsuccess: #959: 1: Success after binutils/gcc/linux/ [...] new 5a130b7de15d 167: onsuccess: #960: 1: Success after binutils/gcc/linux/ [...] new 995f8d70484f 168: onsuccess: #961: 1: Success after binutils/gcc/linux/ [...] new 687b31b6cde8 169: onsuccess: #962: 1: Success after binutils/gcc/linux/ [...] new 0e5089849035 170: onsuccess: #963: 1: Success after binutils/gcc/linux/ [...] new 8e00c6acd9cd 171: onsuccess: #964: 1: Success after binutils/gcc/linux/ [...] new 91f877fcbdc1 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/ [...] new eab22887b097 173: onsuccess: #966: 1: Success after binutils/gcc/linux/ [...] new 5b1a0a4d0736 174: onsuccess: #967: 1: Success after binutils/gcc/linux/ [...] new 63baeef29027 175: onsuccess: #968: 1: Success after binutils/gcc/linux/ [...] new f72b0c3d4e55 176: onsuccess: #969: 1: Success after binutils/gcc/linux/ [...] new 749507cc98c1 177: onsuccess: #970: 1: Success after binutils/gcc/linux/ [...] new 236721932417 178: onsuccess: #971: 1: Success after binutils/gcc/linux/ [...] new 953ec4a724d9 179: onsuccess: #972: 1: Success after binutils/gcc/linux/ [...] new af4d5193bda0 180: onsuccess: #973: 1: Success after binutils/gcc/linux/ [...] new 1278e258deef 181: onsuccess: #974: 1: Success after binutils/gcc/linux/ [...] new 17beb9018ce2 182: onsuccess: #975: 1: Success after binutils/gcc/linux/ [...] new 2c6bc91040cf 183: onsuccess: #976: 1: Success after binutils/gcc/linux/ [...] new 90c5d6b5ac82 184: onsuccess: #977: 1: Success after binutils/gcc/linux/ [...] new 557a88184937 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 928064b0aacb 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new b8b6d503b45e 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 3d26a8bf6fab 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new d54afa8d7772 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new e73ffdd557d2 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 22190518ab43 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 2bc666f89f6f 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new e85c16899511 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new f49037f890cf 194: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new ce7fb3aaf662 195: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 757a4db64d7f 196: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 657e7e8c324b 197: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 5505b8998e07 198: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 4495fa409388 199: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 42b3eac94800 200: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 2627fc0efbd4 201: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 996379b6e348 202: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new bc6e47849625 203: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new da563626a9e8 204: force: #26: : Failure after baseline build: no new commits new bbd350d64a3a 205: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new f11de2ccd345 206: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new d91406548cad 207: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 531d2e9e4a68 208: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new e20539b7e2b8 209: force: #37: 1: Success after baseline build: no new commits new 1620c7b32b06 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181- [...] new 775f39b1ac51 211: onsuccess: #44: 1: Success after linux: 26 commits new 2316daffd3be 212: force: #45: 1: Success after gdb: 22 commits new 398daf0200b4 213: force: #46: 1: Success after gdb-13-branchpoint-1550- [...] new 5311c667ab4b 214: onsuccess: #47: 1: Success after gdb: 21 commits new 4ccb1374318e 215: onsuccess: #48: 1: Success after binutils/gcc/linux/g [...] new 138a0219e2e0 216: onsuccess: #52: 1: Success after binutils/gcc/linux/g [...] new 515e6597a810 217: onsuccess: #53: 1: Success after binutils/gcc/linux/g [...] new 162cf6d77f50 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/g [...] new 769d571968b6 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new f536a0a41d0d 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchp [...] new 55c72e333dc0 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 2cee9a753122 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/g [...] new 07dd13547156 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new d8918275d2e3 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchp [...] new 74d97eed122b 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new eb58aca9440c 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new 622c8380b660 227: force: #81: 1: [TCWG CI] Failure after baseline build [...]

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 (8050d48267cc) \ 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 2044 -> 2068 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 35504 -> 35984 bytes 04-build_abe-gcc/console.log.xz | Bin 204240 -> 205776 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8720 -> 8688 bytes 07-build_abe-glibc/console.log.xz | Bin 242100 -> 242596 bytes 08-build_abe-gdb/console.log.xz | Bin 35404 -> 35176 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3800 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3116 -> 3112 bytes 11-check_regression/console.log.xz | Bin 3988 -> 2908 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 6 +++ 11-check_regression/results.compare | 13 +++-- 11-check_regression/results.compare2 | 92 +------------------------------- 11-check_regression/results.regressions | 14 +++++ 12-update_baseline/console.log | 68 +++++++++++------------ dashboard/dashboard-generate.sh | 2 +- mail/changes-list-long.txt | 8 +-- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 22 ++++---- mail/short-diag.txt | 2 +- manifest.sh | 19 ++++--- results | 14 +++++ sumfiles/gdb.log.0.xz | Bin 2016968 -> 1979592 bytes sumfiles/gdb.log.1.xz | Bin 30412 -> 31148 bytes sumfiles/gdb.sum | 25 ++++----- sumfiles/gdb.sum.0 | 28 +++++----- sumfiles/gdb.sum.1 | 14 ++--- 29 files changed, 138 insertions(+), 192 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions