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-aarch64 in repository toolchain/ci/base-artifacts.

discards 0fe6dd3048 158: onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards a0ee58aeb9 157: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 8bcd6953a0 156: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards e1796ce778 155: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 9055e6cddd 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards e6fc6a81f3 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards c3060702fa 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards b9e6374c37 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 51ccd18365 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 7ffb462593 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards c03615ad6e 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] discards 917aa596c3 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 043e9beb07 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 8f96538782 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 36a009052f 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards 2f4943f577 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards f1cca621f2 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards d41683eabe 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 42ec2aa1c9 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 5275088bcb 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 501fe83f52 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 7fb2245e38 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards f38ce83228 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 5bcd4f83f2 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards 7433b587e2 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards 18369a36b2 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 052a4c9e9b 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 3524dd5115 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards 6549ebf71c 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards e701647c23 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 8c76baeeaa 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 8a6cbf725e 127: force: #27: : Failure after baseline build: no new commits discards 50176d66c5 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 83a7d53d90 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 5bdd482691 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 76189145d1 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 8b0a1f803a 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 264cacc7c9 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 3a7a0333a7 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 4e184b2148 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards f9fa8741b3 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards d8a3217ceb 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 42311ba736 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards aa7080656f 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards c706f263db 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards dd98d195f8 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards 758f50fcfb 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 02d0be41dd 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 79502b6335 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards c5209ca14d 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 7791dd475f 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 32cc7e9e65 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 37eca44d3f 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards 3beff4d0fb 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 1f0790f264 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards bee82357f3 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards 116d3fe3eb 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards 90c9566351 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards fac2924b41 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards 530645e658 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards f53d08fc9f 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards 7774313e75 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards f5240d25fc 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards 6aaac95d75 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards 22ff052d58 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards ad373358f7 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 7f80c6410e 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards 8c1e4a2c07 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 5aed35bbe9 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards ef69b1e877 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards 8ec9b69f49 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards b292ccf68a 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 54332991dd 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards 78a7505de0 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards 44e5561b79 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 5d9320b638 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 30d725feb8 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards 7487770475 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards b76b9302ef 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards e7c265cd2b 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 6dc3a5b5cd 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards c87d268ce1 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards 8cd2cc95e9 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards 69a291db01 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards 30062a7df7 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 62232b6b96 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 51333b273c 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards b701d58ecb 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards ac446c530a 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards 7fe49319a9 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 2f16263374 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards fc9700f9e9 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards a8c5ce52e9 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards f4074bc760 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards 55d96c2a03 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards 1cabc9f329 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 9c658492ee 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards aa75cfa39c 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards dc382d9bef 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] discards bd280145cf 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] discards 4005d20e3a 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 60199d35d2 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new b2e351b040 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new c72e42dbe2 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new 6cc817de01 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new b257df70ee 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new 0b1a4cd3ca 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 0eb5ef42d6 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new 15d8ebd4ab 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new bd019d1659 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new d6fba00d38 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 1a13fb8fa5 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new b66f6c537c 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 765eebcfc0 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new f5146ccbeb 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new b3a9b34ccf 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new eb24085588 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new bbfc64e40a 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 02c5c63148 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new 38ae54d97e 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new eb3e29187b 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new 33fb9ddb79 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new feaf9524fd 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new e30ee9afad 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new e22ccd048f 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 50cf2b7df0 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new 8a0c0bf0e8 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 2995524d65 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new fb679f383e 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new 2427b2ae66 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new 9993c7a7b5 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 128c76efe2 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 33ba4f2be2 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new 41dc7a653c 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new b93b31ae31 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new e54354fdb5 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new ffd2b7706a 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 3dfe5d5082 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 3d625a73cd 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new 7196247442 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new ae309158a1 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new 918c73b64e 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new 7e958b436d 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new 26c6bbd5c3 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new 578ba6dfdf 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new 69bdfd231b 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new 7b3fb2707b 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new 7686430884 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new d653cf35b8 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 9867bb56f8 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new 9b15850961 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new da0186b99f 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new ef5ea102c7 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 135fed6ef7 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 6774ed8a98 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new d6eacbef70 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new bde0b2dd4f 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new b82f2e7c0c 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new a262b7733d 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 15f70dc6c0 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new b95078894c 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 31d383a258 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new bb1f3b190d 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new aed5056461 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 664f86eb7a 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 21603be7ba 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 2b73982b34 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 429ad6b1cc 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new f64715787f 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new eda025c26a 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new b9907fce73 127: force: #27: : Failure after baseline build: no new commits new fc6ff139b0 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 5d525a2ae0 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 5e11496177 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 3c6038ced2 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new ad0fde7068 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 165eed8d99 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 6930b6a616 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new f80cde72b8 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new 3be78fd6c8 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new af3ba8a336 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new cac0dc87be 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 6dacee8155 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 2e90a66d1d 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new d176cd384c 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 5f6a2bff8d 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 559e5a8055 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new a72d1c1c94 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new 083943b2da 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 28085706bf 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 82622db527 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 5eea02e48b 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] new 3ce94a3232 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 5c00bbb8cd 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 82ea13a5e3 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 36cc516bdf 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 59ea0ba2a2 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 150a7a7ab8 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 1a88d6157b 155: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 435a60b6be 156: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 0ea1a1debc 157: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 3dd7868868 158: onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 50287b4583 159: onsuccess: #72: 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 (0fe6dd3048) \ 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 -> 14452 bytes 01-reset_artifacts/console.log.xz | Bin 2152 -> 2124 bytes 02-prepare_abe/console.log.xz | Bin 2460 -> 2456 bytes 03-build_abe-binutils/console.log.xz | Bin 35352 -> 36484 bytes 04-build_abe-gcc/console.log.xz | Bin 204884 -> 204112 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8728 -> 8460 bytes 07-build_abe-glibc/console.log.xz | Bin 244900 -> 242248 bytes 08-build_abe-gdb/console.log.xz | Bin 36284 -> 35532 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3856 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3412 -> 3492 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 1196 -> 1196 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/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 6 ++--- manifest.sh | 32 ++++++++++++----------- sumfiles/gdb.log.xz | Bin 14440 -> 0 bytes sumfiles/gdb.sum | 4 +-- 26 files changed, 59 insertions(+), 55 deletions(-) create mode 100644 00-sumfiles/gdb.log.xz delete mode 100644 sumfiles/gdb.log.xz