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 d2e7194c1a0b 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/g [...] discards d9306bf8e9f3 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] discards b8b8468343b3 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] discards 91f32df52c62 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards 34c2ca4c8986 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards fa49b527419b 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards e24885bd584d 135: onsuccess: #38: 1: Success after binutils/gcc/linux/g [...] discards 8541d66e078d 134: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards a7743019499e 133: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards a2bb879d4e10 132: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards c16909bf4652 131: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards 19dc8cae904b 130: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards 25b3ebf4cc06 129: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 0cfd7908fa5a 128: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 305bdfc55315 127: force: #27: : Failure after baseline build: no new commits discards 2889d2e43a1e 126: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 7e1422344d6f 125: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards ba9ed6c7af23 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 4d2f63ffb286 123: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 1b9b9df83c42 122: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 6d72301653c0 121: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 647fdb455d4e 120: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 66b5fcd8ee2f 119: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards a44af8f7a8ef 118: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards 205978ae78d7 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 9372cecd180b 116: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 5637002dc27d 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 65bbe593661f 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 371fcb6c3e08 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gd [...] discards 521b02fa180f 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 75445da3a9c3 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 16bf393d391d 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards cecd1b399bb5 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 9d2d8cf3a75b 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] discards 8c0409cda523 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards a4d642a104c3 106: onsuccess: #121: 1: Success after binutils/gcc/linux/ [...] discards 2622e1cc5d24 105: onsuccess: #120: 1: Success after binutils/gcc/linux/ [...] discards 716842a0bbb9 104: onsuccess: #119: 1: Success after binutils/gcc/linux/ [...] discards c51b7bf128a5 103: onsuccess: #118: 1: Success after binutils/gcc/linux/ [...] discards e8aafd4da746 102: onsuccess: #117: 1: Success after binutils/gcc/linux/ [...] discards 3a5fbc1ca6a8 101: onsuccess: #116: 1: Success after binutils/gcc/linux/ [...] discards 6aece82b7055 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 3 [...] discards 3a13a3a31e1b 99: onsuccess: #114: 1: Success after binutils/gcc/linux/g [...] discards 8a38ed561d4c 98: onsuccess: #112: 1: Success after binutils/gcc/linux/g [...] discards 4ba67a15e1a5 97: onsuccess: #111: 1: Success after binutils/gcc/linux/g [...] discards 284b938ffc0f 96: onsuccess: #110: 1: Success after binutils/gcc/linux/g [...] discards 9caf5b2f4aac 95: onsuccess: #109: 1: Success after binutils/gcc/linux/g [...] discards 9d96fc3deeca 94: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] discards 250e16826755 93: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] discards eeddb350325b 92: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] discards 7fe98706f1c1 91: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] discards 990322c1855f 90: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] discards 7fda446d5b66 89: onsuccess: #102: 1: Success after binutils/gcc/linux/g [...] discards 5e697ca5dc4d 88: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] discards b4963bdb3757 87: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] discards dd3b8a905d11 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gl [...] discards da264fd8e029 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gd [...] discards af5e9fbb8b3d 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] discards 7e07683fe415 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 [...] discards 1ba5f0a8b6c9 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gd [...] discards 9f83cf503634 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] discards cb0c6245d8e6 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] discards 2df0f0fbf59b 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] discards 7e4d56cf9a59 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] discards ccbefe0d4b0f 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gd [...] discards c6ffabd78493 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gd [...] discards 3bbeb03bcab4 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gl [...] discards 698f13a20419 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] discards 89fd461ae70e 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] discards 7bc6f72ebc7a 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gl [...] discards 469b002c96ea 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gl [...] discards 8fb936f8019b 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gl [...] discards d68eb65d1193 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] discards 73d0640e1b89 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gd [...] discards 23feaec5fdbc 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] discards e83c9b90c486 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gd [...] discards 41f845d1cdb9 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gl [...] discards 824440a285b9 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gd [...] discards ec43b9d5b742 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] discards 82863c25d51c 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gl [...] discards 38e77a8af2eb 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gd [...] discards aed5484c3f81 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gd [...] discards c11559481103 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gl [...] discards e2f3aab6eac7 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 2793167ab358 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards bda0bda9fa4f 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 8e1e97e289d2 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gd [...] discards 60be99d80712 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards a48985e71ba7 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] discards fe70adeb0a00 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] discards 151b0cef8a92 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gl [...] discards abf253a33fb5 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gl [...] discards 27f2a1d33b1b 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gl [...] discards c5265c4351e8 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gl [...] discards d5203cf1fc3b 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards 79622154a1b6 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] discards 39a35ef3235d 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gl [...] discards 2bfb1c2dc1fd 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] discards 09cfabbb481a 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] discards 07d18e03e562 42: onsuccess: #53: 1: Success after linux: 3008 commits discards aaf1e1391d92 41: onsuccess: #51: 1: Success after binutils: 12 commits new 700bee02a0b2 41: onsuccess: #51: 1: Success after binutils: 12 commits new 624aa37b18a7 42: onsuccess: #53: 1: Success after linux: 3008 commits new 2bf78a189fbf 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] new 0c638771f082 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] new 8bb3412213aa 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gl [...] new 32eb8ddd20ce 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] new 5a4a33503234 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new fd6f9e242327 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gl [...] new b6c777eed43e 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gl [...] new 8d72aab0fd3e 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gl [...] new f594da6d5bc3 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gl [...] new e7cda6e5b664 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] new 0896a0ef5665 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] new 7135c384535f 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new f4886f5278b8 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gd [...] new a157905d8c1e 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 65c663105011 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 3263eeb8befe 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 75670a5fa026 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gl [...] new e0865d77cb19 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gd [...] new 897eb4c43f2e 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gd [...] new 1150c4027f2f 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gl [...] new e5d91f5c98eb 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] new 6c5748013bc3 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gd [...] new ffd6be1f90d1 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gl [...] new f81f909c4701 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gd [...] new 8a7635eeb9fe 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] new 42a8a9972972 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gd [...] new 9c5463cfaa83 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] new 717422a502eb 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gl [...] new cdf81d07b212 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gl [...] new 19d91221819a 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gl [...] new fc85c93e814e 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] new 15ac4225cfdb 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] new 3e093a746e18 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gl [...] new 2472b4c9f314 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gd [...] new 73e6bd0b5a78 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gd [...] new b30d990c5135 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] new 2563fefd2b0e 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] new 292aff4c0a71 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] new 3b323abbb410 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] new 013a6ec116e9 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gd [...] new 2b12fddc308e 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 [...] new a1c296372117 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] new a8753da1b39c 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gd [...] new 5379cddb637b 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gl [...] new a76408d05ba5 87: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] new 699799aa7257 88: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] new f11be77d09b8 89: onsuccess: #102: 1: Success after binutils/gcc/linux/g [...] new cabd780fe7a1 90: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] new d433e9bdd731 91: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] new 0a7a38a71835 92: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] new b9b218f9a63f 93: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] new 6f7208ea4236 94: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] new 83594a377af5 95: onsuccess: #109: 1: Success after binutils/gcc/linux/g [...] new e9a7bdeb9861 96: onsuccess: #110: 1: Success after binutils/gcc/linux/g [...] new 0c2be1934c4e 97: onsuccess: #111: 1: Success after binutils/gcc/linux/g [...] new fc8af7447e7f 98: onsuccess: #112: 1: Success after binutils/gcc/linux/g [...] new d64c51c12b53 99: onsuccess: #114: 1: Success after binutils/gcc/linux/g [...] new f566ad9c845b 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 3 [...] new 6d2b1d5e678c 101: onsuccess: #116: 1: Success after binutils/gcc/linux/ [...] new b9f24e1eb066 102: onsuccess: #117: 1: Success after binutils/gcc/linux/ [...] new 5e7f26c3e4a8 103: onsuccess: #118: 1: Success after binutils/gcc/linux/ [...] new 4b60836b7858 104: onsuccess: #119: 1: Success after binutils/gcc/linux/ [...] new 4d52a6372d8a 105: onsuccess: #120: 1: Success after binutils/gcc/linux/ [...] new 5aaa87742583 106: onsuccess: #121: 1: Success after binutils/gcc/linux/ [...] new aa65a4e71d41 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 9a324c28b62d 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] new 3c4969ac4bc9 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new f57507506e3a 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new dee1bf36606b 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new c261eb37db85 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 8e84df281eef 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gd [...] new 685fcb9f07e0 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 8700ea710325 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new af1ae4596452 116: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 3531ae9cc237 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 4888a0fa19e1 118: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 7c45dbc6aea5 119: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 95a8e9a71b0e 120: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new c64703d7b215 121: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 2238179327e3 122: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 7c528ab84bad 123: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new e281827eb67b 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 15c2224d1c9b 125: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new f08e3cb8630e 126: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new 1b7f59fe5f36 127: force: #27: : Failure after baseline build: no new commits new cf437656430c 128: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 57fed1111a33 129: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 7344a3b5a0a1 130: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new 525810f621d8 131: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 77531509da3b 132: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new 55e6dc44f408 133: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new 6126293afcb3 134: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new b25be3945311 135: onsuccess: #38: 1: Success after binutils/gcc/linux/g [...] new 45e7368e69da 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new a5729d7843cb 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 6c463ced297b 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new ca4fe155f64c 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] new 24dc5dbd226a 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] new 754011faea8a 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/g [...] new 7bb8d991250b 142: onsuccess: #46: 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 (d2e7194c1a0b) \ 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 2084 -> 2064 bytes 02-prepare_abe/console.log.xz | Bin 2564 -> 2540 bytes 03-build_abe-binutils/console.log.xz | Bin 35276 -> 35080 bytes 04-build_abe-gcc/console.log.xz | Bin 204244 -> 203904 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8200 -> 8708 bytes 07-build_abe-glibc/console.log.xz | Bin 240808 -> 241708 bytes 08-build_abe-gdb/console.log.xz | Bin 34844 -> 34600 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3808 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2912 -> 2756 bytes 11-check_regression/console.log.xz | Bin 4600 -> 5216 bytes 11-check_regression/results.compare | 4 +-- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 62 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 55 ++++++++++++++++-------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 +++++++++--------- manifest.sh | 38 ++++++++++----------- sumfiles/gdb.log.xz | Bin 14628 -> 14624 bytes sumfiles/gdb.sum | 4 +-- 26 files changed, 110 insertions(+), 105 deletions(-)