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-aarch64 in repository toolchain/ci/base-artifacts.

discards 6da2ef63c1e 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gc [...] discards c1db9fcd211 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gl [...] discards a6c6e41dbdd 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gd [...] discards 92c9b82b76a 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] discards e352a6a71e4 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards 275a9a038bd 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gl [...] discards ccf90c9e2d8 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards 5ce6a48ae55 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] discards 5cc1c760a3e 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 8bd066596cd 127: force: #27: : Failure after baseline build: no new commits discards 2ab325e084d 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 1e36aa84273 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 962d68c9ee8 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 4df1cd1cf62 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 536cbfee095 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 4d8fc27c9ec 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 72024347c12 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 3676781b106 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 96b6cfbf498 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards df0865e0beb 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 95692aaf623 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 307171f5c7e 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 5fde1ae3ea1 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards d7b228d65ec 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 2a698ea02f7 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards f10afd8ea94 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 0fbd8a4a2a5 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards beca89f944c 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards b1a7fdf121a 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 13b3aa5e867 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards ae0c0d92cf0 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] discards 440dc8e0944 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards 1b38871b7ad 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] discards 4aecfeb489b 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] discards 0f821f416bb 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] discards 417cdc36efc 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] discards c3e703bfe26 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] discards 38476735cf9 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] discards dcc5c460b4d 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] discards e9458c4265c 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] discards 2941bff4c36 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] discards 541db7f7f8e 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] discards fdbc75325d5 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards ea8802d6005 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 9853b0ac207 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] discards f9c514a5030 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards bf2484fe134 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 5afa91fa35f 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] discards 60da04e83b1 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards d92cfc3c326 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards d526a7a706e 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] discards fd4eda80156 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] discards 4f4b91d3cfb 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 5cf8d59ff37 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards b62a51b4622 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] discards 20ac2c3d556 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 51ff4223c0e 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 9b62b3aa3f6 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 0f210ccbfb6 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards 2583bb7391d 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] discards 98af8664cb1 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] discards cf0a4ea8dc8 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] discards c45dce4fcc9 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 1054137f69a 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards e79bfde3f2e 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] discards b3625a3ed14 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] discards 24abec1767e 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] discards 83ff95001f9 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards a6b5089c651 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] discards 6ede976fe9e 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards f4a5a98e1b6 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] discards 25552e1bc76 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] discards 949e35d320b 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] discards 7ffbd70114d 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 945a8e8e5ca 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] discards e7d9276cc94 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] discards aeee0741b11 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] discards a6ed2fc9893 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] discards c035bd618cc 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 5a0cdcd97d3 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 3c40c72af31 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 07c2f2bdf21 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] discards fbfb779d5c0 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards 73727850868 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 03b7fdb9990 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 46479b0a959 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] discards 4d5c4cba527 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] discards bb25361188a 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] discards 8098cd653a6 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] discards 1d25e828d0e 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards e98a2809c30 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 4c8b4e1428b 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] discards c82e2d7d6aa 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 0783c8a5e0b 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards d8a8dbedd6c 42: onsuccess: #53: 1: Success after linux: 3008 commits discards a27f6ac5ad4 41: onsuccess: #51: 1: Success after binutils: 12 commits discards 9953469d6d9 40: onsuccess: #49: 1: Success after linux: 219 commits discards e9ac21c35c2 39: onsuccess: #48: 1: Success after glibc: 2 commits discards 8d3b184c4fe 38: onsuccess: #46: 1: Success after binutils: 26 commits discards a2b99a4dac9 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 04300f4becf 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 79b7e745157 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new c21cdee69e4 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 8076cddddf0 38: onsuccess: #46: 1: Success after binutils: 26 commits new a6f1c326e60 39: onsuccess: #48: 1: Success after glibc: 2 commits new 5817f2e478b 40: onsuccess: #49: 1: Success after linux: 219 commits new 3d6a1a74c3d 41: onsuccess: #51: 1: Success after binutils: 12 commits new 5e7be593be8 42: onsuccess: #53: 1: Success after linux: 3008 commits new e67ade63605 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 6a0e2e6d61f 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 8064d71123e 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] new 6e151b1df75 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 01ecf8b256d 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new bd4609f7e56 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] new 8dd6992f494 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] new 66f505549df 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] new 08091dec842 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] new a5de9f8c7cd 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 245b1b1b176 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new fea1f701aeb 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new d001030ca80 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] new 508272bca30 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 8a61f4a6b65 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 10bf5fb6793 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 0a5dbb9f72c 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] new cd870b880cc 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] new c2bc4fa8124 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] new 9228b9eeafd 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] new 7a4f7a12403 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 2cc25570168 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] new 4e530f1e513 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] new fee8af2e06f 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] new be8b7c1a876 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 849c6ba0764 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] new b8fc5c2f702 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 8e278a46d26 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] new dd7575011c8 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] new 2f5bf49ba3e 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] new bc6c0f50065 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 2968948ee29 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 5163c85520c 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] new b358d7634d1 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] new ca5c660b47c 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] new 77ab2ad9c1c 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 95e73951d27 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new b6bcb37bac8 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new ad1e81522c2 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 80e65802df9 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] new 5cc35af9b3a 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 28eaa3526a7 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 156f7b804d7 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] new 781e89fcab3 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] new 2161a722aaf 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 1a75c605b1d 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 80666e1ef9e 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] new f2e84b31314 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 6070a19573f 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 06dd12d140d 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] new d3065d6dab5 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 107c3aeccaf 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 43728628fde 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] new 05eeea7d2a3 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] new 5f1bdf00173 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] new cfc428f55e5 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] new 6e7f0320fa0 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] new ad8cba49b66 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] new 230c3009260 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] new d07b18b06de 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] new 53027719747 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] new 76edee50ae5 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] new 309b50775d4 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new 9e40532a3f9 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] new 06c611b53d2 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new f5bd914a27e 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new bb98da69545 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new fd9ca63efd3 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new bcf83cfedbf 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 8f8a6819611 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new f34f858bc79 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new a96908b9475 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new c045040ca61 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 4ff9e73a528 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new b42c55f79cd 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 20bb796f355 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 656ffb64193 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 87a903d5a0e 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new eb05e39f9d1 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 5d48b288728 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 615a074f839 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 79cd836a2d9 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new a952d9af1cc 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new a463d51d39c 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new ea6fa99f575 127: force: #27: : Failure after baseline build: no new commits new e67b7f32e99 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 34128b850d4 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] new 137046683b0 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new bd0084309fc 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gl [...] new bfb2caa3a13 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new 0c20801b97f 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] new 54546eaf557 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gd [...] new a368cfb1016 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gl [...] new 24805953aac 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gc [...] new 8ce2c8c0ab1 137: onsuccess: #41: 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 (6da2ef63c1e) \ 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 2028 -> 2232 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 35064 -> 35600 bytes 04-build_abe-gcc/console.log.xz | Bin 204092 -> 204200 bytes 06-build_abe-linux/console.log.xz | Bin 8576 -> 8424 bytes 07-build_abe-glibc/console.log.xz | Bin 240948 -> 242000 bytes 08-build_abe-gdb/console.log.xz | Bin 34844 -> 35092 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3832 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2716 -> 2860 bytes 11-check_regression/console.log.xz | Bin 5100 -> 4948 bytes 11-check_regression/results.compare2 | 4 +-- 12-update_baseline/console.log | 58 +++++++++++++++++----------------- 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/changes-list-long.txt | 57 ++++++++++++++++----------------- mail/changes-list-short.txt | 2 +- manifest.sh | 36 ++++++++++----------- sumfiles/gdb.log.xz | Bin 14644 -> 14632 bytes sumfiles/gdb.sum | 4 +-- 23 files changed, 85 insertions(+), 88 deletions(-)