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 a77d7c69f9 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards ef831c5161 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 3481278831 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 2969832a8e 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 5da4029893 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 98ab5f3f8e 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 121f368260 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards fe5410d039 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 865f9e836c 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 70e7458260 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards c2acb84074 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards c199459d51 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 170261da21 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 708f1100fc 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards abfe1c014b 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 21a153f8a7 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 739754ad5a 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 6ddfea20be 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 4512ab46e5 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 7b0bfdd0c4 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 081a803de6 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 36d69733d9 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 7ca60e4874 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 7c263088bd 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 3e2e81d03a 121: force: #26: : Failure after baseline build: no new commits discards 145ea7dea5 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards f74e24d409 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 8b192da825 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 5f1b5ceedb 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 81aa265e92 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards 6e6c9c8ca2 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 0e5caf063d 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 829ada5f77 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 047744e671 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 3f424abbbd 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 33e85bcc5b 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 9cb5601c16 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 9f8d0137f6 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 06774d6e8c 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 8c3da5c70e 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards f6bf584414 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 3f9d951e8e 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards b911874d88 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards b60c875e14 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards dbf954f420 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards ffd3e648b1 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards 9a1cbf8f4a 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards 74c3ee6d4e 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 99262727f7 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards 1b2c34d714 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 3ec2aaa01e 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards a5d054decc 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards bee5e7050c 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 926713a5a1 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards d6c18e5d9b 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 8b3cd4c8ea 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards 0849a0f674 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards 68b3b93729 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 9d3974cd68 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards a78ebc4163 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards bd278e0985 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards eb16f302e8 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards c7a70d318d 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 5224c85fcc 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 6591cf2a95 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards 61bad9450f 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards eb439ea7e5 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards 4f37f98e3c 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards d01e3117a8 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 5b64ca2acf 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards f9b46c2368 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards 782c8310ac 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards fa1f23ee48 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 58d91fc5a0 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards 8c75577e03 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards a30b0bc787 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards 0775af1573 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards b6343f401c 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards 6138552efd 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 41ec7bcb4e 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards eec5c1965f 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards c86494d49f 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards 5e69e3addb 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards f799342cb9 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards e0e288f5fa 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards 59a1db9b2f 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 5ba5769fbd 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards 933752abfa 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards f382ee62f3 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 15b299fae4 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards f8536980cc 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] discards 5a2b2aa2dd 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 885b9318e7 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 89a9528f28 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] discards f0e531ada4 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards b68c4835d9 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] discards ba3c4d3030 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] discards 579063c8b8 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] discards 0b491ad90d 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] discards fa831c42ce 46: onsuccess: #53: 1: Success after binutils/gcc/linux/glib [...] discards 4094f99e70 45: onsuccess: #52: 1: Success after binutils/gcc/linux/glib [...] new 6daee34748 45: onsuccess: #52: 1: Success after binutils/gcc/linux/glib [...] new 56cd428553 46: onsuccess: #53: 1: Success after binutils/gcc/linux/glib [...] new f56f3fa0f6 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] new b2e705cd9f 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] new d2610becfc 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] new 2bffca1992 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new f3b7a9b221 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new f2d0e4d722 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] new 4deae28d1a 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 72889fc9df 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 9890860a84 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] new 6fc12dc9df 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new df252d6ca7 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 326a5238c8 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new 9051f18afe 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new 17d70bdb5b 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 28ffc31ab3 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new 5d8c4672a2 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new c3b2492529 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new 75711e78f6 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new b3907021d5 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new 2dba9b4116 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new f2e6fb7c28 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new bec28be01f 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new f83495d245 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new 6dc0d533d9 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new 59a98dadda 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 62646bd4c2 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new f0bb020363 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 248f6aaa8f 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new 308e951b0b 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new c47001cc60 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new f013629a61 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new d46baa3203 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 6fee3e2e74 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new 3f5f850e9a 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 9d4f687024 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new e171204908 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new d9cea55472 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 335158b711 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new b2265d8748 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 259aee929b 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new 01cda46a03 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new f3d7a961e8 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 1f5e040db1 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new 4cf6bf72f9 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new 38dcee597e 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 0a0bfcb098 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 7526a9516d 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new cb26eea8ad 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 7c90fc3740 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new 6f9b050cc4 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 2d7e01e8f0 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new 207e20b9c7 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 1959399e15 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new 3614223d35 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new 3a928f3983 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new b71b5b56fb 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new 1975cce6b3 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 1b0c5b244e 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 32e5887594 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 9110bce3bf 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new 72b068b541 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new ec46ac8ec3 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 5eca7577bc 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 95a999c0e7 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 478ba623a0 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 79621c4580 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 3acacc1557 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 0e6970d2e8 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 438c2d33f8 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new e400d36bac 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new 9900ddab88 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new 7cbf300371 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 8b55f8fa70 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 564eaf29eb 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new e800e20d65 121: force: #26: : Failure after baseline build: no new commits new 1c998af2e1 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 1ffeb80338 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 0bf8ab6a7b 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 4a60f8c2c4 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new ad6f5aee61 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 1d1fe5bae8 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 3a2bc5ab99 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 2ff05171a4 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 2dbb3e5a2d 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 68310b117e 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new e2595de8b3 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new f90b123fb9 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new a5c9b988b4 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new c9e2e95b33 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 574f8ae490 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new efd481504d 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new efe1ba7825 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 1d028b2321 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 8e228dda14 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 8dbb1382b8 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 4fe9df8562 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new facad1dc86 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new b58ed6c6b7 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new ff7d28cda6 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 5656bfd1d1 146: onsuccess: #54: 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 (a77d7c69f9) \ 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 2292 -> 2076 bytes 02-prepare_abe/console.log.xz | Bin 2564 -> 2520 bytes 03-build_abe-binutils/console.log.xz | Bin 49116 -> 48968 bytes 04-build_abe-gcc/console.log.xz | Bin 235872 -> 235132 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8852 -> 8624 bytes 07-build_abe-glibc/console.log.xz | Bin 232568 -> 232284 bytes 08-build_abe-gdb/console.log.xz | Bin 47028 -> 46540 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3804 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3024 -> 2824 bytes 11-check_regression/console.log.xz | Bin 1944 -> 1968 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 | 2 +- manifest.sh | 38 +++++++++---------- sumfiles/gdb.log.xz | Bin 14244 -> 14248 bytes sumfiles/gdb.sum | 4 +- 24 files changed, 67 insertions(+), 67 deletions(-)