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 3a0260dd088b 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] discards 42ef5b1eec74 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards 3f634a12f64d 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards 262420cf422d 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards 5abe5e94da8d 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards ac10a69d787b 131: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards ca3aa4094c8c 130: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards a585f4291ef1 129: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards b13cbb103eb9 128: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards d64582126db6 127: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards 94c303849a17 126: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards c5ae9f0c602a 125: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards 9f1d81587bd3 124: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards bbd8efcd4ba2 123: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards a90066b12596 122: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 8883d150a6bd 121: force: #26: : Failure after baseline build: no new commits discards f21d85015bba 120: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards be57a6026661 119: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 468200e455e5 118: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards d4973cfae470 117: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards d8d39a25e537 116: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards f5823a263b4e 115: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards fbb5812f561d 114: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards 9e6c0cfdada8 113: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards ebd3be2f63c3 112: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards abbeaa139bca 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 28f92819bcc1 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards e01100fafedd 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards cbd948eb0b9f 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] discards 5b61886db3ce 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 54e7dbcc6009 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] discards 9c0b5150d1af 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 9ee46aeb8c2d 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] discards ad3614f11ac6 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 776cb2df7fcc 102: onsuccess: #123: 1: Success after binutils/gcc/linux/ [...] discards 9ab4d5b1c3c6 101: onsuccess: #122: 1: Success after binutils/gcc/linux/ [...] discards a314485e9fe3 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/ [...] discards 744969c5de6b 99: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards 9255be5f7f83 98: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] discards acb2deed8cb8 97: onsuccess: #107: 1: Success after binutils/gcc/linux/g [...] discards 266438905c74 96: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] discards d420fc562d16 95: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] discards 3e8957e1f249 94: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] discards 5a757d550088 93: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] discards 5d1a4e127d2e 92: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] discards a1eb4bf2cc81 91: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] discards ce445ad6ae9d 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gd [...] discards b6824aa1a418 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gl [...] discards 9fe9881b7e21 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] discards 79a398bc3dd9 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gl [...] discards 6f395199c317 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gl [...] discards 2d04ae3f81a5 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] discards 897c0142d8f9 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] discards 0cdf06f8db44 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] discards e6c18c805dc1 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] discards 899e72a588cc 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gl [...] discards fa414d6fdd0a 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 [...] discards 9abf8af0cb5e 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gd [...] discards 8838f9a7b4f6 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] discards 0f3071fab09a 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] discards 2b46f2a50c5f 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gd [...] discards 7d507e156b10 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gd [...] discards 49663542369c 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gd [...] discards d8751b7140b9 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] discards 86cdf1bfe0e4 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gl [...] discards 8f30c52244e2 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] discards 29a5dfa7d062 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gl [...] discards 75dfa4826efa 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gd [...] discards b6cdda523241 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gl [...] discards a69a361cb67c 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] discards 5aab17ca06e4 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards d57265f44a25 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gd [...] discards 45b4d25093d4 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gl [...] discards 2f24bead0f9e 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] discards 37edd5f8e5a8 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gl [...] discards 4a8c0c07d151 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gd [...] discards a2038a0437c5 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 [...] discards 09d6c2008caf 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gl [...] discards 7508688ef19c 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gd [...] discards efa960f05332 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] discards 860a31f69d98 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] discards 55c290792c8f 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gd [...] discards af5206a99db5 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards e2029c206c2b 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards c8eab267bb89 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gd [...] discards 456953e1b8e6 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 3562a297b9a1 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] discards ac0acdf2b896 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gd [...] discards 429496b8c866 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] discards 5ac3cd28ee45 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] discards 7cfed11a10bc 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gl [...] discards d19d5942481a 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gl [...] discards aad0736264ba 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 450ee8b6c583 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gd [...] discards 5c064bdd5918 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gd [...] discards 5b5433ccf0f1 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gl [...] discards da1c3d3267dc 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gl [...] discards ad49c4b14d38 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gd [...] discards 82c6ce5dae5a 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gl [...] discards 9a44979f765d 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gd [...] discards 57323ec3b8d6 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gd [...] new 337bdec93794 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gd [...] new 8f901a61295c 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gd [...] new a00d4f4524df 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gl [...] new b29f14e87431 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gd [...] new 56f491a8e4fd 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gl [...] new 64eb3bf15963 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gl [...] new e98c21c1744d 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gd [...] new 4cc16bf36db1 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gd [...] new 9d7228c4f430 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 84bdd935f70c 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gl [...] new b7d236506cbd 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gl [...] new ac8e50d5ba11 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] new 359aad3c43ca 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] new e64556752313 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gd [...] new fdf93d178751 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] new 3adbe3cb4fae 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 59e47b921042 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gd [...] new d305690bfa30 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new fb84ced8f401 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 1f3ade66d7c9 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gd [...] new cf92c0b97cd4 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] new 812d6687691b 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] new bd47f71c84db 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gd [...] new 42f8a9689dfb 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gl [...] new 917c731203cf 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 [...] new 7874eff2bd28 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gd [...] new 4aee9cbc08f6 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gl [...] new 9f5628be5996 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] new 1aa3cd96b1c5 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gl [...] new 66318d8fd972 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gd [...] new 696dc0cfd616 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 2ea4c8c9151d 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] new 8b9aefe61e9f 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gl [...] new 9bb9f5c26d52 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gd [...] new 4c30f0137a81 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gl [...] new ecb28d08a6c4 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] new dc51f158258d 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gl [...] new 07677c0cb618 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] new 6482dc6a43ea 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gd [...] new 06e5b083c7bb 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gd [...] new 07e23abf5c6c 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gd [...] new 82419aac2d03 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] new 6c78c2c440d2 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] new 42daccd496cc 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gd [...] new adfcb10c9177 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 [...] new 6a2784fa2bd9 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gl [...] new eddaa635a37a 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] new 40ee9f2facd8 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] new 7dfbc8e2f2ba 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] new 7c25567c3eec 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] new 3a6ec04db157 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gl [...] new 346813260c7d 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gl [...] new eeac12c58643 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] new ebc78ff55f07 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gl [...] new 72001c02689e 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gd [...] new 4b0611191504 91: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] new 80bde34e7f09 92: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] new 16aefb88a254 93: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] new ea3b5c516829 94: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] new a230646d4f3f 95: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] new 3cd0643aa9f2 96: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] new 73de783ab917 97: onsuccess: #107: 1: Success after binutils/gcc/linux/g [...] new 58eeb703b460 98: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] new 15a04fe24f07 99: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new 2f3d5f6bc8e5 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/ [...] new 3cdfd0995bda 101: onsuccess: #122: 1: Success after binutils/gcc/linux/ [...] new b395f059bfbd 102: onsuccess: #123: 1: Success after binutils/gcc/linux/ [...] new a160d566b3cb 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 33b8e1d234b8 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] new 071b4d46acea 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 9104da9d2837 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] new 373b41504adb 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new cd7af6475ae0 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] new 13e0c268ebf2 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new fb4a197ea1ab 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 6fbfc7c7fa1b 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 9ce1942e4b69 112: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new b16cdda49d1c 113: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 97153be525c9 114: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new f82fe94c0f2d 115: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 621dc9b12a5f 116: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new cc39fde7028c 117: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 18579ddf274f 118: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 9bc991d0a65d 119: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 62c4a627f354 120: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new edcb893f5de7 121: force: #26: : Failure after baseline build: no new commits new e9d593c65fdd 122: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 631c0cf04723 123: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 057724b1e35e 124: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 5cf37d676d16 125: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new 6d51debbb828 126: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 9a2dbe92a38f 127: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new bfde7589bb2f 128: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 51f9be6d9ccf 129: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new 2bbc347bde38 130: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new 3dfe7c09e159 131: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new e02963839ba6 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 4e01f3501ccf 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new da1f19a705c9 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 20532bff82ac 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new 50045b96b953 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] new 090d160c29f1 137: onsuccess: #44: 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 (3a0260dd088b) \ 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 2072 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2540 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 49712 -> 49356 bytes 04-build_abe-gcc/console.log.xz | Bin 237772 -> 236412 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8708 -> 8480 bytes 07-build_abe-glibc/console.log.xz | Bin 232028 -> 232780 bytes 08-build_abe-gdb/console.log.xz | Bin 47208 -> 47332 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3760 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3344 -> 2784 bytes 11-check_regression/console.log.xz | Bin 4500 -> 4404 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 42 +++++++++++++++++----------------- 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 | 30 ++++++++++++------------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 +++++++++++++------------- manifest.sh | 32 +++++++++++++------------- sumfiles/gdb.log.xz | Bin 14436 -> 14444 bytes sumfiles/gdb.sum | 4 ++-- 25 files changed, 80 insertions(+), 82 deletions(-)