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 5f6e845e0a 152: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 7fe7bd0f29 151: onsuccess: #66: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 778216b04e 150: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards ed587d1235 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 77c6af12b3 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards d5edcc19ff 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 43e366db7b 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 703735ef8f 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 618d9faab4 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards bcffa0b6d5 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 579fb4df8a 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards afce4166f6 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 3186da9993 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 1078d9c839 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 4c17fad510 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 104407fbb1 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 8f1c162df4 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards dc38d74aa9 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards bf5a785fb6 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 681a6f6734 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards ca64634a0e 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 57862af647 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards c1e2e832db 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 5d5e90baf3 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 53a990eabe 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 96663104ea 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards e008777d6b 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 053382837b 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards cd1245b365 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards eddb521e01 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 5f40ad0a97 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards df509aa48b 121: force: #26: : Failure after baseline build: no new commits discards 96c2b36ec3 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 12e9bba4e7 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 768cc14f48 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards ec3f53ae7b 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 4b67c9bae1 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards 6c6c89d87d 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 57d65983da 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 528aec8085 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 12aea23d8e 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 8393e368a3 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 5cb98a5362 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 6e4cdc3cb2 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards b73e3a342b 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 447ac86c46 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 5cfe658005 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards fdf94106c4 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards e9b794f41f 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards b784d2e6ec 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards b7df53fbe1 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards 042f8b9c1a 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards 51aed87cf3 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards b697b015c3 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards dea4206363 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 61460d4ab8 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards 1765766364 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 16af8f6cc2 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards c7d222a0bf 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 5a526f1633 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards a9ab99815e 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 8e8ab780c6 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 8b65826437 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards 7d15a50119 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards 64c0656176 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards a1f7ad05b1 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards d1bd9f0a57 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards c83c0e59c3 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 5822934a27 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards c618bca985 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards c6240ad85d 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards e396ac67fb 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards 58fb98d871 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards d90d07bb01 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards e47c868621 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards e14db4397a 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards f1ab331e13 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards a9e9ccde09 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards f469e51b43 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards f490ccd566 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards c7bc104faf 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards ddc17664fe 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 185fe47a16 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards 10279e7320 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards 2b802ec7f0 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards 7bfb2153ea 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards ae3dffd321 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 8707de5836 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards ee433910f9 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards 7d1a67dec8 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards 831bccde04 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards 994065f2a4 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards 9cb19b107c 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 35950d4142 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards 6c2bf1cf1a 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards 685ee4f9fc 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 56a0df4b06 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards 7bc48d4eea 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] discards 690dc1d1fe 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 2d9235a547 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 59d633c704 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] new 826e836d0c 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] new 8580b10bc5 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 63d17961ae 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 7e359959e0 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] new 37b89068cb 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new ed68355a1f 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new fbd4652712 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new e52d554d85 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new 34f228d8f8 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 4bdd3f3a09 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new 63a1585178 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new 07333d3c22 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new 003c0d1e81 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new f1d3a6552a 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new d2b17578d8 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 6d18133044 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new df8ec0f771 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new 952b33d360 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new ee04102bab 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new 0d50ad7676 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 54106af6ac 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new 3be3e7d112 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 9b75d9996f 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new 1e1116dd0e 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new f627aef781 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new b297b654c8 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 0690fff4a8 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new ec444933e7 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new 47c0a77c39 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 7fdabd7f63 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new 5af57acbd8 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new ea00484944 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new d1f197b59c 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new dbb5f3d636 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 15c193203e 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new 6bd2f9de9b 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new 5beeefe063 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new cfd58bf042 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new 27dcc1c534 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new c13fc59ee7 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 9443d15ca5 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 88713b18a5 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 3120155a2a 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new c42f05b79e 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new a71f9b5882 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 011a1771f6 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new d0e11bef0c 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 9cd8bf61ee 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new ea8caa1d2d 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new 890b2c1e05 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new 46433ae71b 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new b139642462 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 29cca801b8 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 95a2f8ee9b 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 9cd6071d4c 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new 7b34825f52 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 5daaa92038 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 15fd01bad7 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new edb6742727 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 551f66df6e 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 1c8db59b8f 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 5d1fddd510 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 0dc0d09187 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 2c4753b1d8 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new cf8e112254 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new d6fa8358ef 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new 5418e99e4a 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 1139c6a39a 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 2ec3effc4d 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new d87a4989ca 121: force: #26: : Failure after baseline build: no new commits new cee04d2eee 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new c5a7bdcc51 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 28135cd9f0 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new dcf6db1d61 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 631aa64c1e 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 487f398e40 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new d22e642f5b 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new dd04064e74 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 6956e6cb18 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new fb4af3ae76 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new ba4f456a15 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 37dc7827e6 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 5d27a552c9 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 35116c0e0c 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new bb7535bec2 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 9dc4be2aae 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 8aaca622e7 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 18ff157e30 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new d6868ec0ae 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 8b2ab08005 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 6d3680311a 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 5696c696d0 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 8572f960d1 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 59fa475c8e 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 24602b27ca 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 2b7773cd8d 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 3b6dd29358 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 1ef934c512 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 9c5b3443d4 150: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new ad34f7f9ad 151: onsuccess: #66: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 296af22870 152: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new db01648a15 153: onsuccess: #68: 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 (5f6e845e0a) \ 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 2248 -> 2192 bytes 02-prepare_abe/console.log.xz | Bin 2524 -> 2456 bytes 03-build_abe-binutils/console.log.xz | Bin 48992 -> 49756 bytes 04-build_abe-gcc/console.log.xz | Bin 235144 -> 236556 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8536 -> 8524 bytes 07-build_abe-glibc/console.log.xz | Bin 232596 -> 234812 bytes 08-build_abe-gdb/console.log.xz | Bin 47244 -> 47532 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3868 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3216 -> 3340 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 1276 -> 1208 bytes 11-check_regression/results.compare | 8 +++---- 11-check_regression/results.compare2 | 6 +++--- 12-update_baseline/console.log | 38 +++++++++++++++++----------------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 8 +++---- manifest.sh | 30 +++++++++++++-------------- results | 2 +- sumfiles/gdb.log.xz | Bin 14232 -> 14236 bytes sumfiles/gdb.sum | 4 ++-- sumfiles/xfails.xfail | 2 ++ 26 files changed, 54 insertions(+), 56 deletions(-)