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_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts.
discards 3642421eda2f 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/g [...] discards 68808abded04 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37 [...] discards 2c445c9a9340 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.900 [...] discards 39734a499356 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards d6fee72b2408 227: force: #81: 1: [TCWG CI] Failure after baseline build [...] discards ca1d9285ac96 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards 418edb474991 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards b0c10eb7a10f 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards ec687d706938 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 5301f27bd365 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/g [...] discards e8e986cc2bed 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards 4e04b2241229 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards 06f047c083b4 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 74e09eafdd48 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/g [...] discards 945f81bc508f 217: onsuccess: #53: 1: Success after binutils/gcc/linux/g [...] discards a5eb1af7e400 216: onsuccess: #52: 1: Success after binutils/gcc/linux/g [...] discards d399e285b03f 215: onsuccess: #48: 1: Success after binutils/gcc/linux/g [...] discards 5e358a7dd643 214: onsuccess: #47: 1: Success after gdb: 21 commits discards cc3fda90da54 213: force: #46: 1: Success after gdb-13-branchpoint-1550- [...] discards 1b1334798af0 212: force: #45: 1: Success after gdb: 22 commits discards bb2512f59011 211: onsuccess: #44: 1: Success after linux: 26 commits discards 2c87bbe1f1a7 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181- [...] discards 9641980936ea 209: force: #37: 1: Success after baseline build: no new commits discards 2013321e314c 208: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards 4c9bac3cc221 207: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 81f0f6deb1d9 206: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 323dc0ac06ff 205: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards ed34f204f39b 204: force: #26: : Failure after baseline build: no new commits discards 3ab017f7db1e 203: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 8cf2aea6f47e 202: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 1689007b660e 201: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 5535ff1fd57d 200: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 826a22fe97de 199: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 42ee69530318 198: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 1ab4adc1c56f 197: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards 573752c31523 196: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards 910141ada0ff 195: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 6e6c5cece529 194: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 2142e9e78941 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards d9dcc82f3575 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards bf6eaee63b77 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards 6badf420f218 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards e7d15d4a5690 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 2e2a2eeb8cc7 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards f0bfd865d201 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards ba012cb7510a 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards 543be5138482 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 1da39e281561 184: onsuccess: #977: 1: Success after binutils/gcc/linux/ [...] discards 0805635fb141 183: onsuccess: #976: 1: Success after binutils/gcc/linux/ [...] discards 8b2a317d325e 182: onsuccess: #975: 1: Success after binutils/gcc/linux/ [...] discards d2d646d6815b 181: onsuccess: #974: 1: Success after binutils/gcc/linux/ [...] discards 0c7a57e7e81c 180: onsuccess: #973: 1: Success after binutils/gcc/linux/ [...] discards 2e3fa9e8faf4 179: onsuccess: #972: 1: Success after binutils/gcc/linux/ [...] discards bd58dc654f3e 178: onsuccess: #971: 1: Success after binutils/gcc/linux/ [...] discards 180ff4cd4674 177: onsuccess: #970: 1: Success after binutils/gcc/linux/ [...] discards fcb5e0605dec 176: onsuccess: #969: 1: Success after binutils/gcc/linux/ [...] discards 7779a41b24cf 175: onsuccess: #968: 1: Success after binutils/gcc/linux/ [...] discards 794786c1d650 174: onsuccess: #967: 1: Success after binutils/gcc/linux/ [...] discards 5669a9e50293 173: onsuccess: #966: 1: Success after binutils/gcc/linux/ [...] discards 5f3f9e8908e7 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/ [...] discards 88d750ef91d4 171: onsuccess: #964: 1: Success after binutils/gcc/linux/ [...] discards 229c276b7317 170: onsuccess: #963: 1: Success after binutils/gcc/linux/ [...] discards ab1f9ea869e0 169: onsuccess: #962: 1: Success after binutils/gcc/linux/ [...] discards 970247698161 168: onsuccess: #961: 1: Success after binutils/gcc/linux/ [...] discards e34b7679704b 167: onsuccess: #960: 1: Success after binutils/gcc/linux/ [...] discards d4cf233314ad 166: onsuccess: #959: 1: Success after binutils/gcc/linux/ [...] discards dc99d6fe37cd 165: onsuccess: #958: 1: Success after binutils/gcc/linux/ [...] discards 26d75687ab0e 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/ [...] discards 7e084624b98d 163: onsuccess: #956: 1: Success after binutils/gcc/linux/ [...] discards e0c8be13c3ac 162: onsuccess: #955: 1: Success after binutils/gcc/linux/ [...] discards 546fc74a973e 161: onsuccess: #954: 1: Success after binutils/gcc/linux/ [...] discards f288053909f1 160: onsuccess: #953: 1: Success after binutils/gcc/linux/ [...] discards 9dbc20f55c9e 159: onsuccess: #952: 1: Success after binutils/gcc/linux/ [...] discards 02a9becd71f5 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards be2ad37d0489 157: onsuccess: #950: 1: Success after binutils/gcc/linux/ [...] discards 5af874029e6b 156: onsuccess: #949: 1: Success after binutils/gcc/linux/ [...] discards 33289511df34 155: onsuccess: #948: 1: Success after binutils/gcc/linux/ [...] discards 8e3b1dd875f1 154: onsuccess: #947: 1: Success after binutils/gcc/linux/ [...] discards 1d8118d31478 153: onsuccess: #946: 1: Success after binutils/gcc/linux/ [...] discards 0b571d85b3dd 152: onsuccess: #945: 1: Success after binutils/gcc/linux/ [...] discards 991eafe4ca30 151: onsuccess: #944: 1: Success after binutils/gcc/linux/ [...] discards 1264f2138cf3 150: onsuccess: #943: 1: Success after binutils/gcc/linux/ [...] discards a86cf2ff9532 149: onsuccess: #942: 1: Success after binutils/gcc/linux/ [...] discards 34f52f4bb267 148: onsuccess: #941: 1: Success after binutils/gcc/linux/ [...] discards 32c6af79fcfa 147: onsuccess: #940: 1: Success after binutils/gcc/linux/ [...] discards b719c5865bc7 146: onsuccess: #939: 1: Success after binutils/gcc/linux/ [...] discards 585edafa910f 145: onsuccess: #934: 1: Success after binutils/gcc/linux/ [...] discards e50e4f2a3db9 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/ [...] discards 1186b1f74078 143: onsuccess: #931: 1: Success after binutils/gcc/linux/ [...] discards ab0664b7f1ef 142: onsuccess: #929: 1: Success after binutils/gcc/linux/ [...] discards f9d3cfe2675c 141: onsuccess: #928: 1: Success after binutils/gcc/linux/ [...] discards fed4d187f35e 140: onsuccess: #927: 1: Success after binutils/gcc/linux/ [...] discards 17bde6c71ad2 139: onsuccess: #926: 1: Success after binutils/gcc/linux/ [...] discards f7d9ae32d42d 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 1 [...] discards 12489101c8c1 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 4 [...] discards d7df4118ddcf 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 1 [...] discards 662204fba3e6 135: onsuccess: #922: 1: Success after binutils/gcc/linux/ [...] discards 7a8ae240d8bc 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 2 [...] discards 522e1147ecdb 133: onsuccess: #920: 1: Success after binutils/gcc/linux/ [...] discards 73b304dc9ae9 132: onsuccess: #919: 1: Success after binutils/gcc/linux/ [...] discards f21e2f69e6b6 131: onsuccess: #918: 1: Success after binutils/gcc/linux/ [...] new 9796573df15b 131: onsuccess: #918: 1: Success after binutils/gcc/linux/ [...] new 18a4d043164e 132: onsuccess: #919: 1: Success after binutils/gcc/linux/ [...] new e7a00859c06d 133: onsuccess: #920: 1: Success after binutils/gcc/linux/ [...] new 3cac8bf2b514 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 2 [...] new eacfa25827f9 135: onsuccess: #922: 1: Success after binutils/gcc/linux/ [...] new 6f66f2fa4bfd 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 1 [...] new d65f9651c3bd 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 4 [...] new 7f3cec780792 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 1 [...] new 3e806b9a3b84 139: onsuccess: #926: 1: Success after binutils/gcc/linux/ [...] new c7531c38c562 140: onsuccess: #927: 1: Success after binutils/gcc/linux/ [...] new d7b81634c350 141: onsuccess: #928: 1: Success after binutils/gcc/linux/ [...] new 892021241691 142: onsuccess: #929: 1: Success after binutils/gcc/linux/ [...] new a5b08151ad54 143: onsuccess: #931: 1: Success after binutils/gcc/linux/ [...] new b927b436857e 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/ [...] new 2041dd6ab04a 145: onsuccess: #934: 1: Success after binutils/gcc/linux/ [...] new dfbf28941ffd 146: onsuccess: #939: 1: Success after binutils/gcc/linux/ [...] new de8f56d52879 147: onsuccess: #940: 1: Success after binutils/gcc/linux/ [...] new 43aaa62df888 148: onsuccess: #941: 1: Success after binutils/gcc/linux/ [...] new 037cae668efd 149: onsuccess: #942: 1: Success after binutils/gcc/linux/ [...] new 005777fd5c80 150: onsuccess: #943: 1: Success after binutils/gcc/linux/ [...] new adf423b8dd79 151: onsuccess: #944: 1: Success after binutils/gcc/linux/ [...] new 457b0a02d72c 152: onsuccess: #945: 1: Success after binutils/gcc/linux/ [...] new 3f72947981c2 153: onsuccess: #946: 1: Success after binutils/gcc/linux/ [...] new 5a740d9a254d 154: onsuccess: #947: 1: Success after binutils/gcc/linux/ [...] new fdf7c70e32e8 155: onsuccess: #948: 1: Success after binutils/gcc/linux/ [...] new 9c4138a7fa3c 156: onsuccess: #949: 1: Success after binutils/gcc/linux/ [...] new 489b15f18008 157: onsuccess: #950: 1: Success after binutils/gcc/linux/ [...] new e0da84520595 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 5f3ac8171285 159: onsuccess: #952: 1: Success after binutils/gcc/linux/ [...] new 0bdff104fb21 160: onsuccess: #953: 1: Success after binutils/gcc/linux/ [...] new dbba8575ecf0 161: onsuccess: #954: 1: Success after binutils/gcc/linux/ [...] new cdd1751bd1f0 162: onsuccess: #955: 1: Success after binutils/gcc/linux/ [...] new ef3892812ba8 163: onsuccess: #956: 1: Success after binutils/gcc/linux/ [...] new f5edf9531a87 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/ [...] new b43487132125 165: onsuccess: #958: 1: Success after binutils/gcc/linux/ [...] new c4c69a54e1c6 166: onsuccess: #959: 1: Success after binutils/gcc/linux/ [...] new d25ce7d6e137 167: onsuccess: #960: 1: Success after binutils/gcc/linux/ [...] new 596b12dc9c91 168: onsuccess: #961: 1: Success after binutils/gcc/linux/ [...] new f62f4caef3c7 169: onsuccess: #962: 1: Success after binutils/gcc/linux/ [...] new da2d78552547 170: onsuccess: #963: 1: Success after binutils/gcc/linux/ [...] new b71fcca0e189 171: onsuccess: #964: 1: Success after binutils/gcc/linux/ [...] new cea89db907ed 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/ [...] new 086ac5c59dbd 173: onsuccess: #966: 1: Success after binutils/gcc/linux/ [...] new d89d36301047 174: onsuccess: #967: 1: Success after binutils/gcc/linux/ [...] new 435f17540273 175: onsuccess: #968: 1: Success after binutils/gcc/linux/ [...] new b34468f09296 176: onsuccess: #969: 1: Success after binutils/gcc/linux/ [...] new a209cba5f05b 177: onsuccess: #970: 1: Success after binutils/gcc/linux/ [...] new e2b36fcb9d4f 178: onsuccess: #971: 1: Success after binutils/gcc/linux/ [...] new 6bd175b6ddbd 179: onsuccess: #972: 1: Success after binutils/gcc/linux/ [...] new 90f5d431b1fb 180: onsuccess: #973: 1: Success after binutils/gcc/linux/ [...] new fc50fc91d038 181: onsuccess: #974: 1: Success after binutils/gcc/linux/ [...] new 8dd6dea3875d 182: onsuccess: #975: 1: Success after binutils/gcc/linux/ [...] new 2f709041007f 183: onsuccess: #976: 1: Success after binutils/gcc/linux/ [...] new 41b677eee84f 184: onsuccess: #977: 1: Success after binutils/gcc/linux/ [...] new 0520f0328188 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 703bc6e362eb 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new ac90b674cdb2 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new c68be30522ca 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new c9a34aec135d 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new a44149a1c282 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new f43b73428ddd 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 9f4c64ee2e2e 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new a4f174aca4ec 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new cda4dcbdc040 194: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 193393611c86 195: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 28d612a39c1b 196: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new de440ae8d26c 197: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 4d6405c86c2f 198: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 4f2a6da79079 199: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 69303543a431 200: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 5708095bfaec 201: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 9af6fdfdb92e 202: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new d99fa5d8c373 203: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new f792af40988a 204: force: #26: : Failure after baseline build: no new commits new e13d3d0e9f6f 205: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 8081fc1f0930 206: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new c1e18c298694 207: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 773fe9aad9d6 208: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new a0f92fc50410 209: force: #37: 1: Success after baseline build: no new commits new 31f5a8a517ac 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181- [...] new 7b22e2a0d367 211: onsuccess: #44: 1: Success after linux: 26 commits new 4513a94125bb 212: force: #45: 1: Success after gdb: 22 commits new 85f4d82b4fb0 213: force: #46: 1: Success after gdb-13-branchpoint-1550- [...] new fbd11fb8002c 214: onsuccess: #47: 1: Success after gdb: 21 commits new ce6b3493a45d 215: onsuccess: #48: 1: Success after binutils/gcc/linux/g [...] new ae19fcd6d660 216: onsuccess: #52: 1: Success after binutils/gcc/linux/g [...] new 40e2c38189ac 217: onsuccess: #53: 1: Success after binutils/gcc/linux/g [...] new 8ab674f6b076 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/g [...] new 66ff5ab45de1 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new f41840293e16 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchp [...] new ea01172890ad 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 5f12c4895cd9 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/g [...] new a63fce81ea4c 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new bfe08beb14fa 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchp [...] new dc083791498c 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new c93990530ae9 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new 320c4aa054fe 227: force: #81: 1: [TCWG CI] Failure after baseline build [...] new e6c8052ddad9 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new 04c783784416 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.900 [...] new f0d9b711e32f 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37 [...] new 0b60e070f4a4 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/g [...] new d9212ed9fc21 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits
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 (3642421eda2f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...]
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 1996 -> 1984 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2520 bytes 03-build_abe-binutils/console.log.xz | Bin 34816 -> 34988 bytes 04-build_abe-gcc/console.log.xz | Bin 203088 -> 203244 bytes 06-build_abe-linux/console.log.xz | Bin 8928 -> 8976 bytes 07-build_abe-glibc/console.log.xz | Bin 240788 -> 241148 bytes 08-build_abe-gdb/console.log.xz | Bin 35400 -> 34644 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3780 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3116 -> 2620 bytes 11-check_regression/console.log.xz | Bin 10880 -> 4472 bytes 11-check_regression/results.compare | 10 +- 11-check_regression/results.compare2 | 1056 +++------------------------------ 12-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- mail/changes-list-long.txt | 17 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 29 +- manifest.sh | 25 +- sumfiles/gdb.log.0.xz | Bin 1986560 -> 2004004 bytes sumfiles/gdb.log.1.xz | Bin 16976 -> 29420 bytes sumfiles/gdb.log.2.xz | Bin 0 -> 15496 bytes sumfiles/gdb.log.3.xz | Bin 0 -> 15664 bytes sumfiles/gdb.sum | 44 +- sumfiles/gdb.sum.0 | 43 +- sumfiles/gdb.sum.1 | 115 +++- sumfiles/gdb.sum.2 | 110 ++++ sumfiles/gdb.sum.3 | 110 ++++ 28 files changed, 496 insertions(+), 1115 deletions(-) create mode 100644 sumfiles/gdb.log.2.xz create mode 100644 sumfiles/gdb.log.3.xz create mode 100644 sumfiles/gdb.sum.2 create mode 100644 sumfiles/gdb.sum.3