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 7d76a46d961 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 71f991f0677 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards ee838effcbe 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 772084b53f1 121: force: #26: : Failure after baseline build: no new commits discards 3bb0440e504 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 513ad18bf61 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 7f98c63a042 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 9009e65a942 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 4b0b4521be9 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 9bcb0ca0aaa 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards be8a1388b82 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards f366a5de218 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 987fe3d9b89 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards a7889112314 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 7191202188c 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 9c2580d49b6 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 17fdb85e98e 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards c91ec689f0d 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards cb9b495b8cb 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 3eb07cdf01e 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 798f8952744 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards bb7346252e7 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 848ffbb9630 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards 3985d21a14a 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards 22261fe52cc 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards cac3f603448 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 60f7b3483e8 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 05fe447b477 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards d653234aa9c 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards a68b09aeea7 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards 8d096ae422e 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 6958d12b26b 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 5ea0197df24 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards c85df76f9b4 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 3a83856ff4b 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 76d613c51fc 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 959504becf6 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 44f89d0ec3f 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards 85d5497e17f 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 7b56019faee 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards a156206df56 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards f8e071da60c 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards f30aee13cc9 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards 90e7c9ccd33 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards 69dad4a7692 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 46dd99f4245 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards 31aff8a1734 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 3300c7c502a 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards bed5801c31c 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards 6a35d5f5784 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 899044a5ec9 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 302af6aabc0 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 7463c063870 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards 82e3e64f2ea 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 8cf58215555 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards 191a7d9dfbd 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards 3cc42daf24c 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards 37f05ab9933 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 43fec57b1d1 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 602b2037b66 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 0329a6d54ac 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards 143ccb15600 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 809de9d7036 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards ef99184e7df 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards 8b08be44752 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 0e16493fdce 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards 8634b7ca398 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards d57c2f45156 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards b637f4c121a 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 2981c3a9095 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards dc1ed5faf55 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 25ce039221e 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 70e4f11bf8f 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards 282b655b1d5 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards a1a02a98fe7 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 98033e58c1c 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards 1b69da357f0 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 8b65425d0eb 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 833621dcd41 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards 11acf8e34d3 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards eb09a18ccc9 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 0d6fd10078f 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards 066c6c79703 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards 4a82ac1889c 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 18485bb02c7 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards dde9efd8769 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 6439c6efcf8 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards 3bbd5c61926 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 31c6e9b9309 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 5732e09a950 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards f81652bb233 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 83a54e109bd 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards edfbc169508 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 35700bf846e 31: onsuccess: #38: 1: Success after linux: 14 commits discards a8dbf90a58a 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 10478d000e9 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 75a52461e7b 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 1af8c9b6aef 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 18d47ef33e7 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 19398225236 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] discards eea37f3da23 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new 5b247108f35 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new 284d39a0f26 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new d923da24945 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new b147cb1c45b 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 18cc7943f84 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 05585bf4868 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new bb49f941ab6 30: onsuccess: #36: 1: Success after binutils: 18 commits new f5bb029f9a1 31: onsuccess: #38: 1: Success after linux: 14 commits new 050eaa378e2 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 18b62f9d2cc 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 339eba2e2af 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 8db3e57d454 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 9ba267abde0 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 0be4158026a 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 98e72abc1cc 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new 2d8d463e35a 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new 6243e246b37 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new d2483e7bb5c 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new 9983c45bfa5 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new 8b83598bfd1 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new 52b01b495a4 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new a9d87b2e03c 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new b39c9ea173e 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new 7cf1f391efe 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new c79aa02d9ff 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new e79fdc70858 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new f1fb0b0fd5c 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new a5bed1c97ab 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new dbe38d06628 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new 7d4be739d81 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 92e2845cb93 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new b02111b77a9 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new 42aa0f2c797 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 6152d4c6b12 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 15ad6e72f3d 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new bb7209f0aca 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new 3773e28e8da 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new f1e1f9bdcac 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new dac11aca767 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new efafbd6a496 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 586fdfcb1f3 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new 8da6d937eb2 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 2bdec59c5b6 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new c146e01bf17 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 8e38a1f6560 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new 64cc541bb74 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new b9209f88c6c 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new 2b1887ee253 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new a0d87eb571a 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new c798b72675d 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 9f7cf038f81 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new 358756681f8 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new 7eae2aafe29 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new df2b342ff43 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new e3153bbd5d8 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new a220f5f2fc0 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new 38db57e806a 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new f2f17adee33 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new 1b523957a63 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 4f649ce4973 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 0afd054d0da 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 9dfbdccd742 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 24d6337cae1 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new 572f2024cfb 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 19b66e0fc55 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 80864afbea4 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new e8f260c1a32 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new 4dc0f6f70c5 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new e9d1970891a 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 8392e81ba1e 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 380090185b8 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 7081690fa36 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new 5254995cf05 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 53dbbe611cd 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new 0d0b9fa71aa 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 682021da1f5 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 32c13cce78b 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new fe94755b578 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 2bb32ee8257 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new 794e56e2715 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 722280f5fdb 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 776df77124b 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 47eeec2bffa 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new a86aefef933 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 6df8fec9eb4 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 11bce5d9dd1 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new df64d77a2ff 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new d4deee82a9a 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 73b8054a80e 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 7a0d42dc333 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new f68a2a34118 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 0cfe597a063 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new e2061584b4d 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 6eb9ebe43c7 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 6094fe690c1 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 02e026cd146 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 6cd41f3952f 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 0d9796f729c 121: force: #26: : Failure after baseline build: no new commits new 6e326722585 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new d300be0db50 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new fe4d5d1895e 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 34494c5fa8a 125: onsuccess: #31: 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 (7d76a46d961) \ 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 1744 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 49208 -> 48944 bytes 04-build_abe-gcc/console.log.xz | Bin 234896 -> 235852 bytes 06-build_abe-linux/console.log.xz | Bin 9024 -> 8192 bytes 07-build_abe-glibc/console.log.xz | Bin 233020 -> 233480 bytes 08-build_abe-gdb/console.log.xz | Bin 46528 -> 47476 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3768 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2628 -> 2836 bytes 11-check_regression/console.log.xz | Bin 4732 -> 4900 bytes 11-check_regression/mail-body.txt | 2 +- 11-check_regression/results.compare2 | 29 ++++++++++++--- 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 ++++++++--------- results | 2 +- sumfiles/gdb.log.xz | Bin 11924 -> 14468 bytes sumfiles/gdb.sum | 19 ++++++++-- 25 files changed, 102 insertions(+), 70 deletions(-)