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 ea965abcd8 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] discards 9cbd40898e 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits discards c5d9d57e39 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] discards 2de925a9f8 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] discards 093e39b41f 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits discards 2f7c428c1b 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] discards 39eccc32d4 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] discards 1ff28223e1 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards 891e73f402 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards 0102b21c0c 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards 397701c790 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 9c1a12fca8 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 776c43ed5d 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards a1237cbb55 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 409f592fe2 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards 7dd5694828 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards d0d669cfe6 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards b62e66932a 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards 6af8ef6ba1 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards b8056ccd81 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards be0d03d28d 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards 1b11780972 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 5e745c425c 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 306cdc2afe 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards c44bfc6fd0 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards c804d5d343 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards cf2b667869 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 0aec0451a4 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards bbfff59a8d 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards f9db332900 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards c608cb50e1 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards ccf2104dfe 214: onsuccess: #47: 1: Success after gdb: 21 commits discards a63209264a 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards 06642a428f 212: force: #45: 1: Success after gdb: 22 commits discards 462d05a055 211: onsuccess: #44: 1: Success after linux: 26 commits discards e914517d4c 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards efa71bc302 209: force: #37: 1: Success after baseline build: no new commits discards 8ee88383c5 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards df50cce495 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 365c122362 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards eb4001cbcf 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards c45b091d33 204: force: #26: : Failure after baseline build: no new commits discards 5da67d9411 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards ef531a8d00 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 1ecaec4e80 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards f39e4e33fb 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards d5e2e494f9 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 651063195a 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 3618e18ecf 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 5a3381d692 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 9e66c0f377 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 70d98f4edd 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards bfede98a20 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards f05889dd64 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 631ab5574a 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 4c65c13aa0 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards f15ee841ab 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 31df5b1b45 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 4239580d5a 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 260f023993 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards bc2eab12d8 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards b626968507 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards 6a5f851cbe 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards eb63d8f823 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards 3287b22e1c 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards 555a22256d 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards 5ffb17ff69 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards e063a805c9 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards 03cb6dbbfb 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards 1e0e3ba4f3 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards fadda48599 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards 0700424bd5 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards c5de6ab572 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards 7e4fadfeae 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards 08649a5376 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards e70178da8e 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards c90b80325f 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards 9fc13b06ce 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards 8a20614ffd 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards 86c823be2e 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards 0c1a17aae7 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards 028dcff40c 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards 9b760ff4b6 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards 970beab388 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards 244ea8937b 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards 303be71b97 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards 0ccbe84cee 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards 636faae866 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 246f0cfa6a 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards 9388649441 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards 8dfaba13c7 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards b361fa10ca 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards 447b2951ae 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards 36252e9796 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards 44f4e44037 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards de681d9743 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards 58f801b4dd 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards 5299c3832f 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards 04e813e57d 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards 8b25317e5a 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards eeff592f2b 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new 4cf0ee8de0 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new f94ac1da83 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 560c436913 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new ea81f7e16e 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new 6592157e73 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new 2e65186da3 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new 031f894e67 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 3e9996d5f9 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 59968ac5e4 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new 6aae0be70f 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 355f32be22 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new d12a0e46cb 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new 0756e2e400 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new fa74c010c8 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 23b16d4613 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new 96ff5b259d 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new d1b61b69dc 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 4fbe56cefe 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new bd5995549b 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new 8df9761b5f 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new 47f481f209 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new b2a9482e61 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new f67afc4e16 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new 061402460f 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new d39829fea6 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new 6d5e1e8759 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new 5cfdbf334b 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new 35ccecbea7 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 8d07842166 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new b0dad22231 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new fd1cc9871a 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new d9092ffdd3 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new 3f19ffb4af 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new 5afae13c65 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new efa0871e5d 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new 770a105874 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new f035f0aaba 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new 47bbf224aa 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new 6af729e48c 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new cec8944cbd 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new bd27d76cea 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 156e664459 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 3fc4546941 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new d0f595c52f 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new f6a1e31a3d 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 1847233e3e 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new bd12eff3ff 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new b8998e3f71 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 373778287b 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new d69b5dabb2 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new e7a42fabec 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 4315481bd4 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 8a0d327ef1 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 296f5a1e25 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new c64dcb898d 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 9d43365333 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new e0ad26074d 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 1f61991179 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new d3f533f8d0 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 2562ec7183 204: force: #26: : Failure after baseline build: no new commits new 4584cccea8 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 75d7a07d3c 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 9dd9e2e24c 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 57ea8969bb 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new db40e0a6db 209: force: #37: 1: Success after baseline build: no new commits new 054a52cc8e 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new cc2bc34277 211: onsuccess: #44: 1: Success after linux: 26 commits new 18300479d7 212: force: #45: 1: Success after gdb: 22 commits new 2f2cefbcab 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new fa69c77802 214: onsuccess: #47: 1: Success after gdb: 21 commits new 4b4bc63c1e 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new 6ef14f7538 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new fcc9d9082c 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new 937ebee9a5 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new 6864db3da2 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 305837ecb0 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 56a84187ea 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new fe4c51f2b4 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new 20f6ccd210 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 191cce1f3f 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 49755b98f3 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new 92e2ceefc5 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new e95d9e310f 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new 108d698a1b 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new 8678b0569a 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new 84a96764d8 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new 53b8e524d0 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new 3f7abf6f0b 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new ab0b488fa8 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new 281dfef30d 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 5b5b76890c 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new ca2d4b2a24 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new a592ecc632 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new cf59be03fa 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new 4aded4a280 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] new b7d92261db 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] new 639e72943c 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits new 8a376d5845 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] new 536bd4fd8a 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] new e5db4ada98 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits new 46c70158b6 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] new 905ae4246a 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...]

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 (ea965abcd8) \ 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 2060 -> 2192 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 35360 -> 35520 bytes 04-build_abe-gcc/console.log.xz | Bin 203868 -> 203728 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8800 -> 8864 bytes 07-build_abe-glibc/console.log.xz | Bin 240720 -> 241556 bytes 08-build_abe-gdb/console.log.xz | Bin 34892 -> 34848 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3848 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2752 -> 2840 bytes 11-check_regression/console.log.xz | Bin 5172 -> 1588 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 91 +- 12-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- jenkins/notify.sh | 3 + mail/changes-list-long.txt | 22 - mail/changes-list-short.txt | 1 - mail/check-regression-status.txt | 1 + mail/last_good.sh | 30 - mail/short-diag.txt | 1 - manifest.sh | 28 +- sumfiles/gdb.log.0.xz | Bin 2007704 -> 1946612 bytes sumfiles/gdb.log.1.xz | Bin 15132 -> 20324 bytes sumfiles/gdb.log.2.xz | Bin 0 -> 5388 bytes sumfiles/gdb.log.3.xz | Bin 0 -> 5428 bytes sumfiles/gdb.sum | 1688 +++++++++++++++++++-------------- sumfiles/gdb.sum.0 | 1688 +++++++++++++++++++-------------- sumfiles/gdb.sum.1 | 251 ++++- sumfiles/gdb.sum.2 | 182 ++++ sumfiles/gdb.sum.3 | 182 ++++ 31 files changed, 2651 insertions(+), 1593 deletions(-) create mode 100755 jenkins/notify.sh delete mode 100644 mail/changes-list-long.txt delete mode 100644 mail/changes-list-short.txt create mode 100644 mail/check-regression-status.txt delete mode 100644 mail/last_good.sh delete mode 100644 mail/short-diag.txt create mode 100644 sumfiles/gdb.log.2.xz create mode 100644 sumfiles/gdb.log.3.xz create mode 100644 sumfiles/gdb.sum.2 create mode 100644 sumfiles/gdb.sum.3