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 be7ba35e1e 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards c72c3271c0 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards cc6da63efd 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 7741f7e764 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 6cd883295a 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards fb4673f2f6 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards a9f100ae03 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 007e842e2e 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 181b8bc404 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 4f31aef00a 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards f9823bca1e 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 84b1916472 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards ef5b5c0e8f 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 94d5e174cc 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 85a6e9d328 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards aab5bc6da0 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards baba1a91aa 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 6a9e631237 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 78ce7648c2 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards becc37baa8 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 9e07b90efd 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 4e66b7f79e 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 457c5cf76e 121: force: #26: : Failure after baseline build: no new commits discards feccbd54dd 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards a433672abb 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 3167f30f20 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 214bb55917 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards c701639b9c 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards ae4e720a41 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 4e0378bfdf 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 768016fd45 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 007deefbc3 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 49a59a4779 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 70b73625dd 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards ef57f6858a 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 9b247d2848 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards b6ba9bf4a8 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 8ab6fc6553 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards 94f36ca958 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards bb650e5187 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 707b5d3363 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards c8d1f2fb30 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards 569771f281 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards f046072aed 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards 73ca5e4ad8 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards a0bebea879 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 01e32e34d6 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards 9eeac743a2 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards a020b6eb71 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards 6d906875a5 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards e8200e595a 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards ef623ca1b8 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards eb7dd5879a 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards bc68f7f6ec 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards 4060df54da 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards 4f042de119 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 7b1eb678cf 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards ba78adcf58 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards c93e9a5c4f 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 8a0c7bbccc 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 3cc9660ab3 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 678ddcb50b 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards f05d75b0a4 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards 759f20a758 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 75c5f2a09b 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards 496bc84f1f 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 6da7612c18 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 1d827b82f7 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards 783c9b4929 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards eb3e6f08b6 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards 30d54433f1 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 02f8317e57 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards 7cb74ca5b0 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 4ab26a0881 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards 1a5d8ca2c0 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards 407c5821e1 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards b60f309c79 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards cb18edf92d 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 3c89c7be33 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards 9aedcead88 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards 9c8d15465a 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards 22b0c697b9 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards c6cb5d4b07 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards 17d43d452e 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards aab79de62d 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards 0656f4e7fc 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards 848fe380e4 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 43c13f39b8 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards 50f3d347d5 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] discards 99e9db7797 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards aba61857b8 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards ab4a003e1b 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] discards 0597615cc6 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 86add57fbb 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] discards ab2421b6fc 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] discards fcd22f4637 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] discards 6ef9fb13c2 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] discards d0de3bb164 46: onsuccess: #53: 1: Success after binutils/gcc/linux/glib [...] discards 7693592726 45: onsuccess: #52: 1: Success after binutils/gcc/linux/glib [...] discards d56fc6c19f 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 0a51935877 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb: [...] new 98b942efb6 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb: [...] new 04a2bc4066 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 0f5f8ddbc4 45: onsuccess: #52: 1: Success after binutils/gcc/linux/glib [...] new d8e2515b36 46: onsuccess: #53: 1: Success after binutils/gcc/linux/glib [...] new 7595199ad2 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] new 828ff7ef83 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] new 31c0c7fc37 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] new e54622e12f 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new c46e314622 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 2c6f49860d 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] new 92773d9a36 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 63364b9035 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 091d87915a 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] new a4c45efc6b 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new 8a577f44bd 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 4350aecdd9 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new a9d1d335ee 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new 0f0881c181 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new d4219a98be 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new c322bb58ce 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new 80a97e2865 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new 61cf87e566 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new f8e4890c9e 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new e64de65870 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 77bf6cb7d4 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new d3a287a576 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new 4a1b1177e2 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new ef8a740f68 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new 8dbce22cd2 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new a308161402 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new 560429150b 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new ff748b4d1e 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new c3ca5f2096 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new 34920df5f1 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new 3cf1fd068b 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new df2f59f987 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new f0dcb1b651 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new d36b3d73e5 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new d345c01919 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new 9c7fb0c667 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new f723f70552 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new ceb1e287f5 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 5cf6fa0bb7 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 5d92b099de 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new 5705200b58 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new 90bf5ac659 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 9ad29b84ba 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new 7e2d7b0947 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new f57003d0f1 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new c707105290 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new df76e059ed 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 0cd9ba9e2c 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 5e6bd4ae4e 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new 2125f1093c 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 0b944c17b9 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new 3081736093 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new b2abf8f646 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new 8b52052270 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new 478065abe6 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new b2b9316046 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new 06967233a9 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 9539cd74d7 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 6605a70799 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 9d469b5ec5 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new 2b3044fcf2 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 9c9dbeba3f 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 21ffd9f7ea 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 0a14f3d44d 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new db2d078698 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 0c8176c88f 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 7694571bb6 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new b869fb8219 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new dd996e577f 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 7bffe08078 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new fdbf8098bf 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new 18c129f421 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 9ba9406773 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 35169faa0d 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 2392c5ba9b 121: force: #26: : Failure after baseline build: no new commits new 85485d1005 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new b2b95c0f6f 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 13d6aace49 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new aad47931d7 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new afb3ffb736 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 6ac69f5389 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new fa2d7e6893 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 06be7f4a91 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new be0d4d5a3b 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 3528cb2f25 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new a3e706e887 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 6d936fc38c 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new cd76407f27 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 0506f3745a 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 07d5892f36 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new ab22886e00 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 0389990237 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 6d4b5bb47d 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 018c309789 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 042bb35002 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new f0a295e8b9 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 8e02c958b1 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 20d4b69c5e 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...]
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 (be7ba35e1e) \ 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 2092 -> 2032 bytes 02-prepare_abe/console.log.xz | Bin 2544 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 49172 -> 49208 bytes 04-build_abe-gcc/console.log.xz | Bin 235780 -> 234896 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8296 -> 8256 bytes 07-build_abe-glibc/console.log.xz | Bin 232244 -> 232212 bytes 08-build_abe-gdb/console.log.xz | Bin 46548 -> 46844 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3800 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2796 -> 3132 bytes 11-check_regression/console.log.xz | Bin 4628 -> 4116 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 6 +-- 12-update_baseline/console.log | 68 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/changes-list-long.txt | 28 ++++++-------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 36 +++++++++--------- manifest.sh | 34 ++++++++--------- sumfiles/gdb.log.xz | Bin 14256 -> 14248 bytes sumfiles/gdb.sum | 4 +- 25 files changed, 94 insertions(+), 98 deletions(-)