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 3607ae78c5 257: force: #148: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards d8c9616097 256: force: #147: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 642c871d7f 255: force: #145: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards bcae62c6a7 254: force: #142: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards d9ded2d102 253: force: #141: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards d721829d20 252: onsuccess: #134: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 642d421849 251: onsuccess: #133: 0: [TCWG CI] https://ci.linaro.org/job [...] discards 08de2ec22e 250: force: #132: : [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards c8998d0b7b 249: onsuccess: #124: 1: [TCWG CI] https://ci.linaro.org/job [...] discards e50d5e68cb 248: onsuccess: #123: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 0484ef7910 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] discards fde739bb83 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 70e5c6d602 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] discards 69ff8eeb74 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits discards c45a4b2dd8 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] discards cde665ffc2 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] discards a5ec381849 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits discards 06946319c4 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] discards 4a6962188b 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] discards b9e5fef81b 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards c57298d546 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards f50f3d27a7 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards 9100b6c1ed 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 017a39630a 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 208bb20d90 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards 376dc0804d 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards b646c3db37 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards b2cfaf8caf 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards b7aa42f30b 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards eca857faf4 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards 2d349eb0b2 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards 41dd0d667a 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards bca570d779 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards 439a966b0a 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards ead4c8e4fb 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 8d60f3b8cc 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards e286f12c2e 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards 88e1c413c2 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 581b670f46 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards e5a4a107b9 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards a9be8a7b31 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards 558d46f61f 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards c50afaf024 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards 983154891a 214: onsuccess: #47: 1: Success after gdb: 21 commits discards cb91f62c91 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards bd56dba28b 212: force: #45: 1: Success after gdb: 22 commits discards 3e8393bfd3 211: onsuccess: #44: 1: Success after linux: 26 commits discards cf70232b67 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards 0adb3fc335 209: force: #37: 1: Success after baseline build: no new commits discards 9e89173d0f 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 2e11eb0643 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 9fed0354a0 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 3e82aac749 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 26ba61f0b7 204: force: #26: : Failure after baseline build: no new commits discards 7a0cb9f6c4 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 5ae6851f17 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 5cb16296de 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 1fb9d78fff 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 7e537e287d 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 1dd3ada1dd 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards b037bdcc6e 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 55eed6e461 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 0aa281d15d 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards e33ecce892 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 95c32603ea 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 5655010616 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 5f2723eb08 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 9c6d2b63a4 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 5d81e90e3c 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards dffe08164a 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 76b940a299 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 23dc905831 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards d82d685ee2 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards f117c64bda 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards 3bf778311f 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards 8e17a5000c 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards f36e4eca02 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards 816c988ff2 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards 616362d4fb 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards f826b7e939 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards 0e0fb48b6e 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards 167a4627d5 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards b93ddf4980 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards 142e4c9f3f 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards 9dccad5412 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards 3135d81f8c 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards c6d3f98a1a 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards ec751f5b5a 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards 8a04aa6e3a 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards 5d263c03f6 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards 08c4690f39 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards 580ac52df2 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards 3d98f12b7b 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards 4bb0762bfe 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards 94607f30d8 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards 61406706ab 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards 927cfded9e 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards 071da87dea 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards 51f0459d53 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards 811237b2aa 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards c32f5f01e1 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new 6f7b56d3e2 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new a156c48ef7 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 33b10f847b 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new 503e87e5d0 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new b6c7c0f3b5 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new bb7bfcb456 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new 07e47ede25 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new 3711caea18 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new 8f4e48142e 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new 7037fb233a 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new a7aae09650 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new ab24a9559a 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new 125e6c7e61 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new 6060aefcdf 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new bfbee8f699 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new eebea278a4 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 9548cc34fb 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new 27ced1636b 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new 2df729d651 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new 5e3ef3d7ef 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new d053998e2f 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new a773624588 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new bdfd31569a 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new 0499a7c6e9 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new f58909eb92 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new 61a7ef6ff0 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new 21673444c5 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new f442926d69 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new 8c09f33f1b 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 46208db20f 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new fbc04a956b 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new d1d5561e0b 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 6b5f4779cd 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 4f54cafbe4 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new a262708c7c 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 4ae995b19e 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new dd751c7bd4 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new c07b8a7941 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 9603ea9573 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 12fb78a65f 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 76b687d92d 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new dfba14d4f1 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new cc60b12e45 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 9420bf621d 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 8dd2ba0254 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 82da32418e 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new c198274aa6 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 76fc1d8394 204: force: #26: : Failure after baseline build: no new commits new 6b60f9c2e6 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 280f103e47 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new b136b07b86 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 707e0738e8 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 50886b0858 209: force: #37: 1: Success after baseline build: no new commits new f94c0d0544 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new d56d7444d2 211: onsuccess: #44: 1: Success after linux: 26 commits new b0c789e248 212: force: #45: 1: Success after gdb: 22 commits new 917e1a5847 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new 7d907247f6 214: onsuccess: #47: 1: Success after gdb: 21 commits new 80e51f6eb5 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new 340b95231c 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new 4530fd4fae 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new 4b61714b8d 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new 4b80ece3cc 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 017e7b20cb 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new c291f5d7f7 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 9c944843b0 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new 96178d2599 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 29ecbb1d89 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new f6de91b97b 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new b75cefe2a4 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new c663deaf9f 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new 78b7a0fda9 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new 93a78bc0f4 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new ade3b31785 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new 12a7a56034 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new 583f0f0e44 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new c0051ad26b 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new 52702c6dab 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 0d016beb96 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new f393902a74 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new 7deed05933 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new f75cb632ad 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new 448835eecf 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] new b10572eeef 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] new 53aeb2d6a9 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits new 710e34d499 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] new c0d06ee501 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] new 8068778d99 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits new 5aaf6b21f3 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] new bf8111f890 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new c02ffa94f0 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] new c365e4121e 248: onsuccess: #123: 1: [TCWG CI] https://ci.linaro.org/job [...] new 37fb77097b 249: onsuccess: #124: 1: [TCWG CI] https://ci.linaro.org/job [...] new 34e0a7a743 250: force: #132: : [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 1a864c7ee4 251: onsuccess: #133: 0: [TCWG CI] https://ci.linaro.org/job [...] new a2f7795ccf 252: onsuccess: #134: 1: [TCWG CI] https://ci.linaro.org/job [...] new 75e842fa29 253: force: #141: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new c65c86054e 254: force: #142: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new f8d54fddae 255: force: #145: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new 754d17c0fd 256: force: #147: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new 140c4e444b 257: force: #148: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new e5146ebe53 258: onsuccess: #149: 1: [TCWG CI] https://ci.linaro.org/job [...]

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 (3607ae78c5) \ 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: 00-sumfiles/gdb.log.0.xz | Bin 1911992 -> 0 bytes 00-sumfiles/gdb.log.1.xz | Bin 15408 -> 0 bytes 00-sumfiles/gdb.log.2.xz | Bin 14544 -> 0 bytes 00-sumfiles/gdb.log.xz | Bin 0 -> 1895816 bytes 00-sumfiles/gdb.sum.0 | 113914 ------------------------------- 00-sumfiles/gdb.sum.1 | 122 - 00-sumfiles/gdb.sum.2 | 110 - 01-reset_artifacts/console.log.xz | Bin 2200 -> 2220 bytes 02-prepare_abe/console.log.xz | Bin 2456 -> 2456 bytes 03-build_abe-binutils/console.log.xz | Bin 38068 -> 37036 bytes 04-build_abe-gcc/console.log.xz | Bin 205468 -> 205704 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8668 -> 8432 bytes 07-build_abe-glibc/console.log.xz | Bin 245284 -> 241368 bytes 08-build_abe-gdb/console.log.xz | Bin 36272 -> 35312 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3864 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4808 -> 4672 bytes 10-build_abe-check_gdb/flaky.xfail | 1 + 11-check_regression/console.log.xz | Bin 8044 -> 3376 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 3952 +- 12-update_baseline/console.log | 48 +- git/gcc_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 16 +- manifest.sh | 12 +- sumfiles/flaky.xfail | 7 - sumfiles/gdb.sum | 272 +- sumfiles/xfails.xfail | 10 +- 29 files changed, 389 insertions(+), 118095 deletions(-) delete mode 100644 00-sumfiles/gdb.log.0.xz delete mode 100644 00-sumfiles/gdb.log.1.xz delete mode 100644 00-sumfiles/gdb.log.2.xz create mode 100644 00-sumfiles/gdb.log.xz delete mode 100644 00-sumfiles/gdb.sum.0 delete mode 100644 00-sumfiles/gdb.sum.1 delete mode 100644 00-sumfiles/gdb.sum.2 create mode 100644 10-build_abe-check_gdb/flaky.xfail delete mode 100644 sumfiles/flaky.xfail