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 8a359fd74b 249: onsuccess: #124: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 4ffc410c59 248: onsuccess: #123: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 0d4ec3d469 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] discards cf3a463b4a 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 9f75926c11 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] discards eb3a68dfb4 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits discards 0c5d48a36c 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] discards 0774e4a10e 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] discards 9ad8fae07d 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits discards e7003e2515 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] discards 2565d23dca 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] discards 964c325974 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards 15cc140c6a 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards c67e1cc450 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards 7af81f3d5a 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 7266631a22 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards ffe169fb2e 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards ec7666ec73 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 14b36649ef 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards e1405b143d 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards d35fdd2b85 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards 9b285987fd 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards 12c1b76539 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards a1773eab91 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards 8f8e9f3506 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards 0041506d1c 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 823b4f97b9 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 405e63991c 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards babdc070fb 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards 872e56e60e 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards e045f12103 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 8f82c76647 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards 3fb686a0ff 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards d096b52029 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards 087fd2e7b1 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards 2ae44da37e 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 6f4b56b517 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards cf70dc984a 212: force: #45: 1: Success after gdb: 22 commits discards efbc80d797 211: onsuccess: #44: 1: Success after linux: 26 commits discards 7f08b22095 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards e6646a4584 209: force: #37: 1: Success after baseline build: no new commits discards c17d020d35 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 85d59668fd 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards cc27704e98 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 531c53ac87 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards c8ee59e43e 204: force: #26: : Failure after baseline build: no new commits discards 0346cc9885 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards b78af7a551 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 998a9743ee 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards c92fd7e8dd 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards b77882d3c5 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 30977d998b 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 4ee730364c 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 7ea5ad25d1 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 6ae3859f67 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards aa1b43f97d 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards a784c74109 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards cdcbb350a6 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards b1fc6b2ce4 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards eed6cf08e5 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 716ad9ea41 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards b78a39cf24 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 47ce27d570 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 7a2d4ad119 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards e592087eb7 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards a6951c666a 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards 835d94f512 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards 092f99c69e 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards 9ddfaa9ca2 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards a4fdb5dd4c 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards 200bf4ae5c 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards adcddf3c73 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards d0657b5a34 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards 63df55c7e3 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards 7dcfcbd568 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards 150c253119 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards 5b24cabe04 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards d98a3223d0 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards 4897db2398 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards 82a2060f11 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards ac2b9ba500 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards a0f9e9f409 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards 9201f4df2d 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards 2234a4f148 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards 9b96bdf93a 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards fa221ddf36 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards b9c4ab8663 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards 84fc507e0b 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards 1dbc9df90e 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards 282a209280 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards 01f0743301 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards 6517af6284 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 11c48a3fab 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards f63818d752 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards 21a86897a0 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards 34c90dd2ec 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards 3cceb706d7 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards c3511a99c1 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards fb71054ddf 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards 688819c4cd 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards 7f60665eeb 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new b9be44888a 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new 2ca24b1ec6 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new d789a6cece 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 7d1d2a732b 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 2313a04edf 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new bfdfff0e43 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new abdc6b2ab9 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new 96eb6dabd4 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new 45e2cdd24c 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new 97c3f261a1 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new eb20aa4d43 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new 219287dc2c 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new 012247d799 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 9020bbbc6f 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new f15646c3db 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new c5fa89220f 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new 1c5cae0886 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new bb3a78d8bd 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new e845b15af9 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new 645a735863 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new 2a9d8063b8 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new 914a2c3b7d 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new 41232c3b23 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new a1840ef12b 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 0fe194801d 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new 43ebb4d86f 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new 6647c85707 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new c5dc6eb4b0 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new d389a04625 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new 91bbac2b5b 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new cb3d113a1b 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new afabd1b5eb 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new 10a598151f 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new 38a677702f 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new f07f93c78b 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new b1c36b39ba 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new 08c249317f 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 0a4e6eebf1 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 18ff9054eb 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 58c4393b7d 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new e67c8248f2 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 11f69b7e9e 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 2d02578f08 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new dbe1c23194 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 7bf76fc37e 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 777dc16c24 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 5310a79cb9 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 4dbc2f49ae 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new c5de27f1ad 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new a3bdb75686 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new e595483111 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new d23b3e9caa 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 88718bbdc9 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new ac3d05e40f 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 097583790b 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new d064bdd438 204: force: #26: : Failure after baseline build: no new commits new 8166f6db4f 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 6c1db24b48 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new d008ad4f3e 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 27448b1d95 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 56d3f6edca 209: force: #37: 1: Success after baseline build: no new commits new 324de733b0 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new 6fc94c45b7 211: onsuccess: #44: 1: Success after linux: 26 commits new 8aec1c19bb 212: force: #45: 1: Success after gdb: 22 commits new 3980f0b41e 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new ee2bbd36ff 214: onsuccess: #47: 1: Success after gdb: 21 commits new 0797c5d045 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new 4d22a73613 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new d41dee6a04 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new 22eb44a0fb 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new 37cee54de7 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new d730f456f6 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 19e8654640 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new f7db60c256 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new 82dab9e8e2 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new ad97a8b973 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new a050002093 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new 8088a6e317 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new c7fe0e64f5 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new a8450e9767 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new e3780dce65 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new 4352f091b5 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new 88acd0f0aa 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new 7c6b862e1b 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new ddcd307aa2 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new 3056af79a1 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 66964d60ad 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new 96c644c572 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new 0a28866d11 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new 8815210958 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new 1b7aa2911e 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] new b3eaac0aaa 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] new 42b82d2f89 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits new def04463da 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] new b4b2626ee4 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] new efe7608150 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits new 16b47a6876 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] new b51e5e7d3a 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new cb6340b40a 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] new 2962936a3d 248: onsuccess: #123: 1: [TCWG CI] https://ci.linaro.org/job [...] new 9d24192c08 249: onsuccess: #124: 1: [TCWG CI] https://ci.linaro.org/job [...] new 671d351a9c 250: force: #132: : [TCWG CI] https://ci.linaro.org/job/tcwg [...]

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 (8a359fd74b) \ 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 2068 -> 2176 bytes 02-prepare_abe/console.log.xz | Bin 2524 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 35052 -> 35028 bytes 04-build_abe-gcc/console.log.xz | Bin 204672 -> 203564 bytes 06-build_abe-linux/console.log.xz | Bin 8792 -> 8948 bytes 07-build_abe-glibc/console.log.xz | Bin 240564 -> 242400 bytes 08-build_abe-gdb/console.log.xz | Bin 34648 -> 34820 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3908 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2648 -> 1328 bytes 10-build_abe-check_gdb/flaky.xfail | 1 + 11-check_regression/console.log.xz | Bin 5868 -> 976 bytes 11-check_regression/results.compare | 27 - 11-check_regression/results.compare2 | 792 - 11-check_regression/results.regressions | 3 + 12-update_baseline/console.log | 71 +- jenkins/notify.sh | 2 +- mail/check-regression-status.txt | 2 +- mail/results.compare | 27 - manifest.sh | 23 +- results | 5 +- sumfiles/gdb.log.0.xz | Bin 1968004 -> 0 bytes sumfiles/gdb.log.1.xz | Bin 15140 -> 0 bytes sumfiles/gdb.sum | 113740 ----------------------------- sumfiles/gdb.sum.0 | 113736 ---------------------------- sumfiles/gdb.sum.1 | 504 - 25 files changed, 55 insertions(+), 228878 deletions(-) create mode 100644 10-build_abe-check_gdb/flaky.xfail delete mode 100644 11-check_regression/results.compare delete mode 100644 11-check_regression/results.compare2 create mode 100644 11-check_regression/results.regressions delete mode 100644 mail/results.compare delete mode 100644 sumfiles/gdb.log.0.xz delete mode 100644 sumfiles/gdb.log.1.xz delete mode 100644 sumfiles/gdb.sum delete mode 100644 sumfiles/gdb.sum.0 delete mode 100644 sumfiles/gdb.sum.1