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 db01648a15 153: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 296af22870 152: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards ad34f7f9ad 151: onsuccess: #66: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 9c5b3443d4 150: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 1ef934c512 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 3b6dd29358 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 2b7773cd8d 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 24602b27ca 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 59fa475c8e 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 8572f960d1 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 5696c696d0 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 6d3680311a 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 8b2ab08005 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards d6868ec0ae 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 18ff157e30 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 8aaca622e7 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 9dc4be2aae 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards bb7535bec2 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 35116c0e0c 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 5d27a552c9 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 37dc7827e6 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards ba4f456a15 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards fb4af3ae76 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 6956e6cb18 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards dd04064e74 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards d22e642f5b 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 487f398e40 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 631aa64c1e 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards dcf6db1d61 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 28135cd9f0 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards c5a7bdcc51 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards cee04d2eee 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards d87a4989ca 121: force: #26: : Failure after baseline build: no new commits discards 2ec3effc4d 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 1139c6a39a 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 5418e99e4a 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards d6fa8358ef 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards cf8e112254 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards 2c4753b1d8 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 0dc0d09187 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 5d1fddd510 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 1c8db59b8f 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 551f66df6e 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards edb6742727 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 15fd01bad7 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 5daaa92038 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 7b34825f52 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 9cd6071d4c 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards 95a2f8ee9b 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 29cca801b8 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards b139642462 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 46433ae71b 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards 890b2c1e05 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards ea8caa1d2d 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards 9cd8bf61ee 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards d0e11bef0c 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 011a1771f6 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards a71f9b5882 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards c42f05b79e 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards 3120155a2a 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 88713b18a5 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 9443d15ca5 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards c13fc59ee7 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 27dcc1c534 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards cfd58bf042 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards 5beeefe063 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 6bd2f9de9b 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards 15c193203e 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards dbb5f3d636 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards d1f197b59c 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards ea00484944 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 5af57acbd8 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 7fdabd7f63 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards 47c0a77c39 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards ec444933e7 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards 0690fff4a8 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards b297b654c8 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards f627aef781 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards 1e1116dd0e 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards 9b75d9996f 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards 3be3e7d112 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 54106af6ac 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards 0d50ad7676 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards ee04102bab 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards 952b33d360 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards df8ec0f771 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards 6d18133044 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards d2b17578d8 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards f1d3a6552a 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards 003c0d1e81 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards 07333d3c22 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards 63a1585178 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards 4bdd3f3a09 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards 34f228d8f8 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards e52d554d85 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards fbd4652712 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards ed68355a1f 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 37b89068cb 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards 7e359959e0 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] discards 63d17961ae 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 8580b10bc5 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 55df816fcc 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 3202d00c59 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 9b2923bfc7 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] new 7d82d65238 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new 55f683ea4e 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 077c94b55b 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new 09481e244e 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new eada94c503 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 83efcd998f 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new b599c0faa5 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new fa9620e935 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new 8b234851e5 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new 81e6f11011 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new 76d0c23c1a 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new d86e81cea3 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 5ca4d95707 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new feac82f1f5 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new 4e1dd2b169 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new 3a63afab0b 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 273b239022 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new 040225c47a 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new e0e3dcdb67 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new d0dff05055 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new c2f719c88a 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new 70328c394d 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new bda30e0422 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 73a8b85b7b 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new aa7f66faad 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new ada4d1cd4d 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new 05742c7a27 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new dc447ff092 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 721d141c36 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new cdde0aa8ff 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 0f23ae3671 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new 3337795137 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new 9341616517 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 71625f1751 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new 4265d09bff 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new a73a097119 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 4fd091e62d 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new add97fb910 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 3b79f4539f 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 077e2cd842 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new 3776e55dff 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 5d6e9d9b63 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new 50a52f6586 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new e33aefbb1a 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new 529a826c21 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new 03a965d2e4 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new ca2bf3e2b3 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new db41ab3d1e 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new e44ac7dcfd 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new d6dffb2549 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 3c1558333d 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new 05840707c6 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new af6674ad9d 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new af90d417d4 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 22ad411d8b 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new a80eb89e11 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 2cfbde1406 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 651ccaf77f 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 15a923f638 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 0dddd8e83c 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 6dd5c6f161 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new f59a47a065 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new aabe538788 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 43390f3ec7 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new d5fa210c26 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 0f641f0527 121: force: #26: : Failure after baseline build: no new commits new b74b83741e 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 9c68ff25b7 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new bd7e192956 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new caac5497f0 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new b09b82aa07 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new b259fc44b8 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 178c73be83 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new f769326989 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 0c72b2793a 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 68dcc750bf 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 05262e4398 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new a67cd6d2bf 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 6bd21b398a 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new be7a54d1db 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 750c6680fe 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 805aca0355 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new ac82d7b366 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new ff37c527ed 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new a5770a6cce 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 3f9a29edfc 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 7ffadc655f 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new cf1c91c979 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 664f6e62a7 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new dd0618d127 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new eed8f13f1a 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d0f4687ea9 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new e61d4611fd 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 82124949d6 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 68657b8966 150: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new b6a2b2b135 151: onsuccess: #66: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 954efe8735 152: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 1aa74782ab 153: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 2275abb080 154: onsuccess: #69: 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 (db01648a15) \ 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: 00-sumfiles/gdb.log.xz | Bin 0 -> 14236 bytes 01-reset_artifacts/console.log.xz | Bin 2192 -> 2224 bytes 02-prepare_abe/console.log.xz | Bin 2456 -> 2488 bytes 03-build_abe-binutils/console.log.xz | Bin 49756 -> 50916 bytes 04-build_abe-gcc/console.log.xz | Bin 236556 -> 240312 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8524 -> 8584 bytes 07-build_abe-glibc/console.log.xz | Bin 234812 -> 235636 bytes 08-build_abe-gdb/console.log.xz | Bin 47532 -> 47456 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3884 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3340 -> 3492 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 1208 -> 1208 bytes 11-check_regression/results.compare | 6 ++--- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 46 +++++++++++++++++----------------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 6 ++--- manifest.sh | 30 +++++++++++----------- sumfiles/gdb.log.xz | Bin 14236 -> 0 bytes sumfiles/gdb.sum | 4 +-- 25 files changed, 55 insertions(+), 55 deletions(-) create mode 100644 00-sumfiles/gdb.log.xz delete mode 100644 sumfiles/gdb.log.xz