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 5656bfd1d1 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards ff7d28cda6 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards b58ed6c6b7 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards facad1dc86 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 4fe9df8562 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 8dbb1382b8 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 8e228dda14 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 1d028b2321 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards efe1ba7825 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards efd481504d 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 574f8ae490 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards c9e2e95b33 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards a5c9b988b4 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards f90b123fb9 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards e2595de8b3 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 68310b117e 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 2dbb3e5a2d 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 2ff05171a4 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 3a2bc5ab99 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 1d1fe5bae8 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards ad6f5aee61 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 4a60f8c2c4 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 0bf8ab6a7b 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 1ffeb80338 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 1c998af2e1 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards e800e20d65 121: force: #26: : Failure after baseline build: no new commits discards 564eaf29eb 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 8b55f8fa70 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 7cbf300371 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 9900ddab88 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards e400d36bac 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards 438c2d33f8 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 0e6970d2e8 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 3acacc1557 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 79621c4580 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 478ba623a0 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 95a999c0e7 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 5eca7577bc 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards ec46ac8ec3 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 72b068b541 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 9110bce3bf 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards 32e5887594 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 1b0c5b244e 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 1975cce6b3 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards b71b5b56fb 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards 3a928f3983 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards 3614223d35 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards 1959399e15 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards 207e20b9c7 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 2d7e01e8f0 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards 6f9b050cc4 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 7c90fc3740 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards cb26eea8ad 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 7526a9516d 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 0a0bfcb098 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 38dcee597e 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 4cf6bf72f9 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards 1f5e040db1 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards f3d7a961e8 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 01cda46a03 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards 259aee929b 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards b2265d8748 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 335158b711 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards d9cea55472 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards e171204908 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 9d4f687024 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards 3f5f850e9a 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 6fee3e2e74 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards d46baa3203 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards f013629a61 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards c47001cc60 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards 308e951b0b 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards 248f6aaa8f 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards f0bb020363 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 62646bd4c2 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards 59a98dadda 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 6dc0d533d9 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards f83495d245 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards bec28be01f 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards f2e6fb7c28 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 2dba9b4116 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards b3907021d5 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards 75711e78f6 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards c3b2492529 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards 5d8c4672a2 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards 28ffc31ab3 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards 17d70bdb5b 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 9051f18afe 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards 326a5238c8 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards df252d6ca7 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 6fc12dc9df 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards 9890860a84 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] discards 72889fc9df 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 4deae28d1a 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards f2d0e4d722 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] discards f3b7a9b221 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 2bffca1992 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] discards d2610becfc 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] discards b2e705cd9f 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] discards f56f3fa0f6 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] discards 56cd428553 46: onsuccess: #53: 1: Success after binutils/gcc/linux/glib [...] new 6d055c0433 46: onsuccess: #53: 1: Success after binutils/gcc/linux/glib [...] new ea0ea29574 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] new c9647f38c9 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] new e63f159323 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] new 76e1246cbf 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new cea6ef5072 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 5e47d51545 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] new 0b888a9d86 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 2af47bd754 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new f21911af03 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] new e04e235840 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new 7d4f5db57d 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 8f1dc9f42a 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new 85bf2f9507 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new 88892b29d8 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new bfb4671ba7 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new 00d536746c 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new e5996e5dd4 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new 01e6d927de 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new c4e75b4a1a 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new b27b329fb7 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 22c1b65c77 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new b7e415eb5b 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new 84c83dacef 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new b44ca77517 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new 241f2c099e 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 2ef8c16a88 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new 95c8b1f6d2 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new a8bd5bbbe0 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new 68f79bff51 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new 91eb622228 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new 7639812d3a 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 89e10a43d4 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 25b13466d5 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new 22e1df8448 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 6fe0382f9c 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new 1d9941c9a6 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 3e83684bbe 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new fe0fb25ac7 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new c96df35ccc 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 7ee006b23c 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new b6a2b9f85e 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new b0b15ae421 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new d1d88f85ce 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new 9ec98b6c92 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new 4d63d34c86 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 108635b642 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new adfd0fb7c9 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 31426fd3bb 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 39379fccbd 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new f4a2cae749 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 25e5b64c97 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new 9a0fa3c88d 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 45d9b64056 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new 06740d59fa 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new 3740daab08 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new 1b68d2816e 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new 7c5e441c54 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new a7bfd977c2 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 3840f550de 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 14466a4164 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new 16eca5e3d0 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 2c9a67cd44 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new d20fb265cc 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 06becad341 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new db161956d8 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 6bd9468223 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 60486faa6b 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new eb8cc0e082 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 06afb125fc 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 37f01e4d27 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new fd930fcace 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new 4ec7769ea2 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 9d3672dd7b 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 07c2e119ee 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new e735eadc3a 121: force: #26: : Failure after baseline build: no new commits new 7b38f11850 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 5e1bc39931 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new f12c5ee091 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new c416ef3435 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 9dfa10a97b 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new f6626ba65e 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 99c39b426e 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 62eabe570e 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new b0770bc086 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 94ca9d62d8 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 4c24626e97 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 4aabad7dde 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new f734317d79 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 44afb35873 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 0af88351f9 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 129afbc8f2 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 5c44a8df8d 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 9a81b7f0dd 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 9cdeceec91 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 7891c21191 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 29afc06b6d 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new bdaa54a143 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new b518243744 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 3c7306f19f 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 1a1c421b5b 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 7326ace72f 147: onsuccess: #55: 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 (5656bfd1d1) \ 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 2076 -> 2068 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 48968 -> 49032 bytes 04-build_abe-gcc/console.log.xz | Bin 235132 -> 238104 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8624 -> 8636 bytes 07-build_abe-glibc/console.log.xz | Bin 232284 -> 234168 bytes 08-build_abe-gdb/console.log.xz | Bin 46540 -> 46968 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3816 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2824 -> 2928 bytes 11-check_regression/console.log.xz | Bin 1968 -> 1288 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 6 +-- 12-update_baseline/console.log | 42 ++++++++++----------- dashboard/dashboard-generate.sh | 17 --------- dashboard/dashboard-push.sh | 7 ---- .../squad-vs-first/score/results-functional.json | 1 - git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/dashboard-push.sh | 7 ---- jenkins/notify.sh | 2 +- {11-check_regression => mail}/results.compare | 4 +- manifest.sh | 36 +++++++++--------- sumfiles/gdb.log.xz | Bin 14248 -> 14256 bytes sumfiles/gdb.sum | 4 +- 28 files changed, 53 insertions(+), 87 deletions(-) delete mode 100755 dashboard/dashboard-generate.sh delete mode 100755 dashboard/dashboard-push.sh delete mode 100644 dashboard/squad-vs-first/score/results-functional.json delete mode 100755 jenkins/dashboard-push.sh copy {11-check_regression => mail}/results.compare (72%)