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 8fd120587c8b 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards c3172196fd56 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards c091f26751ca 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards fd2b251f85eb 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards 90f8f88b6c52 131: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards 4d195c884314 130: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards add1bd10c27b 129: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards 0a7ebfc8acae 128: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards 77ebe6846f87 127: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards 2fae21e9e06a 126: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 080d4e1b9647 125: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards f98019f81f8c 124: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards 40a5e288b5d4 123: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 7f002bff595d 122: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards abec3ad70a71 121: force: #26: : Failure after baseline build: no new commits discards 5441d068440d 120: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards df5137b7efe7 119: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 55aa67d7a84d 118: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 3532865343cb 117: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 996f752b1ab2 116: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 63ca03c7917b 115: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards e52f20e8a6e3 114: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards 511e9575dd51 113: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 6be9741fdb79 112: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 54091d3d90bf 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards b8b262e744cf 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 5b528280ccc9 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards 987ced8baa21 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] discards 6153cac8fd38 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 7f3a081de9a5 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] discards d204d111a4b7 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards bdab367d8c10 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] discards b33d3397df2c 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 61281c2d4475 102: onsuccess: #123: 1: Success after binutils/gcc/linux/ [...] discards 912238b29bb7 101: onsuccess: #122: 1: Success after binutils/gcc/linux/ [...] discards e7bb52403fd3 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/ [...] discards ec0c4b00c52f 99: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards 2653088bd972 98: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] discards 27ac92cb7571 97: onsuccess: #107: 1: Success after binutils/gcc/linux/g [...] discards 617b2999e3f4 96: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] discards 2794d96f315b 95: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] discards f32125fd1362 94: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] discards 973e0f7caf5f 93: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] discards 077cdcd9b563 92: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] discards 94980f68b6c7 91: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] discards 57e2775619e2 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gd [...] discards 190c58b6d279 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gl [...] discards be75d75e2a78 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] discards a483a8104441 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gl [...] discards 1de5ac1045a5 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gl [...] discards d1d01691ca05 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] discards bef107ae2248 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] discards 17aa4ab41091 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] discards 7659102c4ded 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] discards 1ae520f84203 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gl [...] discards 918fa27347b0 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 [...] discards 4ae5505d1fd9 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gd [...] discards 8008376acf09 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] discards a60a2fd61a37 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] discards b0adefc4dfe3 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gd [...] discards adb654e92b39 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gd [...] discards ff42b7cd6733 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gd [...] discards 350cfecb6f12 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] discards 35183e982c81 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gl [...] discards 98e6a474637f 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] discards 3a41927f8efd 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gl [...] discards c060b1080b2a 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gd [...] discards 660f8429d711 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gl [...] discards 74225ec19e5f 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] discards 67dbad024376 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 6ad3faf3fb29 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gd [...] discards aae1083b8ce8 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gl [...] discards a4e2c7e9fec8 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] discards 31e3ae4c25bf 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gl [...] discards 61068faec27f 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gd [...] discards 44fe0c2f3ea9 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 [...] discards 225039253f26 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gl [...] discards 8fb1829c839e 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gd [...] discards 8909a96b4877 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] discards bbf326140441 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] discards 8670e6efd634 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gd [...] discards 7da9349ca66b 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards ebafd8312db6 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards f5c571586210 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gd [...] discards 59ec2509f9f4 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 6332d4805bf4 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] discards fcd99f09bf6f 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gd [...] discards 1dedcf057511 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] discards 1324e05e1477 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] discards 37a83bc31dce 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gl [...] discards ec36a4de5aa2 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gl [...] discards 4f57c42f95cb 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 6f272455ccfc 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gd [...] discards d309de0785cb 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gd [...] discards 1ad59195c842 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gl [...] discards 5923b0a5add6 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gl [...] discards 7f1f9145206c 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gd [...] discards 942439c95d85 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gl [...] discards aeb786b7629a 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gd [...] discards 189ecf89b5e0 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gd [...] discards 377e5465ae0a 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gl [...] new 95770f137eff 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gl [...] new 57323ec3b8d6 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gd [...] new 9a44979f765d 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gd [...] new 82c6ce5dae5a 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gl [...] new ad49c4b14d38 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gd [...] new da1c3d3267dc 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gl [...] new 5b5433ccf0f1 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gl [...] new 5c064bdd5918 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gd [...] new 450ee8b6c583 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gd [...] new aad0736264ba 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new d19d5942481a 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gl [...] new 7cfed11a10bc 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gl [...] new 5ac3cd28ee45 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] new 429496b8c866 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] new ac0acdf2b896 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gd [...] new 3562a297b9a1 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] new 456953e1b8e6 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new c8eab267bb89 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gd [...] new e2029c206c2b 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new af5206a99db5 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 55c290792c8f 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gd [...] new 860a31f69d98 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] new efa960f05332 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] new 7508688ef19c 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gd [...] new 09d6c2008caf 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gl [...] new a2038a0437c5 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 [...] new 4a8c0c07d151 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gd [...] new 37edd5f8e5a8 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gl [...] new 2f24bead0f9e 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] new 45b4d25093d4 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gl [...] new d57265f44a25 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gd [...] new 5aab17ca06e4 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new a69a361cb67c 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] new b6cdda523241 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gl [...] new 75dfa4826efa 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gd [...] new 29a5dfa7d062 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gl [...] new 8f30c52244e2 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] new 86cdf1bfe0e4 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gl [...] new d8751b7140b9 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] new 49663542369c 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gd [...] new 7d507e156b10 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gd [...] new 2b46f2a50c5f 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gd [...] new 0f3071fab09a 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] new 8838f9a7b4f6 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] new 9abf8af0cb5e 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gd [...] new fa414d6fdd0a 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 [...] new 899e72a588cc 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gl [...] new e6c18c805dc1 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] new 0cdf06f8db44 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] new 897c0142d8f9 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] new 2d04ae3f81a5 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] new 6f395199c317 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gl [...] new 79a398bc3dd9 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gl [...] new 9fe9881b7e21 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] new b6824aa1a418 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gl [...] new ce445ad6ae9d 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gd [...] new a1eb4bf2cc81 91: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] new 5d1a4e127d2e 92: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] new 5a757d550088 93: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] new 3e8957e1f249 94: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] new d420fc562d16 95: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] new 266438905c74 96: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] new acb2deed8cb8 97: onsuccess: #107: 1: Success after binutils/gcc/linux/g [...] new 9255be5f7f83 98: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] new 744969c5de6b 99: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new a314485e9fe3 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/ [...] new 9ab4d5b1c3c6 101: onsuccess: #122: 1: Success after binutils/gcc/linux/ [...] new 776cb2df7fcc 102: onsuccess: #123: 1: Success after binutils/gcc/linux/ [...] new ad3614f11ac6 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 9ee46aeb8c2d 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] new 9c0b5150d1af 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 54e7dbcc6009 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] new 5b61886db3ce 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new cbd948eb0b9f 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] new e01100fafedd 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 28f92819bcc1 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new abbeaa139bca 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new ebd3be2f63c3 112: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 9e6c0cfdada8 113: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new fbb5812f561d 114: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new f5823a263b4e 115: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new d8d39a25e537 116: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new d4973cfae470 117: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 468200e455e5 118: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new be57a6026661 119: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new f21d85015bba 120: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 8883d150a6bd 121: force: #26: : Failure after baseline build: no new commits new a90066b12596 122: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new bbd8efcd4ba2 123: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 9f1d81587bd3 124: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new c5ae9f0c602a 125: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new 94c303849a17 126: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new d64582126db6 127: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new b13cbb103eb9 128: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new a585f4291ef1 129: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new ca3aa4094c8c 130: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new ac10a69d787b 131: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new 5abe5e94da8d 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 262420cf422d 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new 3f634a12f64d 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 42ef5b1eec74 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new 3a0260dd088b 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...]

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 (8fd120587c8b) \ 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 2256 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2516 -> 2540 bytes 03-build_abe-binutils/console.log.xz | Bin 50064 -> 49712 bytes 04-build_abe-gcc/console.log.xz | Bin 235576 -> 237772 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8596 -> 8708 bytes 07-build_abe-glibc/console.log.xz | Bin 232544 -> 232028 bytes 08-build_abe-gdb/console.log.xz | Bin 47400 -> 47208 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3000 -> 3344 bytes 11-check_regression/console.log.xz | Bin 4868 -> 4500 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 36 ++++++++++++++-------------- 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 | 43 ++++++++++++++-------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 36 ++++++++++++++-------------- manifest.sh | 32 ++++++++++++------------- sumfiles/gdb.log.xz | Bin 14428 -> 14436 bytes sumfiles/gdb.sum | 4 ++-- 25 files changed, 82 insertions(+), 91 deletions(-)