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 ac971f2af63 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 5a3d3bed274 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 858e29331ea 204: force: #26: : Failure after baseline build: no new commits discards 74c64d3a810 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 0396ebc6fcb 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 15a73472ed7 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 08adff23b88 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 27b9ee6ae26 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 389256e9032 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 4c78c743633 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards a0c31188907 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 934c34c7f53 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 698450971a6 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 673169f00a4 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards a161db7f38c 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards aba6b11e857 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 7839b2f0d1c 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 2dc3dd8ae22 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 099fc69319f 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards f97fbd8914c 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards c06d299fd14 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards cb5ae9a410c 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 141ca020668 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards 8de71ad8489 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards c55b8fea62b 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards 94ca4240c39 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards 872018f8533 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 599834ec095 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards a49b9def6f2 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards 715ccd6ba39 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards 7423618ff8a 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards 3569caf7f3b 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 06d2996ef38 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards 99eb7d66ef7 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards a51f3112edb 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 2473ab20b1b 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards cf825b2ba22 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards 2ab3fa5b587 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 7704ece9941 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards 9328d00aefe 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards a3268cc8788 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards c2797a5aea7 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards c845e42966e 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards 2b4c3e7aba0 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 79dd7cca3ad 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards 55f9577633f 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards a537fe22928 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards 294c37765b4 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 865df962375 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards f01f29ca436 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 5551ee6c3c9 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards 3bb5c225492 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 19e1a1317be 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 20ec0aa7919 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards e45fb0de382 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards afa39de6580 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 4badade0053 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards ea83d43af3a 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 0fc7b8b87f9 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 5e26b2fb148 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 56f402e0990 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 772dd0ccaf4 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 1150ad31445 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards 4edde5baa72 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 15f9dc818c3 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 7581786f9c7 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 0a06d10b3a1 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 035668296f6 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 9aba0357ea3 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards fe2f7eba519 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards 0d584e15339 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards 8801b690d61 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 7738b92337b 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards 045f5ad1196 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 83f9a653b30 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards fdf823a1984 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards b56e1a1c1be 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards ed50b400edd 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 60fd75ee229 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards 2bda5368cef 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards a0c3d0a78aa 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards e7dee46cbcd 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards de8bdf11ea7 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 18fcf96e8ef 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 5f198a17f32 122: onsuccess: #909: 1: Success after linux: 2753 commits discards b18ee9f873c 121: onsuccess: #908: 1: Success after glibc: 2 commits discards a556cf543ec 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 38bdb02efb3 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 8f6e035fc72 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards 51164eb75e2 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards ccd98a6c16b 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards 556fa45f8df 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards f1f40b64cfb 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards 2e7883a5d69 113: onsuccess: #898: 1: Success after linux: 3 commits discards 9ac7547ffbb 112: onsuccess: #896: 1: Success after binutils: 24 commits discards c837d20939e 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards 7b94c9d5c17 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 2dcb7fb413b 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards e9f229eb5bc 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards c8c2832fa11 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards f33b096540d 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 0a9c9350950 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 7b011937a96 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 8136fce9963 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 8e87d3f6a72 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new 8fdafe1bc4b 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 162bc711aee 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 311d8758243 112: onsuccess: #896: 1: Success after binutils: 24 commits new 267a8866226 113: onsuccess: #898: 1: Success after linux: 3 commits new b582a717e06 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 343ab397b38 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new d71fcb2c94b 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new 9d408001b17 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new 18133eb6351 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 4e3728992ab 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 43a4734b575 120: onsuccess: #906: 1: Success after binutils: 29 commits new 6913ff5a111 121: onsuccess: #908: 1: Success after glibc: 2 commits new c35572b8fa5 122: onsuccess: #909: 1: Success after linux: 2753 commits new 45f0eee13aa 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 212d9c9ef89 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new a1213fd054d 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 46387ccb342 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 5e9b1b17ee0 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new fefcacf49f8 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new d6128234ea2 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 0435b5b5ee6 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 6a5f35ae914 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new e77d45592a3 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new bc06ad15ac9 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 0c70e0b3e95 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new 3ec39b60130 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 80af1bab75c 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 9f547482de8 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new 4b3f8f4871e 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new dbae49dad30 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 5e1067023e8 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 1740f70d9ab 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 6fb8d1e3d1a 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new d88f12fb00a 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new ae44ed1819a 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new 3da86ae2406 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new fd857a08290 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 78b216b4314 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new beec9e2aaaf 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 3f1cb9f3a9b 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new a6e9e05bc49 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 44a1e93b4a0 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new aed62960eb2 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 53d58e76c2c 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 0341448b45c 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 7e356c4df01 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 94bd12d29b7 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 7982b1a81f2 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 7c7c2617442 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new b3a68b8fc7a 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new 2883bb8f849 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new 3d1d7579247 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 47e86e02703 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 1e151b495dc 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new b4274d48a07 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 600e75cf46d 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new b7f32cd91ff 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new 1616611c20a 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 7d45ef92ecd 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new 9ddaf642aa8 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 75d38c4b964 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new da2f3581271 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 15d207059be 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new 053d54f38e6 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new f1aa6dc339a 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 945bde6b0d1 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new da6ff5e6d0f 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new 845109ddbb2 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 65857556d8f 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 59e3ca5739e 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new 09dcd8e7797 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new 69f0908d642 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new 4a02d827940 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new e6bc8cc354f 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 88963063be7 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 2cd6fbfa7df 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new ed5c73905ea 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new a130b07165f 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 5b62d9663cc 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new fcd7a8ae659 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new fef939bc442 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 7568828f5ab 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 822bb94c1f9 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new fc05875b6a4 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 3582f8fa2ed 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 8f6b86ed485 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 27c8e923cdd 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 48720cea33f 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new fabce85f550 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 6dca639ae65 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 47283ac8278 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 9787542a957 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new de1d572c553 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new e51e00862ae 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new ae02bcfd302 204: force: #26: : Failure after baseline build: no new commits new 4acafb10c1b 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new c0ca3b5f2c3 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 3230119cefa 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...]

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 (ac971f2af63) \ 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 1804 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2480 -> 2484 bytes 03-build_abe-binutils/console.log.xz | Bin 34996 -> 34968 bytes 04-build_abe-gcc/console.log.xz | Bin 202676 -> 203032 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9884 -> 8876 bytes 07-build_abe-glibc/console.log.xz | Bin 241896 -> 241856 bytes 08-build_abe-gdb/console.log.xz | Bin 34596 -> 34492 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3792 -> 3780 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2656 -> 2644 bytes 11-check_regression/console.log.xz | Bin 13676 -> 5584 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 78 +-- 11-check_regression/mail-body.txt | 54 +- 11-check_regression/results.compare | 429 +----------- 11-check_regression/results.compare2 | 1126 +------------------------------ 11-check_regression/results.regressions | 95 +-- 12-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 56 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 95 +-- sumfiles/gdb.log.0.xz | Bin 1913244 -> 1924668 bytes sumfiles/gdb.log.1.xz | Bin 33764 -> 39740 bytes sumfiles/gdb.log.2.xz | Bin 0 -> 14988 bytes sumfiles/gdb.sum | 28 +- sumfiles/gdb.sum.0 | 28 +- sumfiles/gdb.sum.1 | 335 ++++++++- sumfiles/gdb.sum.2 | 110 +++ 35 files changed, 643 insertions(+), 1879 deletions(-) create mode 100644 sumfiles/gdb.log.2.xz create mode 100644 sumfiles/gdb.sum.2