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_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts.

discards d9af66e8ab0e 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] discards b0620cf68fc5 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] discards a0246767cd8f 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards d98626a730a6 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards 1c61f29d8faf 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards 298e415e787e 135: onsuccess: #38: 1: Success after binutils/gcc/linux/g [...] discards b98779a10d3d 134: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards e464ad234d3a 133: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards f7020a014cd2 132: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards 8831311674ef 131: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards e67d1e980a46 130: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards 907eb82901bd 129: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards be2d28a0fa69 128: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 05cfd2a91000 127: force: #27: : Failure after baseline build: no new commits discards 0d90b548f0d3 126: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 2b55d19da753 125: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards ce1276afdb8f 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 8701290cdfa7 123: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 0b7427d17355 122: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 2a7bad263440 121: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 7a03f66fcb44 120: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards df9a4b4b5260 119: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards 314224ffa78d 118: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards b6393a7cef56 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 723fe021fa19 116: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards d72ed6625f97 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 1b0d6beb12f5 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 6a9454d028df 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gd [...] discards fadaaadb0757 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards dd63dd99fdcc 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 50a82b284c6c 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards ee1377e0b27b 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 357808b6d690 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] discards 3f794f7a3ba8 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 93bfc222588b 106: onsuccess: #121: 1: Success after binutils/gcc/linux/ [...] discards 077e0f26381a 105: onsuccess: #120: 1: Success after binutils/gcc/linux/ [...] discards e5973097892c 104: onsuccess: #119: 1: Success after binutils/gcc/linux/ [...] discards 8e69714ca7ca 103: onsuccess: #118: 1: Success after binutils/gcc/linux/ [...] discards 7c8fe3c0de3b 102: onsuccess: #117: 1: Success after binutils/gcc/linux/ [...] discards 69577644536c 101: onsuccess: #116: 1: Success after binutils/gcc/linux/ [...] discards b6f8adac2277 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 3 [...] discards c67ec38df192 99: onsuccess: #114: 1: Success after binutils/gcc/linux/g [...] discards b123ac3cda60 98: onsuccess: #112: 1: Success after binutils/gcc/linux/g [...] discards 87fcf0091914 97: onsuccess: #111: 1: Success after binutils/gcc/linux/g [...] discards e9f2cdddd8ed 96: onsuccess: #110: 1: Success after binutils/gcc/linux/g [...] discards c8430449304b 95: onsuccess: #109: 1: Success after binutils/gcc/linux/g [...] discards d90110ea83bc 94: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] discards d7e7a2a28ad2 93: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] discards 2a781877f56a 92: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] discards d10a3ea3ac0f 91: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] discards 85b23a909868 90: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] discards b90704d21fc7 89: onsuccess: #102: 1: Success after binutils/gcc/linux/g [...] discards 4cb19e3e3ae8 88: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] discards 4527c82d1c3d 87: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] discards d4f0f9006a4f 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gl [...] discards 94ee140ec3d1 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gd [...] discards 97e958045dfc 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] discards 99dc68d3edb3 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 [...] discards cf09917cc161 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gd [...] discards e29a6eed5bf1 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] discards 7521a7c88ede 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] discards efaa3aaf9286 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] discards 00bf8327de3b 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] discards a2bbd65a7037 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gd [...] discards d4d678d6ffd2 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gd [...] discards 09d0346fc060 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gl [...] discards bfef8d68343e 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] discards 38ad7cd14b2c 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] discards 07d47486aadf 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gl [...] discards 808687d7fc3a 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gl [...] discards 2cff7b7c20c9 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gl [...] discards 6040aae1eea0 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] discards 1270d6211e6b 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gd [...] discards e8905fd18b02 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] discards bc822777f43f 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gd [...] discards 96dc423f6bf4 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gl [...] discards 9e07c2f0ebec 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gd [...] discards 0595efedf140 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] discards a785c293fd57 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gl [...] discards 20625dbeb72f 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gd [...] discards b4e2655c87e8 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gd [...] discards 01bfd16a85ef 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gl [...] discards 29e4f8223b3d 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 1d4e6161e48f 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 3eb6a4d6309f 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards ea638fb289b5 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gd [...] discards 20a1cc2d29df 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards c71639009a9b 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] discards dfcc1f913ebc 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] discards ce478e6437e7 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gl [...] discards 8a94b8a826ba 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gl [...] discards 29c21d42267a 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gl [...] discards 9e126613c3b9 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gl [...] discards f9e146682c9f 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards 0c6f303e7511 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] discards bdfcab9434bc 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gl [...] discards 96f02302ee5e 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] discards 8f6ff8df81bf 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] discards 060820fe9571 42: onsuccess: #53: 1: Success after linux: 3008 commits discards 5b0985a972b0 41: onsuccess: #51: 1: Success after binutils: 12 commits discards 63b7ed5b3cd0 40: onsuccess: #49: 1: Success after linux: 219 commits new f7a56cd734d9 40: onsuccess: #49: 1: Success after linux: 219 commits new aaf1e1391d92 41: onsuccess: #51: 1: Success after binutils: 12 commits new 07d18e03e562 42: onsuccess: #53: 1: Success after linux: 3008 commits new 09cfabbb481a 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] new 2bfb1c2dc1fd 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] new 39a35ef3235d 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gl [...] new 79622154a1b6 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] new d5203cf1fc3b 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new c5265c4351e8 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gl [...] new 27f2a1d33b1b 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gl [...] new abf253a33fb5 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gl [...] new 151b0cef8a92 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gl [...] new fe70adeb0a00 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] new a48985e71ba7 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] new 60be99d80712 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 8e1e97e289d2 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gd [...] new bda0bda9fa4f 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 2793167ab358 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new e2f3aab6eac7 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new c11559481103 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gl [...] new aed5484c3f81 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gd [...] new 38e77a8af2eb 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gd [...] new 82863c25d51c 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gl [...] new ec43b9d5b742 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] new 824440a285b9 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gd [...] new 41f845d1cdb9 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gl [...] new e83c9b90c486 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gd [...] new 23feaec5fdbc 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] new 73d0640e1b89 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gd [...] new d68eb65d1193 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] new 8fb936f8019b 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gl [...] new 469b002c96ea 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gl [...] new 7bc6f72ebc7a 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gl [...] new 89fd461ae70e 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] new 698f13a20419 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] new 3bbeb03bcab4 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gl [...] new c6ffabd78493 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gd [...] new ccbefe0d4b0f 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gd [...] new 7e4d56cf9a59 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] new 2df0f0fbf59b 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] new cb0c6245d8e6 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] new 9f83cf503634 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] new 1ba5f0a8b6c9 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gd [...] new 7e07683fe415 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 [...] new af5e9fbb8b3d 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] new da264fd8e029 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gd [...] new dd3b8a905d11 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gl [...] new b4963bdb3757 87: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] new 5e697ca5dc4d 88: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] new 7fda446d5b66 89: onsuccess: #102: 1: Success after binutils/gcc/linux/g [...] new 990322c1855f 90: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] new 7fe98706f1c1 91: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] new eeddb350325b 92: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] new 250e16826755 93: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] new 9d96fc3deeca 94: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] new 9caf5b2f4aac 95: onsuccess: #109: 1: Success after binutils/gcc/linux/g [...] new 284b938ffc0f 96: onsuccess: #110: 1: Success after binutils/gcc/linux/g [...] new 4ba67a15e1a5 97: onsuccess: #111: 1: Success after binutils/gcc/linux/g [...] new 8a38ed561d4c 98: onsuccess: #112: 1: Success after binutils/gcc/linux/g [...] new 3a13a3a31e1b 99: onsuccess: #114: 1: Success after binutils/gcc/linux/g [...] new 6aece82b7055 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 3 [...] new 3a5fbc1ca6a8 101: onsuccess: #116: 1: Success after binutils/gcc/linux/ [...] new e8aafd4da746 102: onsuccess: #117: 1: Success after binutils/gcc/linux/ [...] new c51b7bf128a5 103: onsuccess: #118: 1: Success after binutils/gcc/linux/ [...] new 716842a0bbb9 104: onsuccess: #119: 1: Success after binutils/gcc/linux/ [...] new 2622e1cc5d24 105: onsuccess: #120: 1: Success after binutils/gcc/linux/ [...] new a4d642a104c3 106: onsuccess: #121: 1: Success after binutils/gcc/linux/ [...] new 8c0409cda523 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 9d2d8cf3a75b 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] new cecd1b399bb5 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 16bf393d391d 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new 75445da3a9c3 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 521b02fa180f 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 371fcb6c3e08 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gd [...] new 65bbe593661f 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 5637002dc27d 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 9372cecd180b 116: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 205978ae78d7 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new a44af8f7a8ef 118: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 66b5fcd8ee2f 119: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 647fdb455d4e 120: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 6d72301653c0 121: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 1b9b9df83c42 122: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 4d2f63ffb286 123: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new ba9ed6c7af23 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 7e1422344d6f 125: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 2889d2e43a1e 126: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new 305bdfc55315 127: force: #27: : Failure after baseline build: no new commits new 0cfd7908fa5a 128: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 25b3ebf4cc06 129: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 19dc8cae904b 130: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new c16909bf4652 131: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new a2bb879d4e10 132: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new a7743019499e 133: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new 8541d66e078d 134: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new e24885bd584d 135: onsuccess: #38: 1: Success after binutils/gcc/linux/g [...] new fa49b527419b 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new 34c2ca4c8986 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 91f32df52c62 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new b8b8468343b3 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] new d9306bf8e9f3 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] new d2e7194c1a0b 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/g [...]

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 (d9af66e8ab0e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...]

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 2036 -> 2084 bytes 02-prepare_abe/console.log.xz | Bin 2492 -> 2564 bytes 03-build_abe-binutils/console.log.xz | Bin 35840 -> 35276 bytes 04-build_abe-gcc/console.log.xz | Bin 203772 -> 204244 bytes 06-build_abe-linux/console.log.xz | Bin 8604 -> 8200 bytes 07-build_abe-glibc/console.log.xz | Bin 241236 -> 240808 bytes 08-build_abe-gdb/console.log.xz | Bin 35320 -> 34844 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3776 -> 3780 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3340 -> 2912 bytes 11-check_regression/console.log.xz | Bin 4464 -> 4600 bytes 11-check_regression/results.compare2 | 4 +-- 12-update_baseline/console.log | 62 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 40 +++++++++++++--------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 +++++++++--------- manifest.sh | 32 +++++++++--------- sumfiles/gdb.log.xz | Bin 14620 -> 14628 bytes sumfiles/gdb.sum | 4 +-- 23 files changed, 97 insertions(+), 89 deletions(-)