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 20d4b69c5e 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 8e02c958b1 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards f0a295e8b9 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 042bb35002 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 018c309789 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 6d4b5bb47d 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 0389990237 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards ab22886e00 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 07d5892f36 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 0506f3745a 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards cd76407f27 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 6d936fc38c 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards a3e706e887 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 3528cb2f25 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards be0d4d5a3b 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 06be7f4a91 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards fa2d7e6893 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 6ac69f5389 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards afb3ffb736 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards aad47931d7 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 13d6aace49 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards b2b95c0f6f 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 85485d1005 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 2392c5ba9b 121: force: #26: : Failure after baseline build: no new commits discards 35169faa0d 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 9ba9406773 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 18c129f421 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards fdbf8098bf 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 7bffe08078 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards dd996e577f 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards b869fb8219 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 7694571bb6 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 0c8176c88f 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards db2d078698 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 0a14f3d44d 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 21ffd9f7ea 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 9c9dbeba3f 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 2b3044fcf2 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 9d469b5ec5 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards 6605a70799 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 9539cd74d7 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 06967233a9 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards b2b9316046 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards 478065abe6 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards 8b52052270 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards b2abf8f646 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards 3081736093 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 0b944c17b9 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards 2125f1093c 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 5e6bd4ae4e 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards 0cd9ba9e2c 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards df76e059ed 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards c707105290 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards f57003d0f1 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 7e2d7b0947 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards 9ad29b84ba 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards 90bf5ac659 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 5705200b58 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards 5d92b099de 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards 5cf6fa0bb7 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards ceb1e287f5 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards f723f70552 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 9c7fb0c667 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards d345c01919 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards d36b3d73e5 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards f0dcb1b651 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards df2f59f987 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 3cf1fd068b 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 34920df5f1 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards c3ca5f2096 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards ff748b4d1e 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards 560429150b 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards a308161402 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards 8dbce22cd2 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards ef8a740f68 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards 4a1b1177e2 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards d3a287a576 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards 77bf6cb7d4 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards e64de65870 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards f8e4890c9e 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards 61cf87e566 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards 80a97e2865 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards c322bb58ce 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards d4219a98be 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards 0f0881c181 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards a9d1d335ee 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards 4350aecdd9 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards 8a577f44bd 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards a4c45efc6b 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards 091d87915a 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] discards 63364b9035 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 92773d9a36 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 2c6f49860d 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] discards c46e314622 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards e54622e12f 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] discards 31c0c7fc37 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] discards 828ff7ef83 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] discards 7595199ad2 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] discards d8e2515b36 46: onsuccess: #53: 1: Success after binutils/gcc/linux/glib [...] discards 0f5f8ddbc4 45: onsuccess: #52: 1: Success after binutils/gcc/linux/glib [...] discards 04a2bc4066 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new d0e4d42b6c 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 4094f99e70 45: onsuccess: #52: 1: Success after binutils/gcc/linux/glib [...] new fa831c42ce 46: onsuccess: #53: 1: Success after binutils/gcc/linux/glib [...] new 0b491ad90d 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] new 579063c8b8 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] new ba3c4d3030 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] new b68c4835d9 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new f0e531ada4 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 89a9528f28 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] new 885b9318e7 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 5a2b2aa2dd 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new f8536980cc 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] new 15b299fae4 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new f382ee62f3 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 933752abfa 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new 5ba5769fbd 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new 59a1db9b2f 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new e0e288f5fa 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new f799342cb9 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new 5e69e3addb 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new c86494d49f 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new eec5c1965f 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new 41ec7bcb4e 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 6138552efd 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new b6343f401c 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new 0775af1573 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new a30b0bc787 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new 8c75577e03 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 58d91fc5a0 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new fa1f23ee48 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 782c8310ac 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new f9b46c2368 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new 5b64ca2acf 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new d01e3117a8 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 4f37f98e3c 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new eb439ea7e5 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new 61bad9450f 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 6591cf2a95 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new 5224c85fcc 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new c7a70d318d 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new eb16f302e8 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new bd278e0985 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new a78ebc4163 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new 9d3974cd68 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new 68b3b93729 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 0849a0f674 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new 8b3cd4c8ea 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new d6c18e5d9b 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 926713a5a1 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new bee5e7050c 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new a5d054decc 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 3ec2aaa01e 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new 1b2c34d714 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 99262727f7 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new 74c3ee6d4e 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 9a1cbf8f4a 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new ffd3e648b1 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new dbf954f420 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new b60c875e14 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new b911874d88 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 3f9d951e8e 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new f6bf584414 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 8c3da5c70e 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new 06774d6e8c 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 9f8d0137f6 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 9cb5601c16 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 33e85bcc5b 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 3f424abbbd 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 047744e671 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 829ada5f77 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 0e5caf063d 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 6e6c9c8ca2 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 81aa265e92 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new 5f1b5ceedb 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new 8b192da825 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new f74e24d409 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 145ea7dea5 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 3e2e81d03a 121: force: #26: : Failure after baseline build: no new commits new 7c263088bd 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 7ca60e4874 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 36d69733d9 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 081a803de6 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 7b0bfdd0c4 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 4512ab46e5 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 6ddfea20be 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 739754ad5a 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 21a153f8a7 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new abfe1c014b 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 708f1100fc 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 170261da21 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new c199459d51 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new c2acb84074 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 70e7458260 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 865f9e836c 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new fe5410d039 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 121f368260 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 98ab5f3f8e 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 5da4029893 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 2969832a8e 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 3481278831 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new ef831c5161 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new a77d7c69f9 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...]
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 (20d4b69c5e) \ 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 2032 -> 2292 bytes 02-prepare_abe/console.log.xz | Bin 2528 -> 2564 bytes 03-build_abe-binutils/console.log.xz | Bin 49208 -> 49116 bytes 04-build_abe-gcc/console.log.xz | Bin 234896 -> 235872 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8256 -> 8852 bytes 07-build_abe-glibc/console.log.xz | Bin 232212 -> 232568 bytes 08-build_abe-gdb/console.log.xz | Bin 46844 -> 47028 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3812 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3132 -> 3024 bytes 11-check_regression/console.log.xz | Bin 4116 -> 1944 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 +- git/linux_rev | 2 +- jenkins/notify.sh | 3 ++ mail/changes-list-long.txt | 13 ------- mail/changes-list-short.txt | 1 - mail/check-regression-status.txt | 1 + mail/last_good.sh | 34 ----------------- mail/short-diag.txt | 1 - manifest.sh | 40 ++++++++++---------- sumfiles/gdb.log.xz | Bin 14248 -> 14244 bytes sumfiles/gdb.sum | 4 +- 29 files changed, 72 insertions(+), 115 deletions(-) create mode 100755 jenkins/notify.sh delete mode 100644 mail/changes-list-long.txt delete mode 100644 mail/changes-list-short.txt create mode 100644 mail/check-regression-status.txt delete mode 100644 mail/last_good.sh delete mode 100644 mail/short-diag.txt