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 622c8380b660 227: force: #81: 1: [TCWG CI] Failure after baseline build [...] discards eb58aca9440c 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards 74d97eed122b 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards d8918275d2e3 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards 07dd13547156 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 2cee9a753122 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/g [...] discards 55c72e333dc0 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards f536a0a41d0d 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards 769d571968b6 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 162cf6d77f50 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/g [...] discards 515e6597a810 217: onsuccess: #53: 1: Success after binutils/gcc/linux/g [...] discards 138a0219e2e0 216: onsuccess: #52: 1: Success after binutils/gcc/linux/g [...] discards 4ccb1374318e 215: onsuccess: #48: 1: Success after binutils/gcc/linux/g [...] discards 5311c667ab4b 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 398daf0200b4 213: force: #46: 1: Success after gdb-13-branchpoint-1550- [...] discards 2316daffd3be 212: force: #45: 1: Success after gdb: 22 commits discards 775f39b1ac51 211: onsuccess: #44: 1: Success after linux: 26 commits discards 1620c7b32b06 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181- [...] discards e20539b7e2b8 209: force: #37: 1: Success after baseline build: no new commits discards 531d2e9e4a68 208: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards d91406548cad 207: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards f11de2ccd345 206: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards bbd350d64a3a 205: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards da563626a9e8 204: force: #26: : Failure after baseline build: no new commits discards bc6e47849625 203: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 996379b6e348 202: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 2627fc0efbd4 201: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 42b3eac94800 200: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 4495fa409388 199: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 5505b8998e07 198: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 657e7e8c324b 197: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards 757a4db64d7f 196: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards ce7fb3aaf662 195: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards f49037f890cf 194: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards e85c16899511 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 2bc666f89f6f 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 22190518ab43 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards e73ffdd557d2 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards d54afa8d7772 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 3d26a8bf6fab 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards b8b6d503b45e 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 928064b0aacb 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards 557a88184937 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 90c5d6b5ac82 184: onsuccess: #977: 1: Success after binutils/gcc/linux/ [...] discards 2c6bc91040cf 183: onsuccess: #976: 1: Success after binutils/gcc/linux/ [...] discards 17beb9018ce2 182: onsuccess: #975: 1: Success after binutils/gcc/linux/ [...] discards 1278e258deef 181: onsuccess: #974: 1: Success after binutils/gcc/linux/ [...] discards af4d5193bda0 180: onsuccess: #973: 1: Success after binutils/gcc/linux/ [...] discards 953ec4a724d9 179: onsuccess: #972: 1: Success after binutils/gcc/linux/ [...] discards 236721932417 178: onsuccess: #971: 1: Success after binutils/gcc/linux/ [...] discards 749507cc98c1 177: onsuccess: #970: 1: Success after binutils/gcc/linux/ [...] discards f72b0c3d4e55 176: onsuccess: #969: 1: Success after binutils/gcc/linux/ [...] discards 63baeef29027 175: onsuccess: #968: 1: Success after binutils/gcc/linux/ [...] discards 5b1a0a4d0736 174: onsuccess: #967: 1: Success after binutils/gcc/linux/ [...] discards eab22887b097 173: onsuccess: #966: 1: Success after binutils/gcc/linux/ [...] discards 91f877fcbdc1 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/ [...] discards 8e00c6acd9cd 171: onsuccess: #964: 1: Success after binutils/gcc/linux/ [...] discards 0e5089849035 170: onsuccess: #963: 1: Success after binutils/gcc/linux/ [...] discards 687b31b6cde8 169: onsuccess: #962: 1: Success after binutils/gcc/linux/ [...] discards 995f8d70484f 168: onsuccess: #961: 1: Success after binutils/gcc/linux/ [...] discards 5a130b7de15d 167: onsuccess: #960: 1: Success after binutils/gcc/linux/ [...] discards ad96144d013c 166: onsuccess: #959: 1: Success after binutils/gcc/linux/ [...] discards f2ee9269f2e1 165: onsuccess: #958: 1: Success after binutils/gcc/linux/ [...] discards 74d946ee4d65 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/ [...] discards dc2c356d6a01 163: onsuccess: #956: 1: Success after binutils/gcc/linux/ [...] discards bab45b4ac16f 162: onsuccess: #955: 1: Success after binutils/gcc/linux/ [...] discards 5d3d16a0a0dc 161: onsuccess: #954: 1: Success after binutils/gcc/linux/ [...] discards 318f10fedadd 160: onsuccess: #953: 1: Success after binutils/gcc/linux/ [...] discards f964cdb9e848 159: onsuccess: #952: 1: Success after binutils/gcc/linux/ [...] discards dfc4e2613782 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 17b9e31b1753 157: onsuccess: #950: 1: Success after binutils/gcc/linux/ [...] discards fa6cc9cb727c 156: onsuccess: #949: 1: Success after binutils/gcc/linux/ [...] discards 9babdf2a8268 155: onsuccess: #948: 1: Success after binutils/gcc/linux/ [...] discards 937e9badbe99 154: onsuccess: #947: 1: Success after binutils/gcc/linux/ [...] discards e47b1263148c 153: onsuccess: #946: 1: Success after binutils/gcc/linux/ [...] discards 289faf37971c 152: onsuccess: #945: 1: Success after binutils/gcc/linux/ [...] discards 184d78e0a0b3 151: onsuccess: #944: 1: Success after binutils/gcc/linux/ [...] discards b0e63096170f 150: onsuccess: #943: 1: Success after binutils/gcc/linux/ [...] discards 8d870f4f0b97 149: onsuccess: #942: 1: Success after binutils/gcc/linux/ [...] discards fd606506b967 148: onsuccess: #941: 1: Success after binutils/gcc/linux/ [...] discards e38141a2d712 147: onsuccess: #940: 1: Success after binutils/gcc/linux/ [...] discards 60965e133ced 146: onsuccess: #939: 1: Success after binutils/gcc/linux/ [...] discards d504679bc294 145: onsuccess: #934: 1: Success after binutils/gcc/linux/ [...] discards 12d1a19959b4 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/ [...] discards 786368bdd607 143: onsuccess: #931: 1: Success after binutils/gcc/linux/ [...] discards 62b572a85838 142: onsuccess: #929: 1: Success after binutils/gcc/linux/ [...] discards 8ee2d401f16a 141: onsuccess: #928: 1: Success after binutils/gcc/linux/ [...] discards ba51759aac87 140: onsuccess: #927: 1: Success after binutils/gcc/linux/ [...] discards 94db141305b3 139: onsuccess: #926: 1: Success after binutils/gcc/linux/ [...] discards ca560c2c6359 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 1 [...] discards 281a44be2861 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 4 [...] discards 110ead664bbf 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 1 [...] discards 2ea29ae8a360 135: onsuccess: #922: 1: Success after binutils/gcc/linux/ [...] discards 03a515487be0 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 2 [...] discards 3134af289a2a 133: onsuccess: #920: 1: Success after binutils/gcc/linux/ [...] discards b4820af688bd 132: onsuccess: #919: 1: Success after binutils/gcc/linux/ [...] discards 801844726f7a 131: onsuccess: #918: 1: Success after binutils/gcc/linux/ [...] discards f868d1fd0bdd 130: onsuccess: #917: 1: Success after binutils/gcc/linux/ [...] discards 00524e887534 129: onsuccess: #916: 1: Success after binutils/gcc/linux/ [...] discards 40204d1e5385 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/ [...] discards 0752416f536e 127: onsuccess: #914: 1: Success after binutils/gcc/linux/ [...] new d36a924fddf9 127: onsuccess: #914: 1: Success after binutils/gcc/linux/ [...] new 15c2a445f6f4 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/ [...] new 812b839efe06 129: onsuccess: #916: 1: Success after binutils/gcc/linux/ [...] new 3f8198b3ed37 130: onsuccess: #917: 1: Success after binutils/gcc/linux/ [...] new c2bec719f60a 131: onsuccess: #918: 1: Success after binutils/gcc/linux/ [...] new 1020dd4bd54a 132: onsuccess: #919: 1: Success after binutils/gcc/linux/ [...] new 6e28b8638d73 133: onsuccess: #920: 1: Success after binutils/gcc/linux/ [...] new 913e63d30351 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 2 [...] new 793a4913cc79 135: onsuccess: #922: 1: Success after binutils/gcc/linux/ [...] new f73de1225937 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 1 [...] new 731c2b171822 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 4 [...] new ed9de0cd33e6 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 1 [...] new 6eccaf3f7996 139: onsuccess: #926: 1: Success after binutils/gcc/linux/ [...] new 39b13930233c 140: onsuccess: #927: 1: Success after binutils/gcc/linux/ [...] new 77255adb4423 141: onsuccess: #928: 1: Success after binutils/gcc/linux/ [...] new e24ce74b0302 142: onsuccess: #929: 1: Success after binutils/gcc/linux/ [...] new be9335eb2015 143: onsuccess: #931: 1: Success after binutils/gcc/linux/ [...] new 7f28c98928af 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/ [...] new 358fab7d1a5c 145: onsuccess: #934: 1: Success after binutils/gcc/linux/ [...] new c53d9c6c285d 146: onsuccess: #939: 1: Success after binutils/gcc/linux/ [...] new 22870d3027c6 147: onsuccess: #940: 1: Success after binutils/gcc/linux/ [...] new adb164e34f65 148: onsuccess: #941: 1: Success after binutils/gcc/linux/ [...] new e9471910ebcc 149: onsuccess: #942: 1: Success after binutils/gcc/linux/ [...] new c6fef5e0cb60 150: onsuccess: #943: 1: Success after binutils/gcc/linux/ [...] new 2ad0b6a99bd5 151: onsuccess: #944: 1: Success after binutils/gcc/linux/ [...] new ba6da5e5d4f8 152: onsuccess: #945: 1: Success after binutils/gcc/linux/ [...] new d221bd51c6f8 153: onsuccess: #946: 1: Success after binutils/gcc/linux/ [...] new 93e529d892a5 154: onsuccess: #947: 1: Success after binutils/gcc/linux/ [...] new 897c3f99ab92 155: onsuccess: #948: 1: Success after binutils/gcc/linux/ [...] new f778db52357f 156: onsuccess: #949: 1: Success after binutils/gcc/linux/ [...] new eb05b2c6bac9 157: onsuccess: #950: 1: Success after binutils/gcc/linux/ [...] new 9a2e39ff7379 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 183a76831dd6 159: onsuccess: #952: 1: Success after binutils/gcc/linux/ [...] new 3a8ff0f19473 160: onsuccess: #953: 1: Success after binutils/gcc/linux/ [...] new 941a380a09dc 161: onsuccess: #954: 1: Success after binutils/gcc/linux/ [...] new c12c042474d7 162: onsuccess: #955: 1: Success after binutils/gcc/linux/ [...] new c97d91b1b8d9 163: onsuccess: #956: 1: Success after binutils/gcc/linux/ [...] new b53fcb00bd77 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/ [...] new c6c73bb0f214 165: onsuccess: #958: 1: Success after binutils/gcc/linux/ [...] new 70ab0c6eeb45 166: onsuccess: #959: 1: Success after binutils/gcc/linux/ [...] new 482d075727ae 167: onsuccess: #960: 1: Success after binutils/gcc/linux/ [...] new bce3d5d7ffb6 168: onsuccess: #961: 1: Success after binutils/gcc/linux/ [...] new 8ffdc900e376 169: onsuccess: #962: 1: Success after binutils/gcc/linux/ [...] new 1756fdf53499 170: onsuccess: #963: 1: Success after binutils/gcc/linux/ [...] new d6d0b7614737 171: onsuccess: #964: 1: Success after binutils/gcc/linux/ [...] new 91362c145529 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/ [...] new 7bea4149db59 173: onsuccess: #966: 1: Success after binutils/gcc/linux/ [...] new 7f6a2041bb0f 174: onsuccess: #967: 1: Success after binutils/gcc/linux/ [...] new 356bf12ae1b0 175: onsuccess: #968: 1: Success after binutils/gcc/linux/ [...] new 706eb7db421b 176: onsuccess: #969: 1: Success after binutils/gcc/linux/ [...] new b886cbd04f71 177: onsuccess: #970: 1: Success after binutils/gcc/linux/ [...] new 056e22693dae 178: onsuccess: #971: 1: Success after binutils/gcc/linux/ [...] new 2c2ec98072ab 179: onsuccess: #972: 1: Success after binutils/gcc/linux/ [...] new bd2223afe89d 180: onsuccess: #973: 1: Success after binutils/gcc/linux/ [...] new ecc0631ced26 181: onsuccess: #974: 1: Success after binutils/gcc/linux/ [...] new 36ceec0ca1a8 182: onsuccess: #975: 1: Success after binutils/gcc/linux/ [...] new e7e55d04a5bc 183: onsuccess: #976: 1: Success after binutils/gcc/linux/ [...] new 66775a029667 184: onsuccess: #977: 1: Success after binutils/gcc/linux/ [...] new 24b04c7f5a8f 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 83a849fd965b 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new de6bc5237da0 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 8af782226d2e 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new a12ba7379ad4 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 87395cf1a29e 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 8d057f8da6c8 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 5d360aa1ca8c 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new f62913402602 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 3e0a01e8ab71 194: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 12ce94584362 195: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 3c2265760214 196: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 30b042824b2d 197: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 33c4829406a8 198: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 84b07eb740ab 199: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 67cc19dc9779 200: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 2f904b59c708 201: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 85bbe575d6a9 202: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 5670fdb0a77d 203: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new ebde23a34ebc 204: force: #26: : Failure after baseline build: no new commits new a58cc6a9fbe3 205: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 2458a559aa5c 206: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new bf3947d52e8b 207: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new ba7e6759a53d 208: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 5ea1c5467bc2 209: force: #37: 1: Success after baseline build: no new commits new 2093807724ba 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181- [...] new d166dbde0d98 211: onsuccess: #44: 1: Success after linux: 26 commits new 9150b920f1f4 212: force: #45: 1: Success after gdb: 22 commits new 4a2f6406d88f 213: force: #46: 1: Success after gdb-13-branchpoint-1550- [...] new d91c6d29748a 214: onsuccess: #47: 1: Success after gdb: 21 commits new dc0a211a75d6 215: onsuccess: #48: 1: Success after binutils/gcc/linux/g [...] new a9f102a63588 216: onsuccess: #52: 1: Success after binutils/gcc/linux/g [...] new 65a5defdb77a 217: onsuccess: #53: 1: Success after binutils/gcc/linux/g [...] new c88b3b08ac09 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/g [...] new aeaa8fcb022c 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new fd0e0b766534 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchp [...] new b0cfa4e19572 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 248a2b7e9485 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/g [...] new c2937038e2a4 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 3ae4d51ca1b1 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchp [...] new 98875f115742 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new 59e59962646b 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new 6908e44a0244 227: force: #81: 1: [TCWG CI] Failure after baseline build [...] new 3fb84bee3ce8 228: force: #82: 1: [TCWG CI] Success after glibc: 4 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 (622c8380b660) \ 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 2068 -> 2060 bytes 02-prepare_abe/console.log.xz | Bin 2528 -> 2520 bytes 03-build_abe-binutils/console.log.xz | Bin 35984 -> 35736 bytes 04-build_abe-gcc/console.log.xz | Bin 205776 -> 204072 bytes 06-build_abe-linux/console.log.xz | Bin 8688 -> 8720 bytes 07-build_abe-glibc/console.log.xz | Bin 242596 -> 241164 bytes 08-build_abe-gdb/console.log.xz | Bin 35176 -> 35476 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3808 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3112 -> 3252 bytes 11-check_regression/console.log.xz | Bin 2908 -> 3232 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 6 - 11-check_regression/results.compare | 9 +- 11-check_regression/results.regressions | 14 - 12-update_baseline/console.log | 44 +- dashboard/dashboard-generate.sh | 2 +- git/glibc_rev | 2 +- mail/changes-list-long.txt | 6 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 19 +- mail/short-diag.txt | 2 +- manifest.sh | 15 +- results | 14 - sumfiles/gdb.log.0.xz | Bin 1979592 -> 1941444 bytes sumfiles/gdb.log.1.xz | Bin 31148 -> 22152 bytes sumfiles/gdb.log.2.xz | Bin 0 -> 5436 bytes sumfiles/gdb.log.3.xz | Bin 0 -> 5504 bytes sumfiles/gdb.sum | 1691 +++++++++++++++++------------- sumfiles/gdb.sum.0 | 1695 ++++++++++++++++++------------- sumfiles/gdb.sum.1 | 336 ++++-- sumfiles/gdb.sum.2 | 182 ++++ sumfiles/gdb.sum.3 | 182 ++++ 32 files changed, 2655 insertions(+), 1567 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions 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