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 1d5276e723 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] discards 5f2fe86dcb 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] discards 6fd1c8b14f 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits discards a0a6e649c7 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] discards a14190742b 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] discards 1eb3f2c48c 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards b8aa34d91e 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards a47e75a92b 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards 93f8c71822 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards b4197dc9f0 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards fdea8fda44 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards ab59290485 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 2cf8e9b1b2 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards 2625437534 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards 4c5bf9c6a5 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards fe97647fd7 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards 0bca6d86ec 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards 4f19e54592 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards 210901df0c 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards fe058b3216 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 78cc2e850b 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards cb3ec2d84b 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards 3e4feebc1b 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards 1bb8ba6dff 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 7e5550cd55 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 012489dc32 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards ed681399e1 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards ce9936ffa3 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards d190bf7c85 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards b368a7cfd3 214: onsuccess: #47: 1: Success after gdb: 21 commits discards f38dc6809a 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards 768ea89af9 212: force: #45: 1: Success after gdb: 22 commits discards e9aff42ac9 211: onsuccess: #44: 1: Success after linux: 26 commits discards fda00296b9 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards aa83b24e41 209: force: #37: 1: Success after baseline build: no new commits discards 1969be2416 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards c0a2a603c0 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards bfac0dd692 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 62d20effd3 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 7b05f16062 204: force: #26: : Failure after baseline build: no new commits discards 72ebe9d64b 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards a25521a0b1 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards ce5e9a9b04 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 1499879d10 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 431bc1cbd5 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards e7efd00c8d 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 02e387f6b3 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 5d9b46335d 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 31ab5c9cc2 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 0539c35ab7 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards c7340cde0c 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards bafefea373 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards e8219bdbae 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards f5217b3b37 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 3ac09c7ccd 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards d7e2d313ac 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 0eeb87ccc3 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards db92db9eb7 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 84b6e4e0ad 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards b00a843ba1 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards e481e16e1c 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards 44a937ecc3 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards 65525555d5 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards 0b5ea3bd10 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards 0e0c06ccec 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards 565699bce0 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards 02a37d8120 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards 846f7b3225 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards 137bcea343 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards 558adf0f7c 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards bef1204815 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards 3ebe6e1158 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards f915556d72 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards 591ec7c318 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards 0f5241c0e1 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards 8131d3abd6 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards 80845fb50f 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards 057c32a792 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards 933a95356c 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards 871dcba3bc 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards 5b402e9bea 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards c63ab52bda 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards bee330eb85 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards c014c6655d 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards c15f1c5a0f 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards 03b3b95f44 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 2723609538 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards fdf9bef5c8 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards 50b6a4d771 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards 071d1361d6 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards 74d9699462 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards 69d06812c6 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards 698bfa791c 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards 8ecf1bba57 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards 099de3c065 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards 80f9157c1b 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards 98c7bc384a 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards 285c1dbe21 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards 244862ac0c 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards 110497219d 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards 7026b91bad 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 1bc101c280 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 07b28a674e 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new 4c4571df03 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new ed13ba979f 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new bace74dd61 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new 9ab6a6c64e 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new 433b47901b 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new 95701718d0 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new c1eac4d91b 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new ef801f0b75 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 963f183445 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new a768de8a84 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 0b0a07c2e1 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new f14c0077a2 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new 28c78ce55e 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new a16a333e1d 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 3380caeaa6 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new dec860a57f 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new 368da5d5b1 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 7bf934cb43 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new d05edc6be9 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new a1035ecb5b 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new 8317257883 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new 9904b91cd5 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new 1b571e7276 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new f41f245849 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new 56ac28d294 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new 3118dbf462 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new 6e97b57511 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new 2fe9684bf0 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 8c9651d963 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new 980132df2a 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new 2b776a78c7 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new 326d7452e3 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new babf96c621 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new d1c8fc8dc5 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new 7c6a5fbd85 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new bb94d93c1d 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new 6892c82700 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new d1a5070c7a 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new 628919a452 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new ceed766b96 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new a88041839b 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 8becb9cf8e 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 72f26c03fb 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new e4def644d9 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new b421fe19b1 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 1c05b65920 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new e983af21ce 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 9e62fd76a0 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new f316f971a0 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 0fb6e1a229 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 8ee8948b13 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 94f312a115 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 208e1bf0a4 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 43e9999671 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 05a6b591ca 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 8d8526351a 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new cd424326df 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new aae6d39a64 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 8266156b8b 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 729e771d33 204: force: #26: : Failure after baseline build: no new commits new 2c8b8b3a23 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new e7ecfb5a7a 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 1f094cd268 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 1b8bad70b7 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 9937ef8ed8 209: force: #37: 1: Success after baseline build: no new commits new e2117e8152 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new a601a94a65 211: onsuccess: #44: 1: Success after linux: 26 commits new 2d999ba0a9 212: force: #45: 1: Success after gdb: 22 commits new 72cda742dc 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new 8e1e9c42eb 214: onsuccess: #47: 1: Success after gdb: 21 commits new e8ab7e5a71 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new b13a37063b 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new f9b6f18b58 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new ffea2be109 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new e2334317a3 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new da04dd4ad6 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 2893da73d0 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new f162c75445 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new 450dba408f 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new fb299534fa 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new b587bd1a09 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new e7ae2b8611 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new 9f180d0e31 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new 33806840f7 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new ef2e9588b0 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new 39591ef5b0 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new 7d0626d324 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new 75d570ebc7 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new 82ac1dc699 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new bee99267e9 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new faecab2920 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new 8b8ff3a1eb 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new 890f16d736 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new 1d19ede380 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new c2f88d5eec 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] new a49c0c8def 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] new b102ef40f8 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits new 5d9637292d 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] new b177736be4 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] new 95c67254cb 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 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 (1d5276e723) \ 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 2064 -> 1984 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2540 bytes 03-build_abe-binutils/console.log.xz | Bin 35428 -> 35204 bytes 04-build_abe-gcc/console.log.xz | Bin 205328 -> 203048 bytes 06-build_abe-linux/console.log.xz | Bin 8252 -> 8316 bytes 07-build_abe-glibc/console.log.xz | Bin 240812 -> 241428 bytes 08-build_abe-gdb/console.log.xz | Bin 34700 -> 34764 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3832 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2612 -> 2744 bytes 11-check_regression/console.log.xz | Bin 5224 -> 3992 bytes 11-check_regression/results.compare | 15 ---------- 11-check_regression/results.compare2 | 52 +++++++++++++++++++++------------- 12-update_baseline/console.log | 42 +++++++++++++-------------- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- mail/changes-list-long.txt | 18 ++---------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 ++++++++++++--------- manifest.sh | 25 +++++++--------- sumfiles/gdb.log.0.xz | Bin 1983660 -> 1992308 bytes sumfiles/gdb.log.1.xz | Bin 15128 -> 15136 bytes sumfiles/gdb.sum | 18 ++++++------ sumfiles/gdb.sum.0 | 18 ++++++------ sumfiles/gdb.sum.1 | 4 +-- 24 files changed, 108 insertions(+), 122 deletions(-)