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 b1cf6bd4019 121: force: #26: : Failure after baseline build: no new commits discards e458b3d35aa 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 9eabf9aecaf 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 9f7c5e95a83 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards f033feceb9a 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 924ca094abd 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 01987cc7989 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 1bc82efd484 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 8ef556e815e 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 0f5b1bd0972 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards a20f9396a12 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards c5db3a5b21c 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 81307c2f9fa 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards c662451ce60 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards bebeb232e6a 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards aa3b4327fd2 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 7db2f50f67c 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 417d45ff70a 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 28e749b071d 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 2c3d884bff1 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards 722a40ed54a 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards cab7ef7f6f6 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards 4eea086c065 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards d203c777675 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards a9a5194a3f2 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards 40b1f0b5221 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 478592491ac 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards 8617a57eb12 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 2defa454dc0 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 2614f0e3d90 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 150a3c29fd7 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards fb64be47981 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards fe4576f41e5 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards e9082e4eb28 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards d7dff0e75a3 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards e7c068a1e60 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 5a8eca2f506 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards e0b5e837dec 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards b1677289d02 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards feeb8e1b2c0 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards ba960b4620d 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards 2b9744d1a42 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 986df8e70d6 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards 1ca88abec84 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 3eff9031336 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards aa089693c54 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards 449fb2d0e27 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards e299aab652e 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 7d1b2b68916 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards d19b0a18a8c 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards 560510db0c1 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 3cffb3b6119 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards 4a3a1db8876 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards 59751e2e8b9 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards d92ba40c796 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards cebf81e844b 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 45a96007c17 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 22454b94384 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards 9c7846d6f8e 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 7f423e4493e 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards daaa63b8ed5 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards 19c85c9b366 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards fa7fd338b5f 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards fe489f7e8db 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards cc3f3e44f46 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards dbb9c78c617 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards c009dd97db6 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards e5884eb4133 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 3c9a13a6146 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 7ed4124c418 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards 74c0086275c 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards fe9df17d8d7 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards a09ff0d35e5 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards 72249711fee 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards a3fcb8e9a8e 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards ac55ebf2997 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards 36a3ef4835c 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards 0b97cc84b51 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards f292cbd2d81 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards fe642c0d75b 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards b9daa3fc268 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 27fdb589fad 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards f86464f20a4 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards b063894c0c3 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards 57d466ec828 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 3d112553ec8 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 5639f167d04 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards cd2a7a1a154 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 3b4895a06d8 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 60e4e87fb4f 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 65c06ed99e2 31: onsuccess: #38: 1: Success after linux: 14 commits discards facb2433b94 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 365e45413ad 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards d5918263cc9 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 0116e36ffe1 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 1251f8e6ea3 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards d6ba6e2ec85 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] discards ae46aac838b 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] discards e7834bef478 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards bb7b993521d 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 764bf9918c1 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 030b6dde354 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 30e8bada7f3 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new d24805aab61 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new 6d27db17d4e 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new 9ffd9daea1c 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new 6822988c42f 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 5eda2326ac4 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 001ffcedca2 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 6f785246dfd 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 96f0fd31b7a 30: onsuccess: #36: 1: Success after binutils: 18 commits new ad72a29bb0f 31: onsuccess: #38: 1: Success after linux: 14 commits new 73800414f91 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new d1269d23af6 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 87379b55058 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 45044ab5c4d 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 7365bd115cb 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new d64ca5b7e9c 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 32240a4ca17 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new d73cd4ef6dd 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new 34c3ac0cdee 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new 13ac611d531 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new e8a33787387 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new 5e4b195535e 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new be8dafae9d1 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 25d0fba3878 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new 7e74de6701c 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new f8cbc5978aa 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new aa78d933cca 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new f86199ef3d5 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new ea89caeac28 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 3c72771077f 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 7e87aecb595 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new 573a4496feb 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 1cd202d4649 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 4ae5aed7c87 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new ddca3815f27 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new bf53c33233f 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new d82c77d5d7b 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 8f96bc515fb 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new aeef2015262 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 5b64c4c6685 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 5eb5f717bbc 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new f22d5e77e87 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new c3dd7333b39 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new 5e087e0ed6a 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 2f0573b9f9a 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 42014f35482 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 4b3789aa663 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new 61d27bb586c 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new 9b75023a5a6 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new 32b7bc442e6 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new cf66297c324 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 0295e91611a 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 2dc9c5af7bb 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new b94b8266855 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new 8b63fac66a9 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new 12f01ce7675 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new a6e412ab794 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 85d5538f3dd 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new d730c4acc8b 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new bb379babbda 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new 47d5b8c3d58 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new ecee2728b37 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new c3cdd6333e5 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 11d3ac65f1e 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 63c73233420 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new 53d04a6e8f0 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 2263ecb8ac8 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new e2680e6e8bc 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new 96dfd6aa519 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new 170733f07de 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 20bfd8192d3 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 95009e89a3f 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 18b57e92450 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new d168d7a760a 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new e86ff532800 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 5e7b27610ec 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new 16002e44f80 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new fb7b078aadc 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 9e61320b45b 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new 8f1d9c8123e 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 8b8661b4fb1 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new e93417eb195 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 67e20f9eece 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 73e498e2d82 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 880c24d8281 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 420fe01215c 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new dadd8df3588 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 512046659e4 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 075f4bc2212 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 50851f9920a 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 7a0a18a6415 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 147d4bdf5bd 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new c7a3501af59 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new c6a8acec4d1 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new a5dbe0a4619 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new c06ffcd0c56 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new af3d3358843 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 82a4ed5ddf3 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 2e220fb1df1 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 3af74994ef1 121: force: #26: : Failure after baseline build: no new commits new f55fbbf8048 122: onsuccess: #28: 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 (b1cf6bd4019) \ 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 1936 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 3444 -> 2488 bytes 03-build_abe-binutils/console.log.xz | Bin 53140 -> 49344 bytes 04-build_abe-gcc/console.log.xz | Bin 237548 -> 237628 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8804 -> 8560 bytes 07-build_abe-glibc/console.log.xz | Bin 236444 -> 233748 bytes 08-build_abe-gdb/console.log.xz | Bin 50340 -> 46884 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3784 bytes 10-build_abe-check_gdb/console.log.xz | Bin 1340 -> 2988 bytes 11-check_regression/console.log.xz | Bin 2608 -> 4056 bytes 11-check_regression/jira-body.txt | 2 +- 11-check_regression/mail-body.txt | 10 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.regressions | 2 - 12-update_baseline/console.log | 46 ++--- 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 | 10 +- mail/mail-subject.txt | 2 +- manifest.sh | 35 ++-- results | 4 +- sumfiles/gdb.log.xz | Bin 0 -> 11920 bytes sumfiles/gdb.sum | 340 ++++++++++++++++++++++++++++++++ 28 files changed, 403 insertions(+), 62 deletions(-) delete mode 100644 11-check_regression/results.regressions create mode 100644 sumfiles/gdb.log.xz create mode 100644 sumfiles/gdb.sum