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 8ce2c8c0ab1 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gc [...] discards 24805953aac 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gc [...] discards a368cfb1016 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gl [...] discards 54546eaf557 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gd [...] discards 0c20801b97f 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] discards bfb2caa3a13 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards bd0084309fc 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gl [...] discards 137046683b0 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards 34128b850d4 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] discards e67b7f32e99 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards ea6fa99f575 127: force: #27: : Failure after baseline build: no new commits discards a463d51d39c 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards a952d9af1cc 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 79cd836a2d9 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 615a074f839 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 5d48b288728 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards eb05e39f9d1 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 87a903d5a0e 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 656ffb64193 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 20bb796f355 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards b42c55f79cd 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 4ff9e73a528 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards c045040ca61 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards a96908b9475 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards f34f858bc79 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 8f8a6819611 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards bcf83cfedbf 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards fd9ca63efd3 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards bb98da69545 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards f5bd914a27e 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 06c611b53d2 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 9e40532a3f9 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] discards 309b50775d4 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards 76edee50ae5 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] discards 53027719747 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] discards d07b18b06de 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] discards 230c3009260 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] discards ad8cba49b66 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] discards 6e7f0320fa0 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] discards cfc428f55e5 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] discards 5f1bdf00173 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] discards 05eeea7d2a3 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] discards 43728628fde 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] discards 107c3aeccaf 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards d3065d6dab5 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 06dd12d140d 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] discards 6070a19573f 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards f2e84b31314 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 80666e1ef9e 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] discards 1a75c605b1d 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 2161a722aaf 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 781e89fcab3 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] discards 156f7b804d7 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] discards 28eaa3526a7 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 5cc35af9b3a 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 80e65802df9 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] discards ad1e81522c2 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards b6bcb37bac8 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 95e73951d27 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 77ab2ad9c1c 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards ca5c660b47c 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] discards b358d7634d1 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] discards 5163c85520c 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] discards 2968948ee29 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards bc6c0f50065 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 2f5bf49ba3e 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] discards dd7575011c8 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] discards 8e278a46d26 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] discards b8fc5c2f702 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 849c6ba0764 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] discards be8b7c1a876 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards fee8af2e06f 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] discards 4e530f1e513 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] discards 2cc25570168 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] discards 7a4f7a12403 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 9228b9eeafd 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] discards c2bc4fa8124 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] discards cd870b880cc 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] discards 0a5dbb9f72c 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] discards 10bf5fb6793 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 8a61f4a6b65 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 508272bca30 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards d001030ca80 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] discards fea1f701aeb 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards 245b1b1b176 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards a5de9f8c7cd 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 08091dec842 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] discards 66f505549df 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] discards 8dd6992f494 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] discards bd4609f7e56 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] discards 01ecf8b256d 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards 6e151b1df75 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 8064d71123e 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] discards 6a0e2e6d61f 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards e67ade63605 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 5e7be593be8 42: onsuccess: #53: 1: Success after linux: 3008 commits discards 3d6a1a74c3d 41: onsuccess: #51: 1: Success after binutils: 12 commits discards 5817f2e478b 40: onsuccess: #49: 1: Success after linux: 219 commits discards a6f1c326e60 39: onsuccess: #48: 1: Success after glibc: 2 commits discards 8076cddddf0 38: onsuccess: #46: 1: Success after binutils: 26 commits discards c21cdee69e4 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new f446833786b 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new e2658f80868 38: onsuccess: #46: 1: Success after binutils: 26 commits new ece40cfa14a 39: onsuccess: #48: 1: Success after glibc: 2 commits new 3a2d53e9255 40: onsuccess: #49: 1: Success after linux: 219 commits new e971c279dbb 41: onsuccess: #51: 1: Success after binutils: 12 commits new 902b8f7bf53 42: onsuccess: #53: 1: Success after linux: 3008 commits new 19c5c7a46e4 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new c22f5a5bf2c 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new cd940a38dbc 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] new 7039eb99078 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new c39fc834ff4 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new a238d8753a0 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] new 8d215647858 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] new 892c4995521 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] new 1da4214a84f 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] new cd18625d0f2 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new ff98c86b0c9 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new afd12d3ad06 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new ff0ffd9c12a 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] new bc8757eeeb2 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 257b7ee9436 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new d9c98ba3669 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 2d5f2dff321 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] new 989b2dc45f6 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] new 5e5978ced8b 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] new 03cfa842dd2 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] new 740c0c0f670 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new cfd52aaa323 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] new a77ac29fce1 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] new 01309922788 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] new 1ce9558a0ae 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 8bfa6a26c13 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] new 0bb98ddb57f 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 5b6ff1ba5c1 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] new 1bc13f6304e 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] new 128a70a8a09 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] new ab1cc1121b1 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new b8938c673ea 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new c74142733e8 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] new f7804f1dd61 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] new 2f32d8a41af 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] new ab321a9c053 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 04da1587bb7 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new f436d57ad1c 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 5ffa89dc451 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new e169d2dd4dc 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] new 7a044078bd3 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new c46ef2a6a2c 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 81891581f8e 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] new 741442a05f7 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] new 066652545f7 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 857772504ad 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 27d127db49e 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] new d701690b2f7 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 7b4cfdb661c 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new d9b131ea858 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] new f6278ca6aeb 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 40ab3383836 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new c576f0344e3 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] new 481702caec7 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] new 686ad94f143 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] new af970fc0924 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] new b3c674d4ec2 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] new fcceab61f6b 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] new cb0c3743196 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] new 44181ed49cf 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] new 47026f4abbb 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] new 048715d8ed7 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] new 8396ed7f445 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new 9c91c733f9a 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] new 45d557984ad 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new ed9f2ef3076 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new c9f793e60c4 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 056a32159b2 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 55d94c92262 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new b5d54f5ff10 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 8407d0f6adf 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new b1a64347d29 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 6bb2f5260ab 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 2d569c2981e 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 9183b000241 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 558f89ca138 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new eb04281a082 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 7a832836e49 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 0fdf703408b 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 582e683eea8 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new baeebe7f1f9 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 41af42bff49 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new b7c050dbaf3 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new e0305d02d70 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 30ae2e103fb 127: force: #27: : Failure after baseline build: no new commits new 74b183609c6 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 5c25c60eb62 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] new 1911e441656 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new 23a7278647b 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gl [...] new 56af099e2f0 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new b3f0a0b8959 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] new 09775ca6037 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gd [...] new e5f80627e8f 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gl [...] new 0ed08b14a26 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gc [...] new 78488bd3609 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gc [...] new 623b60f4679 138: onsuccess: #42: 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 (8ce2c8c0ab1) \ 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 2232 -> 2032 bytes 02-prepare_abe/console.log.xz | Bin 2528 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 35600 -> 35992 bytes 04-build_abe-gcc/console.log.xz | Bin 204200 -> 203940 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8424 -> 9600 bytes 07-build_abe-glibc/console.log.xz | Bin 242000 -> 240612 bytes 08-build_abe-gdb/console.log.xz | Bin 35092 -> 35712 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3784 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2860 -> 3712 bytes 11-check_regression/console.log.xz | Bin 4948 -> 4876 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/changes-list-long.txt | 53 +++++++++++++++++----------------- mail/changes-list-short.txt | 2 +- manifest.sh => mail/last_good.sh | 0 manifest.sh | 38 ++++++++++++------------ sumfiles/gdb.log.xz | Bin 14632 -> 14624 bytes sumfiles/gdb.sum | 4 +-- 26 files changed, 81 insertions(+), 82 deletions(-) copy manifest.sh => mail/last_good.sh (100%)