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 cacea0e9d2 256: force: #147: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 692d712583 255: force: #145: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 7c449bcb12 254: force: #142: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 6123d77743 253: force: #141: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards ac45ef944b 252: onsuccess: #134: 1: [TCWG CI] https://ci.linaro.org/job [...] discards a053357023 251: onsuccess: #133: 0: [TCWG CI] https://ci.linaro.org/job [...] discards ddf62e544b 250: force: #132: : [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 39a8888217 249: onsuccess: #124: 1: [TCWG CI] https://ci.linaro.org/job [...] discards a1ab874f74 248: onsuccess: #123: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 6ffed6d68c 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 5beee7b8ed 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 8617d157da 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] discards eb2ed5842d 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits discards 8d019a80d9 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] discards 6a61f75e7e 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] discards 5509636fd7 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits discards 05d787f280 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] discards 1989aa6485 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] discards dc352ba820 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards 5ec440ee0e 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards eee32b2c3b 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards bad6a570bf 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards e0c65b4740 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 2c4c837e3b 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards 8b96fdc770 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 1c4ab60aa1 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards 661b1cc3b7 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards c72800318b 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards 2464ec90f0 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards 585324b495 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards 9b63046507 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards 134c9929ac 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards 8060967d05 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards f111e8913e 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 56c2245283 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards b3520b03da 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards 04fa2990a8 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 861e6a6d5d 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 02ac38568a 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards 7068908bfb 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards 59189e2c6f 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards 05549632fe 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards 85cc4df097 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 7a4b44cf8b 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards be4b3c5e87 212: force: #45: 1: Success after gdb: 22 commits discards 352642fc73 211: onsuccess: #44: 1: Success after linux: 26 commits discards 40609a8e31 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards 681181ddca 209: force: #37: 1: Success after baseline build: no new commits discards 8cdc6dca1f 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 66b8339ef7 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards af1f4b5994 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards be3e58b426 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 984ae7de5a 204: force: #26: : Failure after baseline build: no new commits discards 97827119c5 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 130c570e84 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards ea877178b7 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards ed4f0cd695 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards e8badb9b2e 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 4e1758f93b 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 93ae874bfd 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards fb17a52bcd 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 70cbd4b094 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 202b8fb8e2 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards cf7b684256 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards bf14e39c74 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 3605e6ef41 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 5c94675cb4 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards d15215def2 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards c0cbb3cc05 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 74e25d1638 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 50e5d5e49c 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 1c4200f49e 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 74e753ffea 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards 4cb3ef765d 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards 81a65ff473 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards a467e9b35e 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards 93cd04c7fd 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards b4987f1b25 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards 2af8e3ecfc 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards 55bbcfc6d9 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards a66f487717 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards 32193b3049 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards 1b1ea5822e 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards 8003370a69 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards e086ce9a2d 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards ef0dd7da1b 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards dd383220ff 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards 16bac3368f 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards fa20b317d3 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards c7f2e8ad60 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards af07968b2e 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards 758dde04f4 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards 20ae1ee6da 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards debd388b6a 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards dcb8004bbe 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards 72a3b29b26 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards 1782979757 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards 50acb317fa 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards c874976d41 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 94668c608d 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards 9a89d21598 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new 869b501b13 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new c32f5f01e1 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new 811237b2aa 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 51f0459d53 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new 071da87dea 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new 927cfded9e 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 61406706ab 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new 94607f30d8 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new 4bb0762bfe 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new 3d98f12b7b 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new 580ac52df2 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new 08c4690f39 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new 5d263c03f6 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new 8a04aa6e3a 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new ec751f5b5a 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new c6d3f98a1a 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new 3135d81f8c 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 9dccad5412 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new 142e4c9f3f 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new b93ddf4980 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new 167a4627d5 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new 0e0fb48b6e 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new f826b7e939 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new 616362d4fb 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new 816c988ff2 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new f36e4eca02 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new 8e17a5000c 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new 3bf778311f 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new f117c64bda 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new d82d685ee2 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 23dc905831 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 76b940a299 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new dffe08164a 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 5d81e90e3c 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 9c6d2b63a4 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 5f2723eb08 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 5655010616 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 95c32603ea 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new e33ecce892 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 0aa281d15d 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 55eed6e461 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new b037bdcc6e 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 1dd3ada1dd 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 7e537e287d 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 1fb9d78fff 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 5cb16296de 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 5ae6851f17 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 7a0cb9f6c4 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 26ba61f0b7 204: force: #26: : Failure after baseline build: no new commits new 3e82aac749 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 9fed0354a0 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 2e11eb0643 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 9e89173d0f 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 0adb3fc335 209: force: #37: 1: Success after baseline build: no new commits new cf70232b67 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new 3e8393bfd3 211: onsuccess: #44: 1: Success after linux: 26 commits new bd56dba28b 212: force: #45: 1: Success after gdb: 22 commits new cb91f62c91 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new 983154891a 214: onsuccess: #47: 1: Success after gdb: 21 commits new c50afaf024 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new 558d46f61f 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new a9be8a7b31 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new e5a4a107b9 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new 581b670f46 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 88e1c413c2 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new e286f12c2e 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 8d60f3b8cc 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new ead4c8e4fb 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 439a966b0a 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new bca570d779 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new 41dd0d667a 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new 2d349eb0b2 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new eca857faf4 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new b7aa42f30b 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new b2cfaf8caf 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new b646c3db37 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new 376dc0804d 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new 208bb20d90 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new 017a39630a 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 9100b6c1ed 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new f50f3d27a7 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new c57298d546 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new b9e5fef81b 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new 4a6962188b 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] new 06946319c4 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] new a5ec381849 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits new cde665ffc2 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] new c45a4b2dd8 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] new 69ff8eeb74 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits new 70e5c6d602 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] new fde739bb83 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new 0484ef7910 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] new e50d5e68cb 248: onsuccess: #123: 1: [TCWG CI] https://ci.linaro.org/job [...] new c8998d0b7b 249: onsuccess: #124: 1: [TCWG CI] https://ci.linaro.org/job [...] new 08de2ec22e 250: force: #132: : [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 642d421849 251: onsuccess: #133: 0: [TCWG CI] https://ci.linaro.org/job [...] new d721829d20 252: onsuccess: #134: 1: [TCWG CI] https://ci.linaro.org/job [...] new d9ded2d102 253: force: #141: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new bcae62c6a7 254: force: #142: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new 642c871d7f 255: force: #145: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new d8c9616097 256: force: #147: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new 3607ae78c5 257: force: #148: 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 (cacea0e9d2) \ 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 1881908 -> 1911992 bytes 00-sumfiles/gdb.log.1.xz | Bin 64956 -> 15408 bytes 00-sumfiles/gdb.log.2.xz | Bin 0 -> 14544 bytes 00-sumfiles/gdb.sum.0 | 3661 +++++++++++++- 00-sumfiles/gdb.sum.1 | 8432 +------------------------------ 00-sumfiles/gdb.sum.2 | 110 + 01-reset_artifacts/console.log.xz | Bin 2220 -> 2200 bytes 02-prepare_abe/console.log.xz | Bin 2472 -> 2456 bytes 03-build_abe-binutils/console.log.xz | Bin 38792 -> 38068 bytes 04-build_abe-gcc/console.log.xz | Bin 207448 -> 205468 bytes 06-build_abe-linux/console.log.xz | Bin 8388 -> 8668 bytes 07-build_abe-glibc/console.log.xz | Bin 242100 -> 245284 bytes 08-build_abe-gdb/console.log.xz | Bin 36192 -> 36272 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3904 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4640 -> 4808 bytes 10-build_abe-check_gdb/flaky.xfail | 1 - 11-check_regression/console.log.xz | Bin 10672 -> 8044 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 15 - 11-check_regression/results.compare | 17 +- 11-check_regression/results.compare2 | 354 +- 11-check_regression/results.regressions | 21 - 11-check_regression/trigger-bisect | 3 - 12-update_baseline/console.log | 52 +- git/gcc_rev | 2 +- jenkins/notify.sh | 2 +- mail/check-regression-status.txt | 2 +- mail/results.compare | 17 +- mail/results.regressions | 21 - manifest.sh | 8 +- results | 21 - sumfiles/flaky.xfail | 7 + sumfiles/gdb.sum | 3656 +++++++++++++- sumfiles/xfails.xfail | 12 + 34 files changed, 7519 insertions(+), 8896 deletions(-) create mode 100644 00-sumfiles/gdb.log.2.xz create mode 100644 00-sumfiles/gdb.sum.2 delete mode 100644 10-build_abe-check_gdb/flaky.xfail delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions delete mode 100644 11-check_regression/trigger-bisect delete mode 100644 mail/results.regressions create mode 100644 sumfiles/flaky.xfail