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 02068a38e6 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards eb9d9b43fc 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 3cd2f4fe14 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards d721c26e1c 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] discards 986dff0c57 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards beca849a97 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 1f4b02d1bf 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 779a97f157 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards 612e08bc68 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 787c720605 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards e5599487da 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards a31c633ee2 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 7246e804d1 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 4e4cd20606 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards eccdedaafe 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 20c1b6f6ce 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards f801d7b7c8 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards 00de714586 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards 56fa53fab8 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards e0d42a95d5 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 54b2247d31 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards 2fd6fa1095 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 2de6892a3f 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 5ea5124fbd 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 403fb345cf 127: force: #27: : Failure after baseline build: no new commits discards cbb9002364 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 65ec1ecefb 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 721da442fc 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 6f2113dc02 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 56b71cc174 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 5f567ff387 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 948182d27e 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 239561d921 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 06802b26ce 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 2b913541bb 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 4a645a6937 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 96217d87d3 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards c4041b3df1 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 9bf3e6966b 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards d51912be7e 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 66f3702bd1 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards ff45d4dd0e 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 4737169b2f 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 12f3139091 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 3ae361ec86 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards cfca03ac96 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards 863b4e7d3f 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 2a83bf3948 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards d7f0d95ff6 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards 3fce8f0bb1 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards 65209e3570 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards 5146909fec 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards 0e67292bfa 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards 91e9dc1b92 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards 2b51fa825c 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards 5bf589960f 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards 2b72972ab3 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards 8fb8eb20c1 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards c4e939ccdc 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards e4d0091f1a 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards 718340db6d 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards e2497635d6 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards f9cda8b53d 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards 9896b09187 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 8ce0263956 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards ee1f06472f 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards acaf565ecb 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards 14bf994225 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards c91efe43fa 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards abf08245f5 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards 924333f228 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 846b65938f 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 3c8ecf43ac 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 099a11fd0d 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards dc663d4744 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards 0f7327cbf7 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards 90169c8622 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards 61343aa430 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 42dc46dca8 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards c91858498a 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards 09166f6234 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards 7b41765f90 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards 8ed5a7268f 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards a34c3917ce 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards b489e0c056 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 5983d8eb0d 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards d046234d9e 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards 4881f9b156 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards 0237e7f9fe 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards b0f51e19cf 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards 81209230c6 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards 64c354f5ff 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] discards f11c08f859 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] discards d84367dd65 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 1e5701998b 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards b408cf0c5f 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards f9faced66e 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] discards 1898761a87 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards 6169a77d77 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 8c3d0608eb 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards 49d3b4bc34 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] new 5479712402 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] new 1b39dbfaa1 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new 2a10892ef1 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new f02fd9cd61 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new fe4284ccdb 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] new 941d3c7795 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 87813addbd 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 72314a6cf7 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 8cec969c53 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new 2153d5474e 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new 22169caacd 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new 5ffca84784 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new 2ad5b1bb3f 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 211a267e17 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new ed838401ae 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new 86fb70ffd4 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new 6463ab4f89 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 5e8d2bde7c 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new ca1a95c9cf 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new a8900d3e4b 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new 58a082d71c 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new 180301c2ef 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new 798fa28995 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 66ef1f0bea 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 9217092db9 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new 980b39cbd6 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new 5207283ea7 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new 200c8fc656 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new e0297bdf88 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 3edbc17614 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new b601b538a0 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 77413e3ae0 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new e9d7f59ac3 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 0da9a5e912 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 0680277b9a 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new fd6b7fdc0e 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new c8632cee64 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 7db42def6c 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 1ce4f7ef52 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new 8e56bdeafa 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 5258494489 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new c952f372f8 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new 38260c7a48 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new b70e03bcf7 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 5e386bd43d 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new 7d71480fb9 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new 8f0b6f79f6 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new 943adb25e6 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new db7d0a33a1 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new 77cd2eac69 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new 00499e0287 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new e4613910c7 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new 19c4464f6b 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new ffa612c76c 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new 5ef44d3199 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 37278212f9 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new 9b96fefa6c 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new a7e4e13d06 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 3cb09759cd 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new e29b8c9945 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 25e05ecad7 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 93843b299d 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 977caee364 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 84d6ae813a 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 12da9ebc85 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 795f8aa6a0 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 6186c448c6 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new a20a084d7b 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 2a1f189950 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new bd2a8a42c8 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 65f9febc9e 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 6678eba97a 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new e4daa87cc2 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 83a7ac9df0 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 4d11c33e9c 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 3b65c035f8 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 41220801bb 127: force: #27: : Failure after baseline build: no new commits new e8fb03efe3 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 58dece10a8 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new da98074517 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 3cbddf3bcc 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new b9491c6d81 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 377e412662 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new ec34beb007 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new b3ca8213e6 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new de0dd46890 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new e887d93da7 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 8884b8f0a8 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 1b37426bef 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 2770babb54 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 4bbaa6f46b 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new e05805079d 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new c5a2be66e6 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 96efb31b4b 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new 64145a219e 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 1609d97421 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 0f49e42e49 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 9ba2d70cc9 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] new 25d7e54d70 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new fffaaa5a3a 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 6dd1095ff0 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new f3a2e15cc7 152: force: #64: : [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 (02068a38e6) \ 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 2056 -> 2184 bytes 02-prepare_abe/console.log.xz | Bin 2528 -> 2492 bytes 03-build_abe-binutils/console.log.xz | Bin 35216 -> 35404 bytes 04-build_abe-gcc/console.log.xz | Bin 203324 -> 203268 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8564 -> 8664 bytes 07-build_abe-glibc/console.log.xz | Bin 240592 -> 240772 bytes 08-build_abe-gdb/console.log.xz | Bin 34860 -> 34912 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3108 -> 1720 bytes 10-build_abe-check_gdb/flaky.xfail | 1 + 11-check_regression/console.log.xz | Bin 1292 -> 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 | 71 +++--- jenkins/notify.sh | 2 +- mail/check-regression-status.txt | 2 +- mail/results.compare | 7 - manifest.sh | 23 +- results | 5 +- sumfiles/gdb.log.xz | Bin 14432 -> 0 bytes sumfiles/gdb.sum | 409 -------------------------------- 23 files changed, 55 insertions(+), 517 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