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 0375286895 253: force: #141: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 042a4e37f6 252: onsuccess: #134: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 1d4981ebcc 251: onsuccess: #133: 0: [TCWG CI] https://ci.linaro.org/job [...] discards a7093094b8 250: force: #132: : [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards dd7f93f283 249: onsuccess: #124: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 7b1ed666da 248: onsuccess: #123: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 2acdf0f770 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 346c86aebe 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 71f180f647 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] discards ef3503c20f 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits discards 1a0a8369ce 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] discards 35b1e6065e 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] discards f2cd5f2092 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits discards 4615560553 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] discards 08eb189997 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] discards 52ca51e441 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards a1de94f84a 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards 4372d56f00 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards 0af089b12e 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards e11910c9b8 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards b6bbfc31e1 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards 7983672824 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 6110957d31 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards 73b2cba73c 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards cab9f50a30 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards 6784bb694a 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards ef43dfe17b 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards ee645c7a3c 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards 45f27b68cd 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards 80221065f8 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 19be6342ce 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 10c7e7e8f6 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards 9dbfd8e55d 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards dc74c11b6b 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 593dd7c1da 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards ffb70f2810 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards adf1be95b4 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards 097ba28281 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards 31dfce6302 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards 5e1935465c 214: onsuccess: #47: 1: Success after gdb: 21 commits discards ff1c679e71 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards b8b1fcb75d 212: force: #45: 1: Success after gdb: 22 commits discards 32dc54c642 211: onsuccess: #44: 1: Success after linux: 26 commits discards c41ccaad3f 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards 6f67d3a549 209: force: #37: 1: Success after baseline build: no new commits discards cbac815f38 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 994a930329 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 431f3365ca 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards eed5e19f6b 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 5e652758fa 204: force: #26: : Failure after baseline build: no new commits discards 1d891b9b2f 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 9ae2f59f22 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards a306298f05 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 4d75dc5c52 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 63a4237d9a 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards f4c39b3601 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 1fd310439f 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 8c8604aa30 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 14265daa64 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards b19cb0a9b8 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards f9bf7a0456 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards a8d46f0846 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 9ce60a041f 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 6c8f5b33a4 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 3be3839a50 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 21078bb7f1 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards c91d0c0308 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 3d79b3c77f 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 5221e61850 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards d48fc6f5ed 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards 3cac9f6a03 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards 4bfa015203 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards 40c8d5d270 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards 4273b8aaf5 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards 1145a64298 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards 9f0b3f1730 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards 62b3467db1 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards 3a946a21fd 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards b303950ad6 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards 3efba78ecd 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards 8bb56fbef9 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards 42afc1255c 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards 3b1b77b848 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards 041d283756 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards f9b39bda58 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards 179ffd84a9 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards e086bf7bf3 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards bf764c66a1 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards 34fbc82edb 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards ff71db3d33 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards cf342f8492 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards 17be0fdcf0 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards 3ee8eb5ce3 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards e226b1af12 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards 1e00c95a40 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards 0c4da86ff7 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 041395584c 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards 083a5def92 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards 1510021eda 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards 1d87239306 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards 555cd4dfa2 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new c939dfc6e8 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new 7afc8b2d37 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 0d3490a6c1 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new bd2834c7c8 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new 3117983a4b 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new d7ee6b5c0b 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 2cc1a083de 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new 989199340c 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new 3e1f2df44e 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 04f5ecaeb6 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new 6434d3b9c0 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new 6bba825674 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new 02cbb4906d 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new 5325111835 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new e6ba6f8bac 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new 8e5aa75701 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new e8ffc8748d 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new c380908d28 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new 175033710e 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new 4ba73b667b 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 5832248e5f 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new 22c0da7462 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new 72c755b223 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new d945a01471 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new c5f1422483 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new 33e5b1fdd7 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new 28f6ffb668 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new 35ebee49f5 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new 3d8f5cf35d 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new 20f1c9ef41 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new 9b779d57c7 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new 40e5e5a0f5 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new 5b656f54f4 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new d61092c3c6 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new f0e28cf49d 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 7acf49b68b 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new b0643b4c3d 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new fa31d5310c 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new dfef9780b1 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 83bcf219df 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new ec9263f258 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 049ab51611 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 7b3bc5ec1c 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 7d3aec4846 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new a8a7990a8b 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 1d55693266 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 62868c9ddb 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new e7577fe0fb 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 37eee8fadb 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new f38ed8cd84 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new b12367e126 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 6e8c8244a9 204: force: #26: : Failure after baseline build: no new commits new c5c56cc1df 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 325038d263 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 6e33e0118a 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new cd38b703c5 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new bfbb434927 209: force: #37: 1: Success after baseline build: no new commits new 839c72d00a 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new dd6335627e 211: onsuccess: #44: 1: Success after linux: 26 commits new e0586c22cd 212: force: #45: 1: Success after gdb: 22 commits new a186f251e5 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new 86f4c6bc9a 214: onsuccess: #47: 1: Success after gdb: 21 commits new 130a97b562 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new 9b5b9ff1b9 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new a4d5183e96 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new 7f3c73b78a 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new 0b79c7d8c5 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new e4b82fe7e0 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 04e81f3c43 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 9b57550945 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new a130459818 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 2e40519968 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new ad2d7e3429 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new f6c02eb024 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new 4077e9701a 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new 50bb4f7211 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new 4205bf5d57 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new b69248c7c4 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new 2712a66970 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new 04791d6118 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new 86337b26fe 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new 471cc32aae 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 32e394f90c 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new ae95849ada 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new 00f97bc15a 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new 818d46de8e 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new a5d33f75de 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] new 2defc498f4 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] new 9b85f74187 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits new f40148fdc2 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] new b9643c2a40 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] new 503a40c634 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits new 7fdcb20dc2 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] new d835bdd8d7 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new 3b7e51907f 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] new 3c01ee956d 248: onsuccess: #123: 1: [TCWG CI] https://ci.linaro.org/job [...] new 0d02187fe0 249: onsuccess: #124: 1: [TCWG CI] https://ci.linaro.org/job [...] new ce4ef0283f 250: force: #132: : [TCWG CI] https://ci.linaro.org/job/tcwg [...] new b95f7fa8d8 251: onsuccess: #133: 0: [TCWG CI] https://ci.linaro.org/job [...] new 781ed0a8a0 252: onsuccess: #134: 1: [TCWG CI] https://ci.linaro.org/job [...] new c699c78787 253: force: #141: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new 82564184de 254: force: #142: 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 (0375286895) \ 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 2164 -> 2172 bytes 02-prepare_abe/console.log.xz | Bin 2448 -> 2440 bytes 03-build_abe-binutils/console.log.xz | Bin 35140 -> 35092 bytes 04-build_abe-gcc/console.log.xz | Bin 204276 -> 204632 bytes 06-build_abe-linux/console.log.xz | Bin 8416 -> 8472 bytes 07-build_abe-glibc/console.log.xz | Bin 241536 -> 241640 bytes 08-build_abe-gdb/console.log.xz | Bin 34900 -> 35352 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3876 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3156 -> 3704 bytes 10-build_abe-check_gdb/flaky.xfail | 1 - 11-check_regression/console.log.xz | Bin 1240 -> 880 bytes 11-check_regression/results.compare | 20 --- 12-update_baseline/console.log | 66 +++---- git/gdb_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 20 --- manifest.sh | 10 +- sumfiles/flaky.xfail | 7 + sumfiles/gdb.log.0.xz | Bin 1972076 -> 1954940 bytes sumfiles/gdb.log.1.xz | Bin 29644 -> 33060 bytes sumfiles/gdb.log.2.xz | Bin 0 -> 15216 bytes sumfiles/gdb.sum | 36 ++-- sumfiles/gdb.sum.0 | 45 +++-- sumfiles/gdb.sum.1 | 329 +++++++++++++++++++++++++++++++--- sumfiles/gdb.sum.2 | 109 +++++++++++ 25 files changed, 498 insertions(+), 149 deletions(-) delete mode 100644 10-build_abe-check_gdb/flaky.xfail create mode 100644 sumfiles/flaky.xfail create mode 100644 sumfiles/gdb.log.2.xz create mode 100644 sumfiles/gdb.sum.2