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 82564184de 254: force: #142: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards c699c78787 253: force: #141: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 781ed0a8a0 252: onsuccess: #134: 1: [TCWG CI] https://ci.linaro.org/job [...] discards b95f7fa8d8 251: onsuccess: #133: 0: [TCWG CI] https://ci.linaro.org/job [...] discards ce4ef0283f 250: force: #132: : [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 0d02187fe0 249: onsuccess: #124: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 3c01ee956d 248: onsuccess: #123: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 3b7e51907f 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] discards d835bdd8d7 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 7fdcb20dc2 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] discards 503a40c634 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits discards b9643c2a40 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] discards f40148fdc2 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] discards 9b85f74187 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits discards 2defc498f4 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] discards a5d33f75de 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] discards 818d46de8e 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards 00f97bc15a 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards ae95849ada 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards 32e394f90c 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 471cc32aae 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 86337b26fe 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards 04791d6118 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 2712a66970 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards b69248c7c4 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards 4205bf5d57 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards 50bb4f7211 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards 4077e9701a 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards f6c02eb024 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards ad2d7e3429 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards 2e40519968 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards a130459818 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 9b57550945 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards 04e81f3c43 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards e4b82fe7e0 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 0b79c7d8c5 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 7f3c73b78a 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards a4d5183e96 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards 9b5b9ff1b9 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards 130a97b562 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards 86f4c6bc9a 214: onsuccess: #47: 1: Success after gdb: 21 commits discards a186f251e5 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards e0586c22cd 212: force: #45: 1: Success after gdb: 22 commits discards dd6335627e 211: onsuccess: #44: 1: Success after linux: 26 commits discards 839c72d00a 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards bfbb434927 209: force: #37: 1: Success after baseline build: no new commits discards cd38b703c5 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 6e33e0118a 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 325038d263 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards c5c56cc1df 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 6e8c8244a9 204: force: #26: : Failure after baseline build: no new commits discards b12367e126 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards f38ed8cd84 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 37eee8fadb 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards e7577fe0fb 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 62868c9ddb 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 1d55693266 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards a8a7990a8b 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 7d3aec4846 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 7b3bc5ec1c 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 049ab51611 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards ec9263f258 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 83bcf219df 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards dfef9780b1 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards fa31d5310c 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards b0643b4c3d 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 7acf49b68b 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards f0e28cf49d 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards d61092c3c6 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 5b656f54f4 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 40e5e5a0f5 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards 9b779d57c7 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards 20f1c9ef41 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards 3d8f5cf35d 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards 35ebee49f5 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards 28f6ffb668 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards 33e5b1fdd7 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards c5f1422483 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards d945a01471 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards 72c755b223 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards 22c0da7462 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards 5832248e5f 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards 4ba73b667b 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards 175033710e 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards c380908d28 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards e8ffc8748d 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards 8e5aa75701 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards e6ba6f8bac 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards 5325111835 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards 02cbb4906d 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards 6bba825674 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards 6434d3b9c0 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards 04f5ecaeb6 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards 3e1f2df44e 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards 989199340c 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards 2cc1a083de 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards d7ee6b5c0b 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 3117983a4b 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards bd2834c7c8 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards 0d3490a6c1 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards 7afc8b2d37 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 16974117be 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 35def6a8fa 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new 17e3054cde 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new 065d762600 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new 0f72fe4d63 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 80620e5e42 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new c8caf0d3fd 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new 14e118dd13 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 0624547d8e 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new 9639900584 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new 01e1f798d6 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new 24ce48ddc3 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new fd49ef158a 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new 87e7873848 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new 1df90d92c3 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new b3f983114c 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new 3ba628f99c 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new 1ca6b2a0f2 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new 701c8dae42 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 00f83fb814 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new 2948e541a9 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new d4f2da6447 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new e89b2d67c8 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new 3d2f61d419 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new 2ed8885b09 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new 95de7a5b3f 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new 8015240706 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new c11d113368 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new 40da76b36d 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new 5d455b0a01 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new 857c69f922 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new 561a389d49 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 7f258f8e18 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 80caa67ffe 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new a8aad62dfa 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 5a1d108420 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 9162d9ffa1 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 293d7c54b2 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 8bc8c3433f 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 7f04e863b0 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new b5ea68f3af 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new ebdda07e1b 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 1b45f3f68c 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 69e3f3faa4 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new b28dc76c46 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 21b2daf1d7 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 8542867c69 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 37a65c25b2 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 5d4068080e 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new d02a14d250 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 3113a26b09 204: force: #26: : Failure after baseline build: no new commits new a9c593d167 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 8ac9186b67 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 5cfbff1274 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 39ce358891 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new d50706d521 209: force: #37: 1: Success after baseline build: no new commits new a2021ef5c0 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new f1aed95cd1 211: onsuccess: #44: 1: Success after linux: 26 commits new f048859efb 212: force: #45: 1: Success after gdb: 22 commits new 7a9a097b93 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new 725fbce449 214: onsuccess: #47: 1: Success after gdb: 21 commits new 1540c1d552 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new 0d3f47f00c 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new 6ef5d8e54a 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new dd76dfae15 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new 69d556acfd 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 9eabc09fa4 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 0aa38b7d17 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new b2d4d2a419 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new bee01243a8 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new daffef4fac 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 8d33bf914c 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new 66f784eb78 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new 0a4dc1cefe 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new 2c256b6815 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new 5259890996 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new 0a6ed5a74b 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new c48b86950c 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new 20d370abbc 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new 85a8c44746 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new e88fdc2c82 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new fee1e1d0e8 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new 007ffc2c60 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new 6ad15f1721 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new 2fa5da7616 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new bb491b9956 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] new 576f8a1a82 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] new 1bcf3647b3 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits new 70518fa82d 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] new ed15aaf4d8 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] new 0d5a32e9f6 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits new e18bb76184 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] new 1a52e555d7 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new 1908afca4c 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] new 6468bd8844 248: onsuccess: #123: 1: [TCWG CI] https://ci.linaro.org/job [...] new f93f50d2a6 249: onsuccess: #124: 1: [TCWG CI] https://ci.linaro.org/job [...] new dc22eef015 250: force: #132: : [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 7c085984ae 251: onsuccess: #133: 0: [TCWG CI] https://ci.linaro.org/job [...] new 3c37f5c415 252: onsuccess: #134: 1: [TCWG CI] https://ci.linaro.org/job [...] new ab9d15323e 253: force: #141: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new f175ad0cb1 254: force: #142: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new dc8b7a059c 255: force: #145: 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 (82564184de) \ 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 2172 -> 2016 bytes 02-prepare_abe/console.log.xz | Bin 2440 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 35092 -> 37280 bytes 04-build_abe-gcc/console.log.xz | Bin 204632 -> 204344 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8472 -> 8388 bytes 07-build_abe-glibc/console.log.xz | Bin 241640 -> 242084 bytes 08-build_abe-gdb/console.log.xz | Bin 35352 -> 36272 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3892 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3704 -> 4292 bytes 10-build_abe-check_gdb/flaky.xfail | 1 + 11-check_regression/console.log.xz | Bin 880 -> 1788 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 98 +- 12-update_baseline/console.log | 70 +- git/binutils_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 8 +- manifest.sh | 12 +- results | 2 +- sumfiles/flaky.xfail | 7 - sumfiles/gdb.log.0.xz | Bin 1954940 -> 0 bytes sumfiles/gdb.log.1.xz | Bin 33060 -> 0 bytes sumfiles/gdb.log.2.xz | Bin 15216 -> 0 bytes sumfiles/gdb.log.xz | Bin 0 -> 1953300 bytes sumfiles/gdb.sum | 31 +- sumfiles/gdb.sum.0 | 113745 ------------------------------- sumfiles/gdb.sum.1 | 900 - sumfiles/gdb.sum.2 | 109 - sumfiles/xfails.xfail | 100 + 30 files changed, 266 insertions(+), 114829 deletions(-) create mode 100644 10-build_abe-check_gdb/flaky.xfail delete mode 100644 sumfiles/flaky.xfail delete mode 100644 sumfiles/gdb.log.0.xz delete mode 100644 sumfiles/gdb.log.1.xz delete mode 100644 sumfiles/gdb.log.2.xz create mode 100644 sumfiles/gdb.log.xz delete mode 100644 sumfiles/gdb.sum.0 delete mode 100644 sumfiles/gdb.sum.1 delete mode 100644 sumfiles/gdb.sum.2