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 f3a2e15cc7 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 6dd1095ff0 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards fffaaa5a3a 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 25d7e54d70 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 9ba2d70cc9 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] discards 0f49e42e49 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 1609d97421 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 64145a219e 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 96efb31b4b 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards c5a2be66e6 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards e05805079d 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 4bbaa6f46b 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 2770babb54 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 1b37426bef 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 8884b8f0a8 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards e887d93da7 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards de0dd46890 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards b3ca8213e6 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards ec34beb007 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards 377e412662 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards b9491c6d81 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 3cbddf3bcc 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards da98074517 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 58dece10a8 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards e8fb03efe3 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 41220801bb 127: force: #27: : Failure after baseline build: no new commits discards 3b65c035f8 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 4d11c33e9c 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 83a7ac9df0 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards e4daa87cc2 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 6678eba97a 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 65f9febc9e 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards bd2a8a42c8 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 2a1f189950 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards a20a084d7b 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 6186c448c6 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 795f8aa6a0 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 12da9ebc85 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 84d6ae813a 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 977caee364 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards 93843b299d 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 25e05ecad7 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards e29b8c9945 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 3cb09759cd 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards a7e4e13d06 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 9b96fefa6c 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 37278212f9 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards 5ef44d3199 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards ffa612c76c 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards 19c4464f6b 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards e4613910c7 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards 00499e0287 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards 77cd2eac69 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards db7d0a33a1 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards 943adb25e6 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards 8f0b6f79f6 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards 7d71480fb9 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards 5e386bd43d 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards b70e03bcf7 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 38260c7a48 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards c952f372f8 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards 5258494489 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 8e56bdeafa 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 1ce4f7ef52 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards 7db42def6c 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards c8632cee64 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards fd6b7fdc0e 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards 0680277b9a 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards 0da9a5e912 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards e9d7f59ac3 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 77413e3ae0 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards b601b538a0 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 3edbc17614 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards e0297bdf88 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 200c8fc656 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 5207283ea7 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards 980b39cbd6 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards 9217092db9 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards 66ef1f0bea 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 798fa28995 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 180301c2ef 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards 58a082d71c 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards a8900d3e4b 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards ca1a95c9cf 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 5e8d2bde7c 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards 6463ab4f89 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 86fb70ffd4 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards ed838401ae 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards 211a267e17 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards 2ad5b1bb3f 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 5ffca84784 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards 22169caacd 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards 2153d5474e 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] discards 8cec969c53 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] discards 72314a6cf7 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 87813addbd 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 941d3c7795 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards fe4284ccdb 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] discards f02fd9cd61 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards 2a10892ef1 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 1b39dbfaa1 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new 19a9871224 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new c09bdda135 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new c519e4a04b 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 46037725c1 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] new 71bcda1a28 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 93bd356522 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 5bb318f87f 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 37c73f3cba 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new 603acd8c0c 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new 57fbd8dce7 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new d78f273fec 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new 7750048f2b 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new e41a0da9e3 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new 267d6827cc 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new d8561102db 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new 0bd4f90e94 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new b0a667baa2 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new 41207c72ef 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 88adf6200e 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new 6a371ae553 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new 54ba874b97 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new 13deea7817 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new eee39d301f 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 03f8cb9fb2 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new e8ea90c023 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new c8f8970d03 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new 97f653e7a9 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 456cdcce8c 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new fefd536f7a 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new e347295376 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 61b36f9ad3 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new 9e71deeb9e 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 1e669aab1e 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 3516ba6be0 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new 52faa6cc00 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new 070d5740af 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new d974672a06 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 4f27fa0859 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new e9a092d06a 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 768754ec8d 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new d8d498f4ed 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new b9967f7374 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 5edc1f35ab 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 7c40b9cfa5 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new 7ac8eed37c 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new 51570983e5 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new ed86474ea4 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new 96e204f11c 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new 1aff968e62 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new dbb10cce0e 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new 9ba1ab3c10 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new 5ba2b13b2e 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new 07c2c40be5 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new 7bb2427474 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 094ed2d5c3 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new bd53ba3cf4 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new f7b61ecd8a 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 92472fe532 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new c1f2802ae1 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new ade7e83c42 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new bad021cc17 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 8a1de1b86a 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 7fb7dd1464 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 1a65f5693d 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 84d2a8bded 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 5dc63755dc 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new a68e5271e4 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 18d279a518 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new cc698c4c31 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new c4c5f1e6a8 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new e0e2c9e08d 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 3b2c409ba4 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new cdd2158ceb 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 2103ad9e1c 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 7a48c30cd1 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new ad0f3c94ab 127: force: #27: : Failure after baseline build: no new commits new bdec31e97a 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 576416386a 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 167da83f8c 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new c3afbfb0d3 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new 5558e877c5 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 25d03b8c57 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 5eafce3f66 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new 7a6f0e457c 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new 94e7ad6378 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 63026a89c6 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new dccce68b69 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 40a5698b48 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 2832ae64db 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new a809a2582a 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 4c0b7eb2d9 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new efcc29d1d9 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 45725e2824 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new 2b9a16c144 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new a4457f9314 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 11f5dfee76 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new ffa83a3223 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] new c9a59758c4 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 594658d2b4 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 83282f95f4 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 562404d4fe 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 040d8fc685 153: onsuccess: #65: 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 (f3a2e15cc7) \ 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 -> 2228 bytes 02-prepare_abe/console.log.xz | Bin 2492 -> 2532 bytes 03-build_abe-binutils/console.log.xz | Bin 35404 -> 35056 bytes 04-build_abe-gcc/console.log.xz | Bin 203268 -> 203856 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8664 -> 8416 bytes 07-build_abe-glibc/console.log.xz | Bin 240772 -> 240896 bytes 08-build_abe-gdb/console.log.xz | Bin 34912 -> 34556 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 1720 -> 1716 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 | 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/check-regression-status.txt | 2 +- manifest.sh | 31 ++++++++++++--------- results | 3 --- 23 files changed, 49 insertions(+), 50 deletions(-) delete mode 100644 11-check_regression/results.regressions