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 e69a3f9120 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 60075e116b 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 974f3981b2 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards d19731ea20 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 4e808148cf 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 6815bf3f97 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 24ff16fcc9 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 410bcd1e07 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards d186d909c4 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards edf95a75fe 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards e302111a7b 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards bba9dda8a3 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards b062b1ee7e 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 7373bcf8b5 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards bac9082067 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards ec23c15ef9 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards e84fd923eb 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 6ebb5f77a4 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards abc47a4f4c 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards a1826ab482 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 62673c2993 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 98cf8a9388 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 676aefd6bd 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards b80220651f 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 5789db3903 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 1eab5b6b1f 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards e148ff06fd 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards ca0b97d7a8 121: force: #26: : Failure after baseline build: no new commits discards f0956e00ed 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards c6b99b9770 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards ecbe0688f1 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards e1f33306c0 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards e0b80a5830 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards 4aeba680fc 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 05bd9da5d4 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 4bd52a7cb2 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards eaa9f40f68 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 5253273548 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards d4e84851c2 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 7b7e59fa93 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 4ea32d2ab8 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 9c1b499947 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards e0adc6af49 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards 83956a2fbb 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 036e1063ad 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 8239461b84 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 849f4d17f1 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards 303155e4d6 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards f9fe0d5294 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards 89e59ffa0d 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards 577943f398 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards b9fb24e405 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards 03ed9dca53 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 47bdf0689f 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards e41dc72af6 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 8edeaaf657 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 6a0aa2c461 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 37a09eafcc 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards f7816accdf 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards d5c6d22bf0 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards 5f7d706382 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 627af9d938 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards 3bb8a8331e 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards 657f9ba901 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 8016a56d96 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards fadaad3aff 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 266e729616 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 9c8306c548 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards e3530e3cd6 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards df631f614f 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards e8bb33516a 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 156cf7b9c6 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards c65178ca50 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards a73083b409 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards c46a97e3d6 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards 224aee6d42 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 9545ec1267 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards 14bdfb27e0 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards d801f725b5 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards 755203d3dd 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards 864f624ede 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards 720655dca3 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 6f2f337523 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 0d7485ee22 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards aa932a7a27 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards 67be916438 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards 4591a06159 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards 77e282af71 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards 5a6d32db2d 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards b38c800165 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards 481776cda8 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards 4c851a3827 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 7130508ea8 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards 4b63999019 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] discards e1e752a60e 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards bf8dbf6f4b 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 36edecdbad 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] discards 2a1840fd3d 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 57fbf5bafa 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] discards 54e2d4146a 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] discards aa504298b2 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] new 381e637925 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] new 5d58d486e2 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] new f2459dac70 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new 0703e917de 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new cd64e16b1c 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] new 7d3740c423 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new f59e30feb3 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new b0a0c05f88 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] new 4efa8d8fa9 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new 92b5413c97 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new ed8befa0e3 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new fdb6bb24b6 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new f3485443fd 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new d3ea1a178b 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new 6d204b2293 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new 4a1c349c4b 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new d7f389cd37 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new 499047c6f3 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new 19838bd0b8 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 87ce0440a2 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 1d452f3b8f 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new a6a262c6ea 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new 9a8c820a2f 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new 809f4963ab 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new ace03d4852 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new 824c755fdf 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 02222be65a 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new e7f992b8c4 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new 72bad4bdbb 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new 5b648269e8 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 5786afe31e 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 97796e8467 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new cee95b6ac8 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new fde6dbceb6 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new e99185d8e8 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new bf7620235b 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 2b2d9e060a 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 2f7faceaa4 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new d8e537ca0c 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new 5c577bc280 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new 3aff44e533 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new ef3fb09a93 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new cc865117e2 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new 819018574c 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new c3a80e8bd8 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 5b46e4ad35 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new f64f7bccad 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 8a83333cf6 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new 834b032a47 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 36304bfaa3 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new bb9b043fd4 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 026c5be3fd 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new a54c027a07 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new eb773746f3 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new ab5a0d26ee 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new c8a43ef794 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 76c76bd13e 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new e10c3cbeba 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 3d7c198af0 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new e7187dddef 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 006fb12e43 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 3d344dd591 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new e380614f48 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new dcd3711583 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 44cb7a7f77 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new e21aba53c4 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new fa8d3784a0 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new f3939d02df 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 1ae627faa8 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new 3f24e4b972 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new e61f5083b5 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 0031291d5c 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 678a41d4db 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 2e31180ba3 121: force: #26: : Failure after baseline build: no new commits new 2f10917a37 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new db53b20366 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new fc225ecb75 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 18305fec86 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 140b0599a9 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new cedd028571 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 6ae100c8b7 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new c254c283ac 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 6e4cf44c5f 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 2f582b4f2a 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new a53da6fb64 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 29ee848a0a 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 5b13844f12 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new b6fbd43e8a 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new b966152f47 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new ea501ee338 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 21d7e33ef1 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 1067196613 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new b0a21a5722 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 07a008e65e 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 219ef219cb 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 15e57ecb97 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new d145ae7061 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new ef768646e5 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 4d8926a700 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 298d809f7c 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 887c4fc246 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 503a77a6ac 149: onsuccess: #64: 0: [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 (e69a3f9120) \ 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 2184 -> 2200 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2524 bytes 03-build_abe-binutils/console.log.xz | Bin 49120 -> 49220 bytes 04-build_abe-gcc/console.log.xz | Bin 236096 -> 236160 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8780 -> 8452 bytes 07-build_abe-glibc/console.log.xz | Bin 232752 -> 233052 bytes 08-build_abe-gdb/console.log.xz | Bin 46472 -> 46416 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3804 bytes 10-build_abe-check_gdb/console.log.xz | Bin 1716 -> 1732 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 952 -> 548 bytes 11-check_regression/results.regressions | 3 -- 12-update_baseline/console.log | 66 ++++++++++++++++---------------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- mail/check-regression-status.txt | 2 +- manifest.sh | 31 ++++++++------- results | 3 -- 23 files changed, 59 insertions(+), 60 deletions(-) delete mode 100644 11-check_regression/results.regressions