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

discards 34494c5fa8a 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards fe4d5d1895e 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards d300be0db50 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 6e326722585 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 0d9796f729c 121: force: #26: : Failure after baseline build: no new commits discards 6cd41f3952f 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 02e026cd146 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 6094fe690c1 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 6eb9ebe43c7 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards e2061584b4d 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 0cfe597a063 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards f68a2a34118 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 7a0d42dc333 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 73b8054a80e 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards d4deee82a9a 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards df64d77a2ff 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 11bce5d9dd1 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 6df8fec9eb4 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards a86aefef933 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 47eeec2bffa 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 776df77124b 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 722280f5fdb 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 794e56e2715 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 2bb32ee8257 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards fe94755b578 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards 32c13cce78b 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards 682021da1f5 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 0d0b9fa71aa 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 53dbbe611cd 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards 5254995cf05 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 7081690fa36 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards 380090185b8 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 8392e81ba1e 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards e9d1970891a 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 4dc0f6f70c5 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards e8f260c1a32 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 80864afbea4 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 19b66e0fc55 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 572f2024cfb 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards 24d6337cae1 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 9dfbdccd742 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 0afd054d0da 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 4f649ce4973 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 1b523957a63 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards f2f17adee33 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards 38db57e806a 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards a220f5f2fc0 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards e3153bbd5d8 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards df2b342ff43 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 7eae2aafe29 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards 358756681f8 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 9f7cf038f81 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards c798b72675d 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards a0d87eb571a 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards 2b1887ee253 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards b9209f88c6c 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards 64cc541bb74 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards 8e38a1f6560 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards c146e01bf17 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 2bdec59c5b6 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 8da6d937eb2 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 586fdfcb1f3 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards efafbd6a496 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards dac11aca767 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards f1e1f9bdcac 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards 3773e28e8da 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards bb7209f0aca 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards 15ad6e72f3d 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 6152d4c6b12 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 42aa0f2c797 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards b02111b77a9 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards 92e2845cb93 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 7d4be739d81 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards dbe38d06628 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards a5bed1c97ab 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards f1fb0b0fd5c 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards e79fdc70858 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards c79aa02d9ff 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 7cf1f391efe 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards b39c9ea173e 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards a9d87b2e03c 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards 52b01b495a4 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 8b83598bfd1 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards 9983c45bfa5 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards d2483e7bb5c 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 6243e246b37 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards 2d8d463e35a 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 98e72abc1cc 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards 0be4158026a 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 9ba267abde0 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 8db3e57d454 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 339eba2e2af 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 18b62f9d2cc 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 050eaa378e2 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards f5bb029f9a1 31: onsuccess: #38: 1: Success after linux: 14 commits discards bb49f941ab6 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 05585bf4868 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 18cc7943f84 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards b147cb1c45b 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards d923da24945 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 284d39a0f26 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new be01061a8b9 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new dfbfd2bc09b 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new ff1fdc961bb 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new f0b5ba5f155 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new c5f7a147c55 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 2e70113ce38 30: onsuccess: #36: 1: Success after binutils: 18 commits new 85c7fbf8b01 31: onsuccess: #38: 1: Success after linux: 14 commits new 9b1b1ccfdc7 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 7d411e0d92b 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 0d94bb59577 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new a5fd0776c24 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new f1b0efeef2d 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 8909ccb23a1 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 8e151fc684c 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new e8f89c7e4a9 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new 376b8376091 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new d40c359869f 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new e6ed15f3183 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new bda4812f4ed 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new 83ea3976bd7 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 513483c35f3 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new b78409c09dd 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new 2aa883eceba 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 193b596ce39 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 702c090e7b2 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new e7bc4e03c7b 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new c17ed7c38b3 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new fe99a0c8088 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new b6caa2fb3ac 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new fa42c2ffd48 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new a13248c22fd 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new 52f152528d3 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 5b65b52afaf 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 9ca0d04b3cb 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 3c2b0f1461c 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new aea0fb3081c 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 6d722f1fcb1 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new fdcd8a88382 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new 325630e5bc2 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 526daaa5304 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new 772399ee81c 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 8f8936bff8e 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new cfcce76c26c 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 51b245e1ad0 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new b70c2610d5b 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new f1ff92b60ed 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new 0ba7ff1477f 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 8a6bc21de03 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 5e7676bc950 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 8a5d54b61f7 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new 95219e8f0e3 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new 8e38416075b 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new 7de90d3ee18 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new fe0ba61e3b3 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 84bced38dba 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new b2ae59eb7b4 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 6bdd989ff53 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new c6a9185ef27 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 69096adc431 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 0cd2e5a9d15 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 5c095f5e99e 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new befe4a06a45 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new afe0e01e0e3 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 6405a579831 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 499e679d042 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new 098433c78d5 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new cfb20c6745e 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 3b038ad3567 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new b375cc723d6 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 218076dbd97 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 306d1286de3 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new 5e0d7aac85c 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new dc42a7daca9 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new a4c2b93ac30 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new f545fc72c59 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 400bdb7c8ba 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new 8b4ffc73464 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 33006f21542 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new 9613a3be5ce 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 8826822e8e1 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new f4185230599 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 90bc1e2b682 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 431d8bbe77f 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 0abb993e7d5 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new c2681bff147 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 015f2554d5d 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new f05afdd0e98 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 5a130adec6a 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new e5ea0f11563 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 7e9588c6197 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 64128a95bc5 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 049594f70f7 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 7a1a0ca1702 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 9c74ea06f8c 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 0115578abca 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new f7199dd487b 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 64954ec0b8d 121: force: #26: : Failure after baseline build: no new commits new ccd3da37df5 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 783ca66f54f 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 4f8959d77e0 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 945188c87ae 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 4a374ba3c59 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...]

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 (34494c5fa8a) \ 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 1732 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 48944 -> 49020 bytes 04-build_abe-gcc/console.log.xz | Bin 235852 -> 236288 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8192 -> 8404 bytes 07-build_abe-glibc/console.log.xz | Bin 233480 -> 232820 bytes 08-build_abe-gdb/console.log.xz | Bin 47476 -> 47588 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3768 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2836 -> 2916 bytes 11-check_regression/console.log.xz | Bin 4900 -> 4772 bytes 11-check_regression/mail-body.txt | 2 +- 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 31 +++------------- 12-update_baseline/console.log | 68 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 ++++++++--------- sumfiles/gdb.log.xz | Bin 14468 -> 14476 bytes sumfiles/gdb.sum | 4 +- 26 files changed, 71 insertions(+), 90 deletions(-)