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 95c67254cb 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits discards b177736be4 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] discards 5d9637292d 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] discards b102ef40f8 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits discards a49c0c8def 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] discards c2f88d5eec 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] discards 1d19ede380 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards 890f16d736 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards 8b8ff3a1eb 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards faecab2920 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards bee99267e9 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 82ac1dc699 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards 75d570ebc7 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 7d0626d324 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards 39591ef5b0 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards ef2e9588b0 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards 33806840f7 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards 9f180d0e31 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards e7ae2b8611 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards b587bd1a09 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards fb299534fa 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 450dba408f 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards f162c75445 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards 2893da73d0 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards da04dd4ad6 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards e2334317a3 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards ffea2be109 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards f9b6f18b58 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards b13a37063b 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards e8ab7e5a71 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards 8e1e9c42eb 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 72cda742dc 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards 2d999ba0a9 212: force: #45: 1: Success after gdb: 22 commits discards a601a94a65 211: onsuccess: #44: 1: Success after linux: 26 commits discards e2117e8152 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards 9937ef8ed8 209: force: #37: 1: Success after baseline build: no new commits discards 1b8bad70b7 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 1f094cd268 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards e7ecfb5a7a 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 2c8b8b3a23 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 729e771d33 204: force: #26: : Failure after baseline build: no new commits discards 8266156b8b 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards aae6d39a64 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards cd424326df 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 8d8526351a 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 05a6b591ca 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 43e9999671 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 208e1bf0a4 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 94f312a115 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 8ee8948b13 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 0fb6e1a229 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards f316f971a0 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 9e62fd76a0 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards e983af21ce 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 1c05b65920 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards b421fe19b1 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards e4def644d9 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 72f26c03fb 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 8becb9cf8e 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards a88041839b 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards ceed766b96 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards 628919a452 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards d1a5070c7a 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards 6892c82700 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards bb94d93c1d 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards 7c6a5fbd85 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards d1c8fc8dc5 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards babf96c621 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards 326d7452e3 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards 2b776a78c7 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards 980132df2a 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards 8c9651d963 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards 2fe9684bf0 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards 6e97b57511 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards 3118dbf462 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards 56ac28d294 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards f41f245849 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards 1b571e7276 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards 9904b91cd5 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards 8317257883 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards a1035ecb5b 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards d05edc6be9 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards 7bf934cb43 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards 368da5d5b1 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards dec860a57f 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards 3380caeaa6 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards a16a333e1d 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 28c78ce55e 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards f14c0077a2 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards 0b0a07c2e1 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards a768de8a84 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards 963f183445 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards ef801f0b75 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards c1eac4d91b 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards 95701718d0 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards 433b47901b 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards 9ab6a6c64e 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards bace74dd61 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards ed13ba979f 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards 4c4571df03 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards 07b28a674e 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new 6c356dc5e9 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new eeff592f2b 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new 8b25317e5a 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 04e813e57d 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new 5299c3832f 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new 58f801b4dd 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new de681d9743 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new 44f4e44037 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 36252e9796 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 447b2951ae 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new b361fa10ca 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 8dfaba13c7 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new 9388649441 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new 246f0cfa6a 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new 636faae866 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 0ccbe84cee 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new 303be71b97 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new 244ea8937b 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 970beab388 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new 9b760ff4b6 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new 028dcff40c 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new 0c1a17aae7 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new 86c823be2e 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new 8a20614ffd 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new 9fc13b06ce 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new c90b80325f 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new e70178da8e 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new 08649a5376 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new 7e4fadfeae 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new c5de6ab572 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new 0700424bd5 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new fadda48599 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new 1e0e3ba4f3 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new 03cb6dbbfb 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new e063a805c9 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new 5ffb17ff69 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new 555a22256d 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new 3287b22e1c 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new eb63d8f823 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new 6a5f851cbe 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new b626968507 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new bc2eab12d8 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 260f023993 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 4239580d5a 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 31df5b1b45 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new f15ee841ab 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 4c65c13aa0 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 631ab5574a 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new f05889dd64 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new bfede98a20 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 70d98f4edd 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 9e66c0f377 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 5a3381d692 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 3618e18ecf 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 651063195a 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new d5e2e494f9 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new f39e4e33fb 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 1ecaec4e80 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new ef531a8d00 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 5da67d9411 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new c45b091d33 204: force: #26: : Failure after baseline build: no new commits new eb4001cbcf 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 365c122362 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new df50cce495 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 8ee88383c5 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new efa71bc302 209: force: #37: 1: Success after baseline build: no new commits new e914517d4c 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new 462d05a055 211: onsuccess: #44: 1: Success after linux: 26 commits new 06642a428f 212: force: #45: 1: Success after gdb: 22 commits new a63209264a 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new ccf2104dfe 214: onsuccess: #47: 1: Success after gdb: 21 commits new c608cb50e1 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new f9db332900 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new bbfff59a8d 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new 0aec0451a4 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new cf2b667869 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new c804d5d343 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new c44bfc6fd0 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 306cdc2afe 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new 5e745c425c 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 1b11780972 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new be0d03d28d 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new b8056ccd81 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new 6af8ef6ba1 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new b62e66932a 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new d0d669cfe6 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new 7dd5694828 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new 409f592fe2 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new a1237cbb55 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new 776c43ed5d 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new 9c1a12fca8 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 397701c790 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new 0102b21c0c 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new 891e73f402 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new 1ff28223e1 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new 39eccc32d4 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] new 2f7c428c1b 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] new 093e39b41f 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits new 2de925a9f8 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] new c5d9d57e39 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] new 9cbd40898e 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits new ea965abcd8 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...]
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 (95c67254cb) \ 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 1984 -> 2060 bytes 02-prepare_abe/console.log.xz | Bin 2540 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 35204 -> 35360 bytes 04-build_abe-gcc/console.log.xz | Bin 203048 -> 203868 bytes 06-build_abe-linux/console.log.xz | Bin 8316 -> 8800 bytes 07-build_abe-glibc/console.log.xz | Bin 241428 -> 240720 bytes 08-build_abe-gdb/console.log.xz | Bin 34764 -> 34892 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3848 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2744 -> 2752 bytes 11-check_regression/console.log.xz | Bin 3992 -> 5172 bytes 11-check_regression/results.compare2 | 66 ++++++++++++++------------------ 12-update_baseline/console.log | 70 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 28 ++++++++++---- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 25 ++++++------ manifest.sh | 33 ++++++++-------- sumfiles/gdb.log.0.xz | Bin 1992308 -> 2007704 bytes sumfiles/gdb.log.1.xz | Bin 15136 -> 15132 bytes sumfiles/gdb.sum | 20 +++++----- sumfiles/gdb.sum.0 | 20 +++++----- sumfiles/gdb.sum.1 | 2 +- 26 files changed, 140 insertions(+), 136 deletions(-)