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 7bb8d991250b 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/g [...] discards 754011faea8a 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/g [...] discards 24dc5dbd226a 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] discards ca4fe155f64c 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] discards 6c463ced297b 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards a5729d7843cb 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards 45e7368e69da 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards b25be3945311 135: onsuccess: #38: 1: Success after binutils/gcc/linux/g [...] discards 6126293afcb3 134: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards 55e6dc44f408 133: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 77531509da3b 132: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards 525810f621d8 131: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards 7344a3b5a0a1 130: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards 57fed1111a33 129: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards cf437656430c 128: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 1b7f59fe5f36 127: force: #27: : Failure after baseline build: no new commits discards f08e3cb8630e 126: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 15c2224d1c9b 125: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards e281827eb67b 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 7c528ab84bad 123: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 2238179327e3 122: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards c64703d7b215 121: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 95a8e9a71b0e 120: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 7c45dbc6aea5 119: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards 4888a0fa19e1 118: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards 3531ae9cc237 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards af1ae4596452 116: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 8700ea710325 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 685fcb9f07e0 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 8e84df281eef 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gd [...] discards c261eb37db85 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards dee1bf36606b 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards f57507506e3a 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards 3c4969ac4bc9 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 9a324c28b62d 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] discards aa65a4e71d41 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 5aaa87742583 106: onsuccess: #121: 1: Success after binutils/gcc/linux/ [...] discards 4d52a6372d8a 105: onsuccess: #120: 1: Success after binutils/gcc/linux/ [...] discards 4b60836b7858 104: onsuccess: #119: 1: Success after binutils/gcc/linux/ [...] discards 5e7f26c3e4a8 103: onsuccess: #118: 1: Success after binutils/gcc/linux/ [...] discards b9f24e1eb066 102: onsuccess: #117: 1: Success after binutils/gcc/linux/ [...] discards 6d2b1d5e678c 101: onsuccess: #116: 1: Success after binutils/gcc/linux/ [...] discards f566ad9c845b 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 3 [...] discards d64c51c12b53 99: onsuccess: #114: 1: Success after binutils/gcc/linux/g [...] discards fc8af7447e7f 98: onsuccess: #112: 1: Success after binutils/gcc/linux/g [...] discards 0c2be1934c4e 97: onsuccess: #111: 1: Success after binutils/gcc/linux/g [...] discards e9a7bdeb9861 96: onsuccess: #110: 1: Success after binutils/gcc/linux/g [...] discards 83594a377af5 95: onsuccess: #109: 1: Success after binutils/gcc/linux/g [...] discards 6f7208ea4236 94: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] discards b9b218f9a63f 93: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] discards 0a7a38a71835 92: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] discards d433e9bdd731 91: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] discards cabd780fe7a1 90: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] discards f11be77d09b8 89: onsuccess: #102: 1: Success after binutils/gcc/linux/g [...] discards 699799aa7257 88: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] discards a76408d05ba5 87: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] discards 5379cddb637b 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gl [...] discards a8753da1b39c 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gd [...] discards a1c296372117 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] discards 2b12fddc308e 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 [...] discards 013a6ec116e9 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gd [...] discards 3b323abbb410 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] discards 292aff4c0a71 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] discards 2563fefd2b0e 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] discards b30d990c5135 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] discards 73e6bd0b5a78 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gd [...] discards 2472b4c9f314 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gd [...] discards 3e093a746e18 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gl [...] discards 15ac4225cfdb 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] discards fc85c93e814e 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] discards 19d91221819a 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gl [...] discards cdf81d07b212 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gl [...] discards 717422a502eb 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gl [...] discards 9c5463cfaa83 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] discards 42a8a9972972 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gd [...] discards 8a7635eeb9fe 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] discards f81f909c4701 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gd [...] discards ffd6be1f90d1 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gl [...] discards 6c5748013bc3 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gd [...] discards e5d91f5c98eb 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] discards 1150c4027f2f 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gl [...] discards 897eb4c43f2e 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gd [...] discards e0865d77cb19 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gd [...] discards 75670a5fa026 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gl [...] discards 3263eeb8befe 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 65c663105011 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards a157905d8c1e 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards f4886f5278b8 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gd [...] discards 7135c384535f 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards 0896a0ef5665 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] discards e7cda6e5b664 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] discards f594da6d5bc3 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gl [...] discards 8d72aab0fd3e 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gl [...] discards b6c777eed43e 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gl [...] discards fd6f9e242327 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gl [...] discards 5a4a33503234 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards 32eb8ddd20ce 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] discards 8bb3412213aa 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gl [...] discards 0c638771f082 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] discards 2bf78a189fbf 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] discards 624aa37b18a7 42: onsuccess: #53: 1: Success after linux: 3008 commits new 8ef272dbf590 42: onsuccess: #53: 1: Success after linux: 3008 commits new 717c24fb1e9e 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] new 5f36a7f902cd 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] new 4fe72bbea535 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gl [...] new c047bd7dd1b0 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] new 5f7ef4a568ce 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new 9aa063bb8b40 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gl [...] new 6a1fc34f12b6 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gl [...] new 97e373012e84 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gl [...] new 511e8bda855c 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gl [...] new 27895151d745 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] new fa2451be83b4 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] new 0e622532084e 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 23997efe2f56 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gd [...] new a60c661e9ec3 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 96df4680df44 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new ed1ae25f7979 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 475a23eac1b7 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gl [...] new b2a6debf067e 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gd [...] new 7fd06b41f2e0 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gd [...] new 5f9bd41026d9 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gl [...] new 386a2f2b9a16 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] new 7786339b9611 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gd [...] new c481846ca4f4 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gl [...] new fb726b4130b5 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gd [...] new fc1f4727f6b0 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] new 3fc9b077727a 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gd [...] new 101acb5a23cf 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] new 4b5bc342e79d 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gl [...] new 640e6d6ed43e 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gl [...] new e8189ce47be8 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gl [...] new 0b6ce11e8c5c 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] new e49402a4c1f3 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] new f98e3404ce3d 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gl [...] new d6fff489be23 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gd [...] new 265cf009f216 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gd [...] new db24291e2a07 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] new b10d1fa59195 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] new 954d94747ab2 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] new 573d5e21209c 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] new af211af4a17b 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gd [...] new 60d4c19f4baa 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 [...] new 3e81162f854e 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] new f320f9353f54 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gd [...] new 525e0902aa03 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gl [...] new ec927c64affe 87: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] new 292b49b1b80b 88: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] new 9b809714316a 89: onsuccess: #102: 1: Success after binutils/gcc/linux/g [...] new 9a000ca5ffe2 90: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] new 333e0f5912ba 91: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] new eb625901e632 92: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] new 894cb39a0c84 93: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] new c335bd605fb1 94: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] new b125f326e103 95: onsuccess: #109: 1: Success after binutils/gcc/linux/g [...] new 5149facaa8d7 96: onsuccess: #110: 1: Success after binutils/gcc/linux/g [...] new 1f92df610f2e 97: onsuccess: #111: 1: Success after binutils/gcc/linux/g [...] new 6ad05c3771a4 98: onsuccess: #112: 1: Success after binutils/gcc/linux/g [...] new 032a23def662 99: onsuccess: #114: 1: Success after binutils/gcc/linux/g [...] new cdb78be664ec 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 3 [...] new 7f6b8a671e25 101: onsuccess: #116: 1: Success after binutils/gcc/linux/ [...] new e89004213834 102: onsuccess: #117: 1: Success after binutils/gcc/linux/ [...] new 59a1c865018c 103: onsuccess: #118: 1: Success after binutils/gcc/linux/ [...] new dda73bbbdf93 104: onsuccess: #119: 1: Success after binutils/gcc/linux/ [...] new 67055c7fe3e3 105: onsuccess: #120: 1: Success after binutils/gcc/linux/ [...] new 7476310dfdaa 106: onsuccess: #121: 1: Success after binutils/gcc/linux/ [...] new 813335c3792f 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new af13217cfa4c 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] new 5894f6188358 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 7d6e7ad049f2 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new 7375c7b5b704 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new a0f63d707b0a 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 001bf4e86ac6 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gd [...] new 957cd3a0efd7 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new b4ee6044e9d8 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new c4ce5cfcbcb5 116: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new cb7fcb708ef9 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 6d06775f200e 118: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 3ca0f6f5f9ec 119: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new e0a7557c97da 120: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new a4dfd2ca3aef 121: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new b6313b153ee6 122: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new e26c1f3d9530 123: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 23812b20deb8 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new deee2ce611fa 125: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 2eaba67fc28c 126: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new 6b03ee4c66b9 127: force: #27: : Failure after baseline build: no new commits new 130d47d6bda7 128: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 52e6d67f0f37 129: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new bcdf1dc15976 130: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new 73dae855d605 131: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 311c5c5134be 132: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new 558b6bd90180 133: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new 727216918519 134: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new 26ddbf395660 135: onsuccess: #38: 1: Success after binutils/gcc/linux/g [...] new b0f6e7eec357 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new 5ba4640dea38 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 551b652fccaf 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new 2cb29b1f0f66 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] new 3cf0e058d341 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] new e86812fba140 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/g [...] new 2e176a9d799e 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/g [...] new 86e31f073ded 143: onsuccess: #47: 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 (7bb8d991250b) \ 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 2064 -> 2032 bytes 02-prepare_abe/console.log.xz | Bin 2540 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 35080 -> 35672 bytes 04-build_abe-gcc/console.log.xz | Bin 203904 -> 203200 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8708 -> 8724 bytes 07-build_abe-glibc/console.log.xz | Bin 241708 -> 241260 bytes 08-build_abe-gdb/console.log.xz | Bin 34600 -> 35036 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3804 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2756 -> 3320 bytes 11-check_regression/console.log.xz | Bin 5216 -> 4876 bytes 11-check_regression/results.compare | 4 +-- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 44 ++++++++++++++--------------- 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 | 51 +++++++++++++++------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 ++++++++++++------------- manifest.sh | 38 ++++++++++++------------- sumfiles/gdb.log.xz | Bin 14624 -> 14620 bytes sumfiles/gdb.sum | 4 +-- 26 files changed, 96 insertions(+), 103 deletions(-)