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 4b2f18a351c 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gc [...] discards 47766b00e8c 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gl [...] discards e8b48c8bd7f 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] discards b264ffc1ac6 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards 2a2b7d12ce5 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards 1f01bafb196 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] discards baf3c4bebee 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] discards ec3327554c5 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 1438c79c199 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 464deac6488 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 8c4cb6b75c3 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards dd7691ca033 121: force: #26: : Failure after baseline build: no new commits discards ec7935eb063 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 8abcb736db6 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 4401ef10513 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 310b70174f9 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 9bcc97ef33e 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 5c0683dd03b 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 8de90255302 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards a23868e02a6 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 8ac4498208b 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards ac272ba2ae3 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 1fc63313c12 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards c4977297949 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards d57260d82b6 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards abf68736a3e 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 8510a3e9e9c 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 435fe00b7d6 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 6b8a8afb73c 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards c9fc24029fe 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 55e56a0da6a 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards 3a806223ace 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards d3e0fc5685e 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards 83d3f93acdb 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 138b43f2819 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 4e0b2efee08 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards bd9e8bde1e0 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards fe7d946b57c 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards 628fe377b6a 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 0f90e2c3fa5 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards ec030133642 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 1bb55a2c005 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 138fb685876 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 20f79b58769 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 0ea294c1a2b 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 9ad2d6f1040 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards ae0386f12c0 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards fdb0406a8c7 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards f0664068560 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 32b74b9e1ba 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 07e5b69e041 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards cd5121eb18c 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards a289d7cda78 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards edab1b6c8ff 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards 8b8dad2a0a7 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 9a0dbed0743 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 1051553765d 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards 9cc2dcae95d 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 7576fe06766 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 11d47a7204f 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 4a56f3d56f3 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards a5c7d9b27cb 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 3feab57ff72 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards 0dfd91cb703 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards d0c8d0706ec 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards 52c46fc2703 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards c8feaf4f0e1 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards b0d7ee78d5b 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 1790ca4ab0d 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards b3bdc959c26 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 7e49461c8a9 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards e5a42b6d222 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards cf847c607c2 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 5dc12dec343 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards 482699c01b2 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 6c1f697b9e4 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 56cd0ef8c9e 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards b7cbacd1337 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards 2a6a2f867db 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards ef200bc8674 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 4d656707a1f 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards cba3bc99683 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards aebc850dcbb 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 2adcf1aae5b 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards d481ee693a0 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 32eaa1a8f97 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 66f5baf9cf4 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards ed2f02077ed 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards 1daf02b0283 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 736ae1ac3b2 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards 3cbe5651e6c 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards 4d3e8d7a465 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards c1533967497 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards 6c876c22726 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards dc1d2198c45 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards 6da430bfb14 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 4d2209743a6 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards a56fbe99fe2 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 0be3f40934c 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 000d7744215 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 4557969e428 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 76b2f09eaab 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 67e2354c1a6 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 7cbe9ee8f5a 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 58b57e57a2e 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new cc0c6f7faa2 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 65bde5bc9d3 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 1af7f1a9131 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new a365a62ff05 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new 475fddffd28 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new c0edde7c1af 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new 128d92ef7b3 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new 4587ecc0916 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new fc222bfcc43 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 379e2835fd2 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new 6b736f18980 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new 9fd604e8b0d 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 253637829ff 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 5bc21117df6 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new 35dfac1442e 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new bfb83afe69c 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new d034f128e85 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new 4d3bf01fa4d 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new b38de214e11 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 3fafbd3a054 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new 8d9f1066c22 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new d10fe1c4136 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 58b1bf4fed5 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 5b829774c28 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new c05b61eb3ba 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new af2a222c454 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 0d53a4b937c 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new 4c85902431b 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new f8c319b7160 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new 02e1dbc7bd0 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 90417197842 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new b5fdeba2f51 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 4e75ff54415 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new b793c23666d 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new e75001f84f4 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new 4981007799f 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 9a907ed995e 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 52bb6d05a96 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 1d5b436088f 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new 737c1462b03 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new 4bd8cef25d4 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new 3298bea36a4 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new cf3a51b0d64 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 62c244c7118 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new 7efabeae118 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new b77b4751533 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new 7257dad943e 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 6cb82f88f3f 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 67c45b33dc4 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 8b9866ee65f 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new ebbe61dd7ac 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new 4cc36ed1544 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 6d0e306a0b3 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 71ba9498329 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new 3ccf2b086a0 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new 10350797161 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 4094d7c20fb 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 50a774d0666 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new cd4d3043c5c 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 91b3843d462 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new 348c9d3a4e1 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new b93895ec458 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new cc6cd9c652c 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 930aa1e92f6 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 8b290475498 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new 9b4aef5f65c 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 7745935f9c7 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new 11e7eb300aa 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new de4df5f4394 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new e04f22d7d26 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new b0f90d66856 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new e3c54df5c19 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 9e42b36bd0c 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 690a47b5146 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 8dff3312e2f 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new eb20b2f0b69 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new c1a0548127b 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 7e8af6bcf4b 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new eb92b5e8115 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 529398eea34 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 12fb0e3125a 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 73563d7fcb5 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new c8b4b322b76 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 0677a298403 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 41a3545c10f 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new a9e2d18d459 121: force: #26: : Failure after baseline build: no new commits new 6a70c77d780 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new e0ffe0861dd 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 5afac8bcf56 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 14f34bda315 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new fad5c17ffaa 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] new 13e9850265f 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] new cf7997c7bd8 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new ed11aa8a6fc 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new 25b6ab75496 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] new c403e29c6e3 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gl [...] new 3598a466feb 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gc [...] new dbebe066674 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gc [...]
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 (4b2f18a351c) \ 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 2260 -> 2032 bytes 02-prepare_abe/console.log.xz | Bin 2552 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 50148 -> 48832 bytes 04-build_abe-gcc/console.log.xz | Bin 237464 -> 235708 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8784 -> 8388 bytes 07-build_abe-glibc/console.log.xz | Bin 232348 -> 232956 bytes 08-build_abe-gdb/console.log.xz | Bin 46788 -> 47468 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3772 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3108 -> 2864 bytes 11-check_regression/console.log.xz | Bin 5132 -> 4600 bytes 11-check_regression/results.compare | 4 +-- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 66 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 56 +++++++++++++---------------- mail/changes-list-short.txt | 2 +- manifest.sh | 32 ++++++++--------- sumfiles/gdb.log.xz | Bin 14452 -> 14440 bytes sumfiles/gdb.sum | 4 +-- 24 files changed, 87 insertions(+), 93 deletions(-)