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 ce8d05910c 248: onsuccess: #123: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 4298fb8f02 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 19b78bac13 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards fa6f75cd5d 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] discards 0bef3524cf 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits discards 0f03e2ae2e 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] discards 47ae3312a9 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] discards 9b4ab62035 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits discards e3c851761a 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] discards f7402faa34 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] discards 984367cae7 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards c899f45b6b 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards d57da848f9 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards 43eab87efb 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 3776c42d72 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 1d46dfda13 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards a12132f1a7 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 20950c3cfe 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards 972e0c2ad2 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards fed2349361 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards 2410823a26 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards ac67247ed2 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards 48f49c0dd8 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards ffae145758 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards 4fd74b1e3f 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards fd06c954fd 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards e4ecc7e76a 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards dc9a2138cd 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards 52fc0926ff 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 7d4d2cd5fd 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 89599d7498 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards 841901459e 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards 65876d3d82 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards 8d99932fa3 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards 58c448154b 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 93fbaddbb0 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards 2a943eac29 212: force: #45: 1: Success after gdb: 22 commits discards e245c3be23 211: onsuccess: #44: 1: Success after linux: 26 commits discards 831e1256c3 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards ab6e4b7136 209: force: #37: 1: Success after baseline build: no new commits discards 6761563119 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards d493c00a1a 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards c5a12aade8 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards f087968685 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 0ddfb18165 204: force: #26: : Failure after baseline build: no new commits discards 9b2ee76912 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 1fe4b30b05 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 636568f2ff 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 315772aecf 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 1cb2408d59 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards f9b87308fc 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 82f6877925 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards b7322112e6 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 11d2c57125 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 1ebeb6bac1 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 76c46b3d67 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 49088e362e 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards c09b77536e 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 0e88cbdd4c 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 67a1d2743e 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards b8e336ed49 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 49c4d84ac3 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 49f26cdd19 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards f01dcfdb5f 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 22dce6564d 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards ad7b765bd3 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards 56d628c018 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards ef7016e515 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards e194c8a13e 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards e8db73d042 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards ab504adf2e 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards 5a61616896 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards c6f862fa4c 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards c1f82637fe 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards 3ddd32976a 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards 0b6d7a5ae5 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards f8fe1e20e5 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards 6a74d72126 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards 585df6bc7d 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards 5b649e0235 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards 95a206f2dc 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards 144ded2ad4 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards f87c54f70c 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards 2438c9e615 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards a4faff61a6 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards e5700fec50 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards 17b795517c 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards 8050513ec2 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards ec9a1cbf97 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards 0757d8ffec 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards 00b6e66ddc 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 45fa885f18 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards 0ebdd9c642 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards 3a3af9d58e 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards 4514492811 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards 7cb90b7e55 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards 75dd9b92f1 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards a3c4bbe738 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards 2db3b5320e 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards 7263a02746 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards 7d42b979da 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new 7157bf6cec 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new 7f60665eeb 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new 688819c4cd 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new fb71054ddf 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new c3511a99c1 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 3cceb706d7 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new 34c90dd2ec 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 21a86897a0 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new f63818d752 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new 11c48a3fab 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new 6517af6284 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 01f0743301 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new 282a209280 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new 1dbc9df90e 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 84fc507e0b 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new b9c4ab8663 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new fa221ddf36 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new 9b96bdf93a 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new 2234a4f148 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new 9201f4df2d 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new a0f9e9f409 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new ac2b9ba500 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new 82a2060f11 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new 4897db2398 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new d98a3223d0 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 5b24cabe04 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new 150c253119 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new 7dcfcbd568 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new 63df55c7e3 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new d0657b5a34 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new adcddf3c73 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new 200bf4ae5c 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new a4fdb5dd4c 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new 9ddfaa9ca2 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new 092f99c69e 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new 835d94f512 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new a6951c666a 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new e592087eb7 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 7a2d4ad119 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 47ce27d570 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new b78a39cf24 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 716ad9ea41 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new eed6cf08e5 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new b1fc6b2ce4 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new cdcbb350a6 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new a784c74109 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new aa1b43f97d 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 6ae3859f67 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 7ea5ad25d1 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 4ee730364c 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 30977d998b 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new b77882d3c5 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new c92fd7e8dd 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 998a9743ee 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new b78af7a551 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 0346cc9885 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new c8ee59e43e 204: force: #26: : Failure after baseline build: no new commits new 531c53ac87 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new cc27704e98 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 85d59668fd 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new c17d020d35 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new e6646a4584 209: force: #37: 1: Success after baseline build: no new commits new 7f08b22095 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new efbc80d797 211: onsuccess: #44: 1: Success after linux: 26 commits new cf70dc984a 212: force: #45: 1: Success after gdb: 22 commits new 6f4b56b517 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new 2ae44da37e 214: onsuccess: #47: 1: Success after gdb: 21 commits new 087fd2e7b1 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new d096b52029 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new 3fb686a0ff 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new 8f82c76647 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new e045f12103 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 872e56e60e 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new babdc070fb 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 405e63991c 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new 823b4f97b9 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 0041506d1c 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 8f8e9f3506 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new a1773eab91 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new 12c1b76539 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new 9b285987fd 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new d35fdd2b85 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new e1405b143d 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new 14b36649ef 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new ec7666ec73 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new ffe169fb2e 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new 7266631a22 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 7af81f3d5a 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new c67e1cc450 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new 15cc140c6a 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new 964c325974 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new 2565d23dca 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] new e7003e2515 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] new 9ad8fae07d 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits new 0774e4a10e 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] new 0c5d48a36c 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] new eb3a68dfb4 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits new 9f75926c11 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] new cf3a463b4a 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new 0d4ec3d469 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] new 4ffc410c59 248: onsuccess: #123: 1: [TCWG CI] https://ci.linaro.org/job [...] new 8a359fd74b 249: onsuccess: #124: 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 (ce8d05910c) \ 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 2252 -> 2068 bytes 02-prepare_abe/console.log.xz | Bin 2600 -> 2524 bytes 03-build_abe-binutils/console.log.xz | Bin 35156 -> 35052 bytes 04-build_abe-gcc/console.log.xz | Bin 203064 -> 204672 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8600 -> 8792 bytes 07-build_abe-glibc/console.log.xz | Bin 240760 -> 240564 bytes 08-build_abe-gdb/console.log.xz | Bin 34884 -> 34648 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3844 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2856 -> 2648 bytes 11-check_regression/console.log.xz | Bin 1776 -> 5868 bytes 11-check_regression/results.compare | 24 +- 11-check_regression/results.compare2 | 779 +++++++++++++++++- 12-update_baseline/console.log | 42 +- 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/results.compare | 24 +- manifest.sh | 32 +- sumfiles/gdb.log.0.xz | Bin 1936368 -> 1968004 bytes sumfiles/gdb.log.1.xz | Bin 20316 -> 15140 bytes sumfiles/gdb.log.2.xz | Bin 5276 -> 0 bytes sumfiles/gdb.log.3.xz | Bin 5400 -> 0 bytes sumfiles/gdb.sum | 1431 +++++++++++--------------------- sumfiles/gdb.sum.0 | 1435 +++++++++++---------------------- sumfiles/gdb.sum.1 | 251 +----- sumfiles/gdb.sum.2 | 173 ---- sumfiles/gdb.sum.3 | 182 ----- 31 files changed, 1808 insertions(+), 2577 deletions(-) delete mode 100644 sumfiles/gdb.log.2.xz delete mode 100644 sumfiles/gdb.log.3.xz delete mode 100644 sumfiles/gdb.sum.2 delete mode 100644 sumfiles/gdb.sum.3