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 671d351a9c 250: force: #132: : [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 9d24192c08 249: onsuccess: #124: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 2962936a3d 248: onsuccess: #123: 1: [TCWG CI] https://ci.linaro.org/job [...] discards cb6340b40a 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] discards b51e5e7d3a 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 16b47a6876 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] discards efe7608150 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits discards b4b2626ee4 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] discards def04463da 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] discards 42b82d2f89 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits discards b3eaac0aaa 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] discards 1b7aa2911e 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] discards 8815210958 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards 0a28866d11 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards 96c644c572 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards 66964d60ad 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 3056af79a1 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards ddcd307aa2 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards 7c6b862e1b 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 88acd0f0aa 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards 4352f091b5 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards e3780dce65 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards a8450e9767 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards c7fe0e64f5 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards 8088a6e317 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards a050002093 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards ad97a8b973 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 82dab9e8e2 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards f7db60c256 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards 19e8654640 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards d730f456f6 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 37cee54de7 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 22eb44a0fb 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards d41dee6a04 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards 4d22a73613 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards 0797c5d045 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards ee2bbd36ff 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 3980f0b41e 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards 8aec1c19bb 212: force: #45: 1: Success after gdb: 22 commits discards 6fc94c45b7 211: onsuccess: #44: 1: Success after linux: 26 commits discards 324de733b0 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards 56d3f6edca 209: force: #37: 1: Success after baseline build: no new commits discards 27448b1d95 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards d008ad4f3e 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 6c1db24b48 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 8166f6db4f 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards d064bdd438 204: force: #26: : Failure after baseline build: no new commits discards 097583790b 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards ac3d05e40f 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 88718bbdc9 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards d23b3e9caa 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards e595483111 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards a3bdb75686 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards c5de27f1ad 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 4dbc2f49ae 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 5310a79cb9 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 777dc16c24 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 7bf76fc37e 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards dbe1c23194 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 2d02578f08 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 11f69b7e9e 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards e67c8248f2 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 58c4393b7d 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 18ff9054eb 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 0a4e6eebf1 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 08c249317f 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards b1c36b39ba 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards f07f93c78b 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards 38a677702f 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards 10a598151f 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards afabd1b5eb 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards cb3d113a1b 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards 91bbac2b5b 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards d389a04625 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards c5dc6eb4b0 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards 6647c85707 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards 43ebb4d86f 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards 0fe194801d 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards a1840ef12b 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards 41232c3b23 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards 914a2c3b7d 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards 2a9d8063b8 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards 645a735863 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards e845b15af9 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards bb3a78d8bd 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards 1c5cae0886 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards c5fa89220f 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards f15646c3db 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards 9020bbbc6f 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards 012247d799 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards 219287dc2c 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards eb20aa4d43 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards 97c3f261a1 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 45e2cdd24c 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards 96eb6dabd4 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards abdc6b2ab9 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards bfdfff0e43 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards 2313a04edf 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards 7d1d2a732b 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards d789a6cece 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards 2ca24b1ec6 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new 81e2996b3f 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new d13b6856c6 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new a6d9368ee2 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 5d49f28948 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new 49e8bdaeaf 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 8e122f35e5 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new df0b27117a 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new 31d452cce6 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new 965e4fca45 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 474dbec886 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new 91a1b5ec8f 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new 750795d59d 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 1adcc5fc19 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new 074af96f94 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new e63aa5634e 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new 7d106a3de5 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new 7125285621 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new f895b3a484 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new cbed4eae47 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new 79d0453118 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new 475aae6d23 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new f63b8f5dc9 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new ecbc2a8d9c 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 5d9a1cb7b6 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new 7238b76d31 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new a83802da67 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new abbe2909c1 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new 2ab127d7d3 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new 72c96fee71 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new a8f05dc5a6 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new db07c3bea7 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new d3bfb7f724 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new 0dbf7848c2 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new 5a0b9a09a5 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new d2aec7fc5c 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new 5d5a8a9e27 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 6866d4e928 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 82bd0ee30d 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new f110557d63 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 182142ab83 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new b150c8f6b7 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new e53c7a66ec 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new e4d13a85f2 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 8db451edce 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 678c2f0e2b 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 8ed9f5f978 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 4174046e4b 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new b9bc3246b8 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 707607d9e5 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 8024aa1652 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 37e1afe9c9 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 776399b86a 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 62a9f85625 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 61de74e141 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 9a2bc18937 204: force: #26: : Failure after baseline build: no new commits new 0d8548db56 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 182660a3b6 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 932e3edca7 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new bbd5129d2c 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new f4de4cc258 209: force: #37: 1: Success after baseline build: no new commits new a7f34782ff 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new 2dd9799f5f 211: onsuccess: #44: 1: Success after linux: 26 commits new cf71606e33 212: force: #45: 1: Success after gdb: 22 commits new 8d89382597 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new c1218e3f86 214: onsuccess: #47: 1: Success after gdb: 21 commits new d0e868df67 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new eb789798b8 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new 3bee7b0d57 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new 2c09c1ec96 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new 740eeeffab 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 473f1fb63d 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 25bc5045fd 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 05ae5710ea 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new 2ee3cd642d 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 9530e780e2 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 51265777b2 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new d3cad4521a 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new 7d2771858c 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new 60e07075af 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new b85565baf2 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new 4929c5fb8f 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new 9466ebf066 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new c9438b886f 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new 4d0db8c941 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new 94563731fe 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new f877a0fac6 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new 22ae56ee84 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new d065206c9b 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new 1da7430b6e 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new 735c01b38b 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] new 59a3a9710f 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] new dc556e34ef 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits new b9de1b2034 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] new 2b8d759360 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] new e1083e2729 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits new b746e8a144 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] new 75614e42da 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new ab6ecbed4f 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] new 365702f46b 248: onsuccess: #123: 1: [TCWG CI] https://ci.linaro.org/job [...] new 424b49498a 249: onsuccess: #124: 1: [TCWG CI] https://ci.linaro.org/job [...] new 8aa055c37f 250: force: #132: : [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 321360b1b2 251: onsuccess: #133: 0: [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 (671d351a9c) \ 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 2176 -> 2044 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 35028 -> 34996 bytes 04-build_abe-gcc/console.log.xz | Bin 203564 -> 202772 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8948 -> 8508 bytes 07-build_abe-glibc/console.log.xz | Bin 242400 -> 241504 bytes 08-build_abe-gdb/console.log.xz | Bin 34820 -> 34712 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3832 bytes 10-build_abe-check_gdb/console.log.xz | Bin 1328 -> 1328 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 976 -> 548 bytes 11-check_regression/results.regressions | 3 --- 12-update_baseline/console.log | 46 ++++++++++++++++---------------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- mail/check-regression-status.txt | 2 +- manifest.sh | 33 +++++++++++++---------- results | 3 --- 23 files changed, 50 insertions(+), 51 deletions(-) delete mode 100644 11-check_regression/results.regressions