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 bd76a33d70b 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 526f0c07759 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 98614a806a7 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards e3fac1fb56e 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 816d1cb4cbf 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 1539d37e19b 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 3dcdf9cc0da 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 3b9342b3438 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 3ee37514ba5 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards d2316c26767 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 5ef9197259b 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 6758676969d 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 160d7bfbb03 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards 9ea6d100b1b 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 7de19785dbd 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 956246de081 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 7ad580cce96 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 817d4051f07 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 128b2ed1c12 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards 12a9e507aec 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards 7cfa4d571a7 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards 77c688fd2b4 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 621cfa2a9ce 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 7c591bd4a31 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards ee5676c2897 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 78581cb572d 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards 7752c3a9fc9 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 8deda5ce1bd 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 38190c79655 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 5ac3db46288 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 4385a096da5 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 6c5b94f864e 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards b09a97503b6 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 038bbd942b9 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards 17516689044 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 26680287054 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 6101c4e99d0 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards d1d5a8a9982 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 6a8162a4fe5 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards ce79dd05f7a 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards 141f02bf887 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 97e8728c064 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards 4991761bd8b 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 167dddb3984 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 0ad46eab8bb 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards c49987bd53f 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 4bc60ff8a57 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards b1ee3450fa3 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 997b9a64339 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards a55c223f060 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 9b087b54f2b 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards 180b32dffd5 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards fd9fa536612 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards 488c76c5a7f 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 11ac63259e5 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 27a43036084 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards aa6abf4c6f5 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards 44e5a76522d 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 26bfbc2509b 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards 957ca347f22 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards b9c87829cad 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 2ea419340b4 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards ee51772493f 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 99a388395ea 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 85ae60b33e9 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 80a2ebf77d8 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards 3b706cf98ec 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 790e00154af 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards b88468343c4 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards 73b33b0aadd 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 6f3fa58aebd 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 4feca180e41 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards 9f83737238c 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 001c1d35156 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 7f22f93bfca 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards 1551895a935 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards b02512a8867 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 56d612e6e2e 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards 96ec59b015a 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards 9b6e56b552e 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 083168d9865 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards bcdec55abd8 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 84369898759 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards 932107aa4cc 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 3b48730fb92 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 200af0f453b 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 4d0f818d30f 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 3746238f194 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 8622708d2b6 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards cea4f5c5c0b 31: onsuccess: #38: 1: Success after linux: 14 commits discards e3fc4d1fa74 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 5a3366e7d56 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards d375ba7f630 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards ccb9e673421 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 2abeeb3b891 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 1ce7cb3861f 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] discards 1e378c014cd 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] discards 190c8138dfe 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards 801bfb63d60 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 11f072b969c 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards e0bc5017937 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new 22b0d2b34f7 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new 764bf9918c1 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new bb7b993521d 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new e7834bef478 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new ae46aac838b 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new d6ba6e2ec85 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new 1251f8e6ea3 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 0116e36ffe1 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new d5918263cc9 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 365e45413ad 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new facb2433b94 30: onsuccess: #36: 1: Success after binutils: 18 commits new 65c06ed99e2 31: onsuccess: #38: 1: Success after linux: 14 commits new 60e4e87fb4f 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 3b4895a06d8 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new cd2a7a1a154 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 5639f167d04 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 3d112553ec8 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 57d466ec828 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new b063894c0c3 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new f86464f20a4 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new 27fdb589fad 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new b9daa3fc268 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new fe642c0d75b 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new f292cbd2d81 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new 0b97cc84b51 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 36a3ef4835c 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new ac55ebf2997 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new a3fcb8e9a8e 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 72249711fee 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new a09ff0d35e5 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new fe9df17d8d7 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 74c0086275c 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 7ed4124c418 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new 3c9a13a6146 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new e5884eb4133 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new c009dd97db6 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new dbb9c78c617 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new cc3f3e44f46 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new fe489f7e8db 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new fa7fd338b5f 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new 19c85c9b366 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new daaa63b8ed5 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 7f423e4493e 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new 9c7846d6f8e 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 22454b94384 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new 45a96007c17 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new cebf81e844b 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new d92ba40c796 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 59751e2e8b9 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new 4a3a1db8876 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new 3cffb3b6119 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new 560510db0c1 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new d19b0a18a8c 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 7d1b2b68916 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new e299aab652e 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new 449fb2d0e27 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new aa089693c54 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new 3eff9031336 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 1ca88abec84 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 986df8e70d6 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new 2b9744d1a42 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new ba960b4620d 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new feeb8e1b2c0 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new b1677289d02 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new e0b5e837dec 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 5a8eca2f506 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new e7c068a1e60 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new d7dff0e75a3 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new e9082e4eb28 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new fe4576f41e5 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new fb64be47981 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new 150a3c29fd7 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 2614f0e3d90 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 2defa454dc0 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 8617a57eb12 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 478592491ac 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new 40b1f0b5221 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new a9a5194a3f2 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new d203c777675 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 4eea086c065 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new cab7ef7f6f6 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new 722a40ed54a 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 2c3d884bff1 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new 28e749b071d 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 417d45ff70a 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 7db2f50f67c 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new aa3b4327fd2 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new bebeb232e6a 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new c662451ce60 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 81307c2f9fa 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new c5db3a5b21c 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new a20f9396a12 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 0f5b1bd0972 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 8ef556e815e 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 1bc82efd484 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 01987cc7989 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 924ca094abd 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new f033feceb9a 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 9f7c5e95a83 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 9eabf9aecaf 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new e458b3d35aa 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new b1cf6bd4019 121: force: #26: : Failure after baseline build: no new commits
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 (bd76a33d70b) \ 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 1764 -> 1936 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 3444 bytes 03-build_abe-binutils/console.log.xz | Bin 53052 -> 53140 bytes 04-build_abe-gcc/console.log.xz | Bin 238204 -> 237548 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8620 -> 8804 bytes 07-build_abe-glibc/console.log.xz | Bin 235268 -> 236444 bytes 08-build_abe-gdb/console.log.xz | Bin 51672 -> 50340 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3740 -> 3780 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2588 -> 1340 bytes 11-check_regression/console.log.xz | Bin 6124 -> 2608 bytes 11-check_regression/jira-body.txt | 2 +- 11-check_regression/mail-body.txt | 7 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.compare | 7 - 11-check_regression/results.compare2 | 42 ---- 11-check_regression/results.regressions | 2 + 12-update_baseline/console.log | 40 ++-- dashboard/dashboard-generate.sh | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 7 +- mail/mail-subject.txt | 2 +- manifest.sh | 27 ++- results | 6 +- sumfiles/gdb.log.xz | Bin 11932 -> 0 bytes sumfiles/gdb.sum | 340 -------------------------------- 26 files changed, 50 insertions(+), 438 deletions(-) delete mode 100644 11-check_regression/results.compare delete mode 100644 11-check_regression/results.compare2 create mode 100644 11-check_regression/results.regressions delete mode 100644 sumfiles/gdb.log.xz delete mode 100644 sumfiles/gdb.sum