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 321360b1b2 251: onsuccess: #133: 0: [TCWG CI] https://ci.linaro.org/job [...] discards 8aa055c37f 250: force: #132: : [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 424b49498a 249: onsuccess: #124: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 365702f46b 248: onsuccess: #123: 1: [TCWG CI] https://ci.linaro.org/job [...] discards ab6ecbed4f 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 75614e42da 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards b746e8a144 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] discards e1083e2729 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits discards 2b8d759360 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] discards b9de1b2034 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] discards dc556e34ef 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits discards 59a3a9710f 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] discards 735c01b38b 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] discards 1da7430b6e 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards d065206c9b 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards 22ae56ee84 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards f877a0fac6 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 94563731fe 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 4d0db8c941 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards c9438b886f 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 9466ebf066 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards 4929c5fb8f 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards b85565baf2 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards 60e07075af 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards 7d2771858c 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards d3cad4521a 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards 51265777b2 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards 9530e780e2 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 2ee3cd642d 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 05ae5710ea 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards 25bc5045fd 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards 473f1fb63d 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 740eeeffab 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 2c09c1ec96 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards 3bee7b0d57 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards eb789798b8 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards d0e868df67 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards c1218e3f86 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 8d89382597 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards cf71606e33 212: force: #45: 1: Success after gdb: 22 commits discards 2dd9799f5f 211: onsuccess: #44: 1: Success after linux: 26 commits discards a7f34782ff 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards f4de4cc258 209: force: #37: 1: Success after baseline build: no new commits discards bbd5129d2c 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 932e3edca7 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 182660a3b6 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 0d8548db56 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 9a2bc18937 204: force: #26: : Failure after baseline build: no new commits discards 61de74e141 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 62a9f85625 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 776399b86a 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 37e1afe9c9 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 8024aa1652 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 707607d9e5 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards b9bc3246b8 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 4174046e4b 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 8ed9f5f978 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 678c2f0e2b 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 8db451edce 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards e4d13a85f2 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards e53c7a66ec 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards b150c8f6b7 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 182142ab83 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards f110557d63 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 82bd0ee30d 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 6866d4e928 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 5d5a8a9e27 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards d2aec7fc5c 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards 5a0b9a09a5 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards 0dbf7848c2 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards d3bfb7f724 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards db07c3bea7 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards a8f05dc5a6 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards 72c96fee71 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards 2ab127d7d3 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards abbe2909c1 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards a83802da67 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards 7238b76d31 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards 5d9a1cb7b6 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards ecbc2a8d9c 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards f63b8f5dc9 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards 475aae6d23 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards 79d0453118 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards cbed4eae47 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards f895b3a484 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards 7125285621 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards 7d106a3de5 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards e63aa5634e 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards 074af96f94 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards 1adcc5fc19 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards 750795d59d 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards 91a1b5ec8f 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards 474dbec886 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards 965e4fca45 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 31d452cce6 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards df0b27117a 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards 8e122f35e5 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards 49e8bdaeaf 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards 5d49f28948 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards a6d9368ee2 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards d13b6856c6 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 981832edf6 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 67a9c257b2 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new bc64cf9f3f 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new 2a53afbd7e 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new da5e4b01a6 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new a2553b3e6f 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new 8d0b38f8e8 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new 0d859e2954 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 2fe16e3a17 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new e1a26b737d 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new ad1c000106 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 02b86b49c1 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new 27d95236e8 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new acd4342b37 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new ed3d3e1808 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new 2cf996184f 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new be0aca687d 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new 55045e7863 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new 22bde883d6 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new 1c6e35ab1c 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new 830e4f9a30 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new 5208b3f9d7 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 88b26d15a0 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new d8abcd968e 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new 3573334983 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new 21ab1c2941 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new dc2953fdaf 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new 36fc891338 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new 951fe4c79f 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new ffc238e932 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new 3679ab5931 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new dd69a6a12a 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new af3593628c 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new e21423e4c1 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new bbc7dbbe16 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 0ccbbc2cf0 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 1804a9b825 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 6ca0c2af8d 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 2e46fb5bb3 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 9be4802d1b 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new f3845ce15e 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 5b3fd145f4 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 3ba0be7823 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 5080e27ac1 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 1f208d4fc8 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 48bcb4c6ee 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 77b98d6409 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 8cce525efe 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new a6ea4c937c 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 1aff614615 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new c3677780c3 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 981ed5a6dd 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 3b85eaf1f3 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 97989d2003 204: force: #26: : Failure after baseline build: no new commits new b2e1e02b6d 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new df89b6b210 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 831cd5a1e8 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 01982f02c6 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 89f8b9f817 209: force: #37: 1: Success after baseline build: no new commits new a4b4a0e658 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new 96603fa5e0 211: onsuccess: #44: 1: Success after linux: 26 commits new 47e8a59694 212: force: #45: 1: Success after gdb: 22 commits new c01e80b237 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new 1dfa0ef4f5 214: onsuccess: #47: 1: Success after gdb: 21 commits new 9269ceb3fc 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new 119a82aa5c 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new 00e5024e8f 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new b62539f844 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new e3fc967336 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new eb97ace041 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 1b329d7057 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new a3cbb6deac 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new dd694eb4a3 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 34ea9d6959 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 954fc89b7e 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new df5552d14d 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new 304c2ac3ac 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new 3914eb4606 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new 50a054d79d 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new 97951127ad 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new 96de014cae 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new 2d500a5715 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new ecc41ef2c8 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new 04a0234376 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 83b47283bc 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new b2b77494ef 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new e6b5740294 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new 51825ed185 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new dade27e32a 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] new 9f66097fef 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] new cc77390c0b 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits new e5e1e30723 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] new 8368f65531 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] new 8c30818ea4 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits new 0588b2d400 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] new d0b0d79c0b 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new 07da871676 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] new 3c7d770dbe 248: onsuccess: #123: 1: [TCWG CI] https://ci.linaro.org/job [...] new 0cd58f85b0 249: onsuccess: #124: 1: [TCWG CI] https://ci.linaro.org/job [...] new 8224056397 250: force: #132: : [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 0ddf5caf39 251: onsuccess: #133: 0: [TCWG CI] https://ci.linaro.org/job [...] new 0d271fa401 252: onsuccess: #134: 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 (321360b1b2) \ 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 2044 -> 2016 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2488 bytes 03-build_abe-binutils/console.log.xz | Bin 34996 -> 35256 bytes 04-build_abe-gcc/console.log.xz | Bin 202772 -> 204160 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8508 -> 8244 bytes 07-build_abe-glibc/console.log.xz | Bin 241504 -> 241576 bytes 08-build_abe-gdb/console.log.xz | Bin 34712 -> 34600 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3900 bytes 10-build_abe-check_gdb/console.log.xz | Bin 1328 -> 3056 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 548 -> 548 bytes 12-update_baseline/console.log | 46 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 30 +- results | 2 +- sumfiles/gdb.log.0.xz | Bin 0 -> 1916908 bytes sumfiles/gdb.log.1.xz | Bin 0 -> 784 bytes sumfiles/gdb.sum | 110120 +++++++++++++++++++++++++++++++ sumfiles/gdb.sum.0 | 110116 ++++++++++++++++++++++++++++++ sumfiles/gdb.sum.1 | 14 + sumfiles/xfails.xfail | 0 26 files changed, 220295 insertions(+), 45 deletions(-) create mode 100644 sumfiles/gdb.log.0.xz create mode 100644 sumfiles/gdb.log.1.xz create mode 100644 sumfiles/gdb.sum create mode 100644 sumfiles/gdb.sum.0 create mode 100644 sumfiles/gdb.sum.1 create mode 100644 sumfiles/xfails.xfail