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 f55fbbf8048 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 3af74994ef1 121: force: #26: : Failure after baseline build: no new commits discards 2e220fb1df1 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 82a4ed5ddf3 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards af3d3358843 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards c06ffcd0c56 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards a5dbe0a4619 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards c6a8acec4d1 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards c7a3501af59 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 147d4bdf5bd 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 7a0a18a6415 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 50851f9920a 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 075f4bc2212 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 512046659e4 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards dadd8df3588 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards 420fe01215c 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 880c24d8281 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 73e498e2d82 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 67e20f9eece 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards e93417eb195 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 8b8661b4fb1 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards 8f1d9c8123e 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards 9e61320b45b 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards fb7b078aadc 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 16002e44f80 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 5e7b27610ec 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards e86ff532800 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards d168d7a760a 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards 18b57e92450 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 95009e89a3f 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 20bfd8192d3 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 170733f07de 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 96dfd6aa519 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards e2680e6e8bc 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 2263ecb8ac8 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 53d04a6e8f0 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards 63c73233420 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 11d3ac65f1e 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards c3cdd6333e5 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards ecee2728b37 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 47d5b8c3d58 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards bb379babbda 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards d730c4acc8b 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 85d5538f3dd 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards a6e412ab794 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 12f01ce7675 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 8b63fac66a9 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards b94b8266855 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 2dc9c5af7bb 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 0295e91611a 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards cf66297c324 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards 32b7bc442e6 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 9b75023a5a6 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards 61d27bb586c 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards 4b3789aa663 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards 42014f35482 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 2f0573b9f9a 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 5e087e0ed6a 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards c3dd7333b39 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards f22d5e77e87 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 5eb5f717bbc 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards 5b64c4c6685 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards aeef2015262 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 8f96bc515fb 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards d82c77d5d7b 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards bf53c33233f 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards ddca3815f27 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 4ae5aed7c87 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards 1cd202d4649 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 573a4496feb 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 7e87aecb595 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards 3c72771077f 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards ea89caeac28 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards f86199ef3d5 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards aa78d933cca 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards f8cbc5978aa 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 7e74de6701c 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards 25d0fba3878 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards be8dafae9d1 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 5e4b195535e 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards e8a33787387 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards 13ac611d531 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 34c3ac0cdee 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards d73cd4ef6dd 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 32240a4ca17 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards d64ca5b7e9c 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 7365bd115cb 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 45044ab5c4d 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 87379b55058 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards d1269d23af6 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 73800414f91 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards ad72a29bb0f 31: onsuccess: #38: 1: Success after linux: 14 commits discards 96f0fd31b7a 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 6f785246dfd 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 001ffcedca2 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 5eda2326ac4 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 6822988c42f 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 9ffd9daea1c 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] discards 6d27db17d4e 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] discards d24805aab61 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards 30e8bada7f3 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new aedc9334c8a 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new d9c59cd4b0e 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new 34445328d94 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new 510d4c42d2f 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new b465d6ff078 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 054a76d68d2 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 6408682a45e 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 120f09cba08 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 147501ea65e 30: onsuccess: #36: 1: Success after binutils: 18 commits new ad164af3b85 31: onsuccess: #38: 1: Success after linux: 14 commits new 5ad20eba2e6 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 3880b168c6c 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 2dcf4aab119 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 28d5d01025c 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 2c904b7484f 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new efc213d44d2 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 0da11d8f6e8 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new a93eecbd03d 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new 0b74d23bc6b 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new aa5015d6d4a 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new 89aa73ca7a5 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new 68b5f2f1808 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new 6d2a2ec86f5 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 2e56cd6b764 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new b4fe575b27e 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new 0b5a42479de 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 46f1a4baeaa 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new bab11ea253b 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new 67135e8e628 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new c9f3563db7a 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 3ecf7cde04e 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new 00d51e4e2cf 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 31b08defe05 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 80fc584fdc1 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new 486d213ae15 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 3d704ba86eb 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new f584d244bb9 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new fe70178deaa 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new 4d9ba3fb994 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new a3d9b7b7b76 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 742a3ac9eb5 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new b55eba97869 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 092d5f20f99 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new 13c941554a5 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 46a88454ae5 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 4b6eb4b3c39 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 1907f4dc0d5 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new c84c0554911 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new d872596bd1a 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new eb05282787e 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 84ddeceafeb 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 79d37b38cf1 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 28c1fd9c872 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new 764d123c6e5 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new 36a201f0d00 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new 51d0c463f12 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 13ca88f1e4a 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 14a313d81a1 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new dac04fa98ff 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new bcd8c187455 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new 120732962b0 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 8d0c4116ab5 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 54a2edbb360 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new afd0c060871 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 55854698f8c 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new faa3a282906 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 7a905ad26a1 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 4c880a1f775 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new abc793c5843 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new 2b0d05a1ca2 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new b93cdc17c74 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new ed02781ebc5 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 3f187146470 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new da8991fdb53 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new ba3d3891403 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 1c37afdafe9 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new 504ce8519d1 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new a8f64131b78 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new b2786dee2c7 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new 0ad92b2284f 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new ab3dfb219b6 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new 5363781c641 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 5c151567f12 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new bcde2af2041 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new e96cd3d34f2 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new b9e76e2ace2 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 74b1efe64bb 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new cc48fe1b234 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 79ba6e666ae 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new f69e75fffa2 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new eb0e493282e 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 4152e2f2f8a 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 8e5cca5a246 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 577612ee85c 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new e77a8126645 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 37972a01d9b 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 0b54a2ccac4 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new befd6572bcf 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 6b53c570c0c 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 43792c1c349 121: force: #26: : Failure after baseline build: no new commits new a133cb0dab8 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 44c8beb8fd2 123: onsuccess: #29: 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 (f55fbbf8048) \ 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 1756 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2488 -> 2476 bytes 03-build_abe-binutils/console.log.xz | Bin 49344 -> 48904 bytes 04-build_abe-gcc/console.log.xz | Bin 237628 -> 235140 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8560 -> 9904 bytes 07-build_abe-glibc/console.log.xz | Bin 233748 -> 233708 bytes 08-build_abe-gdb/console.log.xz | Bin 46884 -> 47200 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3776 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2988 -> 2688 bytes 11-check_regression/console.log.xz | Bin 4056 -> 4724 bytes 11-check_regression/mail-body.txt | 3 +-- 11-check_regression/results.compare | 7 ++++++ 11-check_regression/results.compare2 | 42 ++++++++++++++++++++++++++++++++ 12-update_baseline/console.log | 44 +++++++++++++++++----------------- 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 | 5 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++------------- sumfiles/gdb.log.xz | Bin 11920 -> 11940 bytes sumfiles/gdb.sum | 4 ++-- 26 files changed, 99 insertions(+), 52 deletions(-) create mode 100644 11-check_regression/results.compare create mode 100644 11-check_regression/results.compare2