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 7326ace72f 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 1a1c421b5b 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 3c7306f19f 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards b518243744 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards bdaa54a143 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 29afc06b6d 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 7891c21191 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 9cdeceec91 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 9a81b7f0dd 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 5c44a8df8d 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 129afbc8f2 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 0af88351f9 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 44afb35873 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards f734317d79 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 4aabad7dde 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 4c24626e97 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 94ca9d62d8 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards b0770bc086 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 62eabe570e 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 99c39b426e 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards f6626ba65e 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 9dfa10a97b 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards c416ef3435 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards f12c5ee091 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 5e1bc39931 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 7b38f11850 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards e735eadc3a 121: force: #26: : Failure after baseline build: no new commits discards 07c2e119ee 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 9d3672dd7b 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 4ec7769ea2 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards fd930fcace 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 37f01e4d27 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards 06afb125fc 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards eb8cc0e082 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 60486faa6b 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 6bd9468223 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards db161956d8 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 06becad341 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards d20fb265cc 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 2c9a67cd44 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 16eca5e3d0 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 14466a4164 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards 3840f550de 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards a7bfd977c2 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 7c5e441c54 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 1b68d2816e 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards 3740daab08 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards 06740d59fa 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards 45d9b64056 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards 9a0fa3c88d 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 25e5b64c97 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards f4a2cae749 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 39379fccbd 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards 31426fd3bb 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards adfd0fb7c9 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 108635b642 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 4d63d34c86 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 9ec98b6c92 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards d1d88f85ce 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards b0b15ae421 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards b6a2b9f85e 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards 7ee006b23c 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards c96df35ccc 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards fe0fb25ac7 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 3e83684bbe 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 1d9941c9a6 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 6fe0382f9c 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards 22e1df8448 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 25b13466d5 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards 89e10a43d4 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 7639812d3a 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 91eb622228 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards 68f79bff51 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards a8bd5bbbe0 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards 95c8b1f6d2 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 2ef8c16a88 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards 241f2c099e 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards b44ca77517 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards 84c83dacef 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards b7e415eb5b 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards 22c1b65c77 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards b27b329fb7 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards c4e75b4a1a 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards 01e6d927de 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards e5996e5dd4 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards 00d536746c 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards bfb4671ba7 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards 88892b29d8 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 85bf2f9507 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards 8f1dc9f42a 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards 7d4f5db57d 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards e04e235840 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards f21911af03 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] discards 2af47bd754 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 0b888a9d86 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 5e47d51545 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] discards cea6ef5072 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 76e1246cbf 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] discards e63f159323 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] discards c9647f38c9 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] discards ea0ea29574 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] new c3ef01d6d5 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] new aa504298b2 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] new 54e2d4146a 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] new 57fbf5bafa 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new 2a1840fd3d 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 36edecdbad 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] new bf8dbf6f4b 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new e1e752a60e 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 4b63999019 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] new 7130508ea8 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new 4c851a3827 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 481776cda8 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new b38c800165 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new 5a6d32db2d 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 77e282af71 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new 4591a06159 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new 67be916438 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new aa932a7a27 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new 0d7485ee22 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new 6f2f337523 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 720655dca3 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 864f624ede 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new 755203d3dd 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new d801f725b5 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new 14bdfb27e0 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 9545ec1267 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new 224aee6d42 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new c46a97e3d6 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new a73083b409 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new c65178ca50 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new 156cf7b9c6 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new e8bb33516a 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new df631f614f 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new e3530e3cd6 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 9c8306c548 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new 266e729616 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new fadaad3aff 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 8016a56d96 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 657f9ba901 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 3bb8a8331e 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new 627af9d938 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new 5f7d706382 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new d5c6d22bf0 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new f7816accdf 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new 37a09eafcc 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 6a0aa2c461 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 8edeaaf657 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new e41dc72af6 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 47bdf0689f 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new 03ed9dca53 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new b9fb24e405 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new 577943f398 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 89e59ffa0d 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new f9fe0d5294 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new 303155e4d6 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new 849f4d17f1 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new 8239461b84 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 036e1063ad 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 83956a2fbb 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new e0adc6af49 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new 9c1b499947 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 4ea32d2ab8 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 7b7e59fa93 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new d4e84851c2 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 5253273548 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new eaa9f40f68 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 4bd52a7cb2 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 05bd9da5d4 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 4aeba680fc 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new e0b80a5830 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new e1f33306c0 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new ecbe0688f1 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new c6b99b9770 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new f0956e00ed 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new ca0b97d7a8 121: force: #26: : Failure after baseline build: no new commits new e148ff06fd 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 1eab5b6b1f 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 5789db3903 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new b80220651f 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 676aefd6bd 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 98cf8a9388 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 62673c2993 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new a1826ab482 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new abc47a4f4c 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 6ebb5f77a4 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new e84fd923eb 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new ec23c15ef9 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new bac9082067 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 7373bcf8b5 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new b062b1ee7e 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new bba9dda8a3 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new e302111a7b 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new edf95a75fe 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new d186d909c4 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 410bcd1e07 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 24ff16fcc9 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 6815bf3f97 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 4e808148cf 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new d19731ea20 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 974f3981b2 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 60075e116b 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new e69a3f9120 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...]

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 (7326ace72f) \ 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 2068 -> 2184 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 49032 -> 49120 bytes 04-build_abe-gcc/console.log.xz | Bin 238104 -> 236096 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8636 -> 8780 bytes 07-build_abe-glibc/console.log.xz | Bin 234168 -> 232752 bytes 08-build_abe-gdb/console.log.xz | Bin 46968 -> 46472 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3852 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2928 -> 1716 bytes 10-build_abe-check_gdb/flaky.xfail | 1 + 11-check_regression/console.log.xz | Bin 1288 -> 952 bytes 11-check_regression/results.compare | 7 - 11-check_regression/results.compare2 | 42 ---- 11-check_regression/results.regressions | 3 + 12-update_baseline/console.log | 47 ++--- jenkins/notify.sh | 2 +- mail/check-regression-status.txt | 2 +- mail/results.compare | 7 - manifest.sh | 23 +-- results | 5 +- sumfiles/gdb.log.xz | Bin 14256 -> 0 bytes sumfiles/gdb.sum | 353 -------------------------------- 23 files changed, 43 insertions(+), 449 deletions(-) create mode 100644 10-build_abe-check_gdb/flaky.xfail delete mode 100644 11-check_regression/results.compare delete mode 100644 11-check_regression/results.compare2 create mode 100644 11-check_regression/results.regressions delete mode 100644 mail/results.compare delete mode 100644 sumfiles/gdb.log.xz delete mode 100644 sumfiles/gdb.sum