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 44c8beb8fd2 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards a133cb0dab8 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 43792c1c349 121: force: #26: : Failure after baseline build: no new commits discards 6b53c570c0c 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards befd6572bcf 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 0b54a2ccac4 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 37972a01d9b 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards e77a8126645 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 577612ee85c 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 8e5cca5a246 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 4152e2f2f8a 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards eb0e493282e 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards f69e75fffa2 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 79ba6e666ae 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards cc48fe1b234 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 74b1efe64bb 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards b9e76e2ace2 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards e96cd3d34f2 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards bcde2af2041 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 5c151567f12 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 5363781c641 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards ab3dfb219b6 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards 0ad92b2284f 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards b2786dee2c7 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards a8f64131b78 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 504ce8519d1 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 1c37afdafe9 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards ba3d3891403 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards da8991fdb53 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards 3f187146470 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards ed02781ebc5 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards b93cdc17c74 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 2b0d05a1ca2 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards abc793c5843 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 4c880a1f775 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 7a905ad26a1 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards faa3a282906 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards 55854698f8c 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards afd0c060871 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 54a2edbb360 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 8d0c4116ab5 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 120732962b0 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards bcd8c187455 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards dac04fa98ff 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 14a313d81a1 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards 13ca88f1e4a 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 51d0c463f12 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 36a201f0d00 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards 764d123c6e5 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 28c1fd9c872 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 79d37b38cf1 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 84ddeceafeb 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards eb05282787e 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards d872596bd1a 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards c84c0554911 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards 1907f4dc0d5 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards 4b6eb4b3c39 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 46a88454ae5 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 13c941554a5 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 092d5f20f99 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards b55eba97869 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 742a3ac9eb5 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards a3d9b7b7b76 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards 4d9ba3fb994 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards fe70178deaa 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards f584d244bb9 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 3d704ba86eb 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 486d213ae15 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 80fc584fdc1 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards 31b08defe05 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 00d51e4e2cf 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 3ecf7cde04e 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards c9f3563db7a 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 67135e8e628 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards bab11ea253b 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards 46f1a4baeaa 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 0b5a42479de 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards b4fe575b27e 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards 2e56cd6b764 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards 6d2a2ec86f5 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 68b5f2f1808 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards 89aa73ca7a5 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards aa5015d6d4a 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 0b74d23bc6b 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards a93eecbd03d 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 0da11d8f6e8 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards efc213d44d2 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 2c904b7484f 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 28d5d01025c 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 2dcf4aab119 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 3880b168c6c 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 5ad20eba2e6 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards ad164af3b85 31: onsuccess: #38: 1: Success after linux: 14 commits discards 147501ea65e 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 120f09cba08 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 6408682a45e 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 054a76d68d2 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards b465d6ff078 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 510d4c42d2f 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] discards 34445328d94 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] discards d9c59cd4b0e 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new 8ce510752b1 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new eea37f3da23 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new 19398225236 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new 18d47ef33e7 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 1af8c9b6aef 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 75a52461e7b 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 10478d000e9 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new a8dbf90a58a 30: onsuccess: #36: 1: Success after binutils: 18 commits new 35700bf846e 31: onsuccess: #38: 1: Success after linux: 14 commits new edfbc169508 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 83a54e109bd 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new f81652bb233 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 5732e09a950 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 31c6e9b9309 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 3bbd5c61926 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 6439c6efcf8 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new dde9efd8769 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new 18485bb02c7 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new 4a82ac1889c 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new 066c6c79703 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new 0d6fd10078f 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new eb09a18ccc9 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 11acf8e34d3 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new 833621dcd41 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new 8b65425d0eb 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 1b69da357f0 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 98033e58c1c 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new a1a02a98fe7 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 282b655b1d5 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 70e4f11bf8f 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new 25ce039221e 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new dc1ed5faf55 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 2981c3a9095 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new b637f4c121a 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new d57c2f45156 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 8634b7ca398 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 0e16493fdce 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new 8b08be44752 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new ef99184e7df 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 809de9d7036 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new 143ccb15600 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 0329a6d54ac 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new 602b2037b66 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 43fec57b1d1 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 37f05ab9933 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 3cc42daf24c 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new 191a7d9dfbd 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new 8cf58215555 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new 82e3e64f2ea 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 7463c063870 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 302af6aabc0 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 899044a5ec9 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new 6a35d5f5784 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new bed5801c31c 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new 3300c7c502a 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 31aff8a1734 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 46dd99f4245 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new 69dad4a7692 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 90e7c9ccd33 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new f30aee13cc9 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new f8e071da60c 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new a156206df56 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 7b56019faee 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 85d5497e17f 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new 44f89d0ec3f 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 959504becf6 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 76d613c51fc 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new 3a83856ff4b 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new c85df76f9b4 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 5ea0197df24 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 6958d12b26b 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 8d096ae422e 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new a68b09aeea7 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new d653234aa9c 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 05fe447b477 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new 60f7b3483e8 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new cac3f603448 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 22261fe52cc 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new 3985d21a14a 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 848ffbb9630 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new bb7346252e7 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 798f8952744 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 3eb07cdf01e 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new cb9b495b8cb 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new c91ec689f0d 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 17fdb85e98e 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 9c2580d49b6 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 7191202188c 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new a7889112314 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 987fe3d9b89 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new f366a5de218 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new be8a1388b82 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 9bcb0ca0aaa 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 4b0b4521be9 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 9009e65a942 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 7f98c63a042 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 513ad18bf61 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 3bb0440e504 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 772084b53f1 121: force: #26: : Failure after baseline build: no new commits new ee838effcbe 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 71f991f0677 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 7d76a46d961 124: onsuccess: #30: 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 (44c8beb8fd2) \ 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 1796 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2476 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 48904 -> 49208 bytes 04-build_abe-gcc/console.log.xz | Bin 235140 -> 234896 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9904 -> 9024 bytes 07-build_abe-glibc/console.log.xz | Bin 233708 -> 233020 bytes 08-build_abe-gdb/console.log.xz | Bin 47200 -> 46528 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3776 -> 3784 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2688 -> 2628 bytes 11-check_regression/console.log.xz | Bin 4724 -> 4732 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 6 +-- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++-------- sumfiles/gdb.log.xz | Bin 11940 -> 11924 bytes sumfiles/gdb.sum | 4 +- 25 files changed, 65 insertions(+), 65 deletions(-)