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 bfa8b76453e 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 01265d697b3 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 8abfa449c75 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards b570a8165be 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards dadabdd9797 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 43c8ca71595 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 805b8b87f56 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 5090c42e513 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 4b84ae309c6 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 2b188667caa 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 6a96af5c29d 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 2e23a531ad3 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards ed05188115e 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 14c5081a03d 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 526dc3adc31 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards d29081e3788 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards f2edb3f86c8 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 7f7a86b4f33 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards 26218f3c6ec 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards 0b74028b4ed 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards 93c12b0e95d 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards d082c300d9f 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 1ab1b551cad 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards b090318addb 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 66d9746ec43 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards ed36a95dcce 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 9c7e48d510b 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 050f3f03787 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 8a339daee9c 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 506740141f6 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 3518323a920 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 183491ecc00 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards ff202ff8e13 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards 653fe13e804 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 99f61f2924f 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 3ed80257e47 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 72757c6d3f5 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 7e484db4c2b 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards d22db1cf0f2 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards e1fd64faea5 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards ea284dc68e7 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards d587000d43f 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards af492a3f8ca 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 1f99f0ad03a 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards adbe2548b23 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 8bea0d40daa 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 77122be8fc8 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 2abba98757b 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards 94cc050870a 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards d034afff71a 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards 11b4f4fe667 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards 1939b60e9ee 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards c40bcc24d87 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards deb4c5ec230 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 622db248d8d 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 280aa83a77b 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards fe942c759ad 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards fd8cc37e878 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards 56385904c10 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards 338c337bd4f 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 19f9e78b643 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards 3b24a9ba51f 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards e6c47a0361b 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 46f7f1dc102 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 1b06ca78e8a 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards 4053e8c88ab 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards a7c44791afd 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards a967bfea29a 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards e3f627ff693 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards e32619fb2a1 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards b1b3526131c 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards 54b44e70cc5 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 62d008ca077 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 7d8cf27d4c1 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards 98c68eb3d6b 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards d2d05a1500f 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards b4836a1b3bf 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards fc71be48e8f 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards 4b2cb7ed22e 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 5d600236e6e 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards 6505dc5e47a 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 04a627d57dc 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards e8ca4698a00 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 3d5d9bbe9d2 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 86e87cac14b 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 696cf57b510 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards d5dfdeedad2 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 8852001971e 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 4039528a0b9 31: onsuccess: #38: 1: Success after linux: 14 commits discards 35abb5d85e0 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 0f73b74e5c4 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 87f7721ab59 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 172b59ec7b4 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards fd9d2354ecd 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 88fd6d50c9b 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] discards d7f4245ebbc 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] discards 97d1316642e 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards ae1552496cb 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 200217fd44b 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards 960c388bb23 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] discards f8d50cd97e7 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] new 18801f6c771 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] new e0bc5017937 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new 11f072b969c 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 801bfb63d60 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 190c8138dfe 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new 1e378c014cd 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new 1ce7cb3861f 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new 2abeeb3b891 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new ccb9e673421 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new d375ba7f630 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 5a3366e7d56 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new e3fc4d1fa74 30: onsuccess: #36: 1: Success after binutils: 18 commits new cea4f5c5c0b 31: onsuccess: #38: 1: Success after linux: 14 commits new 8622708d2b6 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 3746238f194 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 4d0f818d30f 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 200af0f453b 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 3b48730fb92 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 932107aa4cc 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 84369898759 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new bcdec55abd8 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new 083168d9865 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new 9b6e56b552e 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new 96ec59b015a 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new 56d612e6e2e 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new b02512a8867 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 1551895a935 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new 7f22f93bfca 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new 001c1d35156 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 9f83737238c 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 4feca180e41 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new 6f3fa58aebd 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 73b33b0aadd 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new b88468343c4 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new 790e00154af 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 3b706cf98ec 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 80a2ebf77d8 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new 85ae60b33e9 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 99a388395ea 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new ee51772493f 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 2ea419340b4 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new b9c87829cad 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 957ca347f22 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 26bfbc2509b 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new 44e5a76522d 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new aa6abf4c6f5 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new 27a43036084 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 11ac63259e5 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 488c76c5a7f 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new fd9fa536612 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new 180b32dffd5 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new 9b087b54f2b 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new a55c223f060 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 997b9a64339 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new b1ee3450fa3 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 4bc60ff8a57 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new c49987bd53f 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new 0ad46eab8bb 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new 167dddb3984 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 4991761bd8b 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 97e8728c064 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new 141f02bf887 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new ce79dd05f7a 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new 6a8162a4fe5 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new d1d5a8a9982 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 6101c4e99d0 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 26680287054 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 17516689044 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new 038bbd942b9 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new b09a97503b6 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 6c5b94f864e 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new 4385a096da5 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new 5ac3db46288 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 38190c79655 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 8deda5ce1bd 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 7752c3a9fc9 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 78581cb572d 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new ee5676c2897 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 7c591bd4a31 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new 621cfa2a9ce 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 77c688fd2b4 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 7cfa4d571a7 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new 12a9e507aec 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 128b2ed1c12 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new 817d4051f07 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 7ad580cce96 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 956246de081 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 7de19785dbd 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 9ea6d100b1b 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 160d7bfbb03 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 6758676969d 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 5ef9197259b 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new d2316c26767 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 3ee37514ba5 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 3b9342b3438 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 3dcdf9cc0da 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 1539d37e19b 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 816d1cb4cbf 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new e3fac1fb56e 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 98614a806a7 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 526f0c07759 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new bd76a33d70b 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...]
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 (bfa8b76453e) \ 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 1784 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2804 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 53908 -> 53052 bytes 04-build_abe-gcc/console.log.xz | Bin 238688 -> 238204 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8272 -> 8620 bytes 07-build_abe-glibc/console.log.xz | Bin 235692 -> 235268 bytes 08-build_abe-gdb/console.log.xz | Bin 50516 -> 51672 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3748 -> 3740 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2616 -> 2588 bytes 11-check_regression/console.log.xz | Bin 6144 -> 6124 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 44 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++++++++++--------------- sumfiles/gdb.log.xz | Bin 11920 -> 11932 bytes sumfiles/gdb.sum | 30 +++++++++++------------ 26 files changed, 70 insertions(+), 70 deletions(-)