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-arm in repository toolchain/ci/base-artifacts.

discards 8df8571f42 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 59b726c7df 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 3f1db5f9b7 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 77010a380b 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 74c0d6cbf0 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 95dd916753 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards a7d4d63044 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 0ecb9eb731 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 969efd5351 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 2c7b059052 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards f560de88ad 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 6d0ad9485e 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards cdce99b574 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 0a41fc572c 92: onsuccess: #575: 1: Success after linux: 34 commits discards c0add0c306 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 7804ef2a23 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 12a9c94f73 89: onsuccess: #570: 1: Success after linux: 11 commits discards f2886a5971 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 01e04b807d 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 6bcd9b280c 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 60b47cc4bb 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards d482add6d3 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 165f464867 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 6c33445430 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards bbc2b84909 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards b586562263 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards b7a2282a85 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards deaff0a8de 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 6306b0d22d 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 3fc37a0d58 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 885e7689ae 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 243f01668d 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards bdcc6c082c 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards b550088379 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards ad31d90f62 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 60a1ca5d19 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 4af07a8b0f 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 718faf7f33 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards 128767c038 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 4d88977c2c 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 278a8d4b80 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 11bea1e487 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 9fa0e13f64 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 4e3ed4db67 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 894300e4ad 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 59ca598d5f 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards 87bbb2ffe2 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards a857e24e8c 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards ad3e746e89 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards 47119abd62 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 7ddf8c8b66 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards eb6671685e 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards 5a9321e1ff 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 3f0389e14e 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 89207fd68b 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 2ba9b30c52 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards 1ca7fc4350 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards b8d7abd8bc 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards b8dd1f4c47 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards 785b3ae0b2 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 0230417781 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards 32a0716781 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards dde2cf6b89 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards d857c4f3ed 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards faad47e347 41: onsuccess: #514: 1: Success after linux: 64 commits discards 48404185cd 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] discards 5319063246 39: onsuccess: #511: 1: Success after binutils: 8 commits discards dcd5306e62 38: onsuccess: #508: 1: Success after binutils: 3 commits discards e8bc182d6a 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards 3ae66a805b 36: onsuccess: #505: 1: Success after glibc: 3 commits discards 5b4c4e8d02 35: onsuccess: #503: 1: Success after binutils: 11 commits discards 9652086dbe 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 07d83100af 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] discards 33b28a29a3 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 36521113b5 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 0494854fea 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 28010d60bb 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 3ac174d1a7 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] discards e91517e27a 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 2e2865e948 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] discards 56c0fe9a96 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards ef17aff5ba 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards f2f88712bf 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 0f92ae5d71 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 63df868651 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8f1d6eec19 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a8369db470 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e5e8849f2f 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 72f27e8ce2 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f12fdd6e86 16: onsuccess: 1: Successful build after binutils: 4 commits discards c816ac498a 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a58c6c58ff 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ecbd5cb18e 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e5fbeb822e 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 81f91a4f17 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6cae48cd11 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ea5987088a 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards deffd375ef 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards d6ff279cd2 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 75e306a484 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 620c87c8d1 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new aba58b514e 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 9211da7af4 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 2a35d72b3d 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 21315fb335 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 7a78e8288c 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a8ee62b579 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f8e89a11d8 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7edfff1467 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new aac2287c9b 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 525dbb1f0f 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a939f5d5e7 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1f7c6180a7 16: onsuccess: 1: Successful build after binutils: 4 commits new 6581c62d02 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2d4a47d35f 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0da74e70c9 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2f308d36f8 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 650cd0cc02 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 92210b90a7 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new fd8888600b 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new d73433debd 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 8e709936ae 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 5df662e489 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] new a6706e2e5c 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 3e2fe46b77 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] new d65a6fadb1 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 8f5777b3d0 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 1d2dd0523e 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 056ebbb339 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 70c71db5c8 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] new dac5f1f34c 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 17f7110de3 35: onsuccess: #503: 1: Success after binutils: 11 commits new a4e440be8c 36: onsuccess: #505: 1: Success after glibc: 3 commits new c038def0d7 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] new b6fa846f3c 38: onsuccess: #508: 1: Success after binutils: 3 commits new 2285660d25 39: onsuccess: #511: 1: Success after binutils: 8 commits new 66b2b43da8 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new 1c3c284af0 41: onsuccess: #514: 1: Success after linux: 64 commits new 20d5900039 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new bf07112156 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new b66ec19316 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new d1f1de0cd5 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new c833816993 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new b3148e607d 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new f5e4da360d 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new bebf7d5de2 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 15b85290e1 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new 8d0c649601 51: onsuccess: #525: 1: Success after binutils: 8 commits new 7f4d2dd5a4 52: onsuccess: #528: 1: Success after binutils: 8 commits new 0c4f3d1156 53: onsuccess: #531: 1: Success after binutils: 12 commits new cd5a26e911 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new 4fa56bd985 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 9896efad77 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new dc7839abcd 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new a0cca6d0cb 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 15cec891ca 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new ff8fcff926 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new 4a99154121 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 4e0bdea030 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 8f443aa285 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 10903702e7 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 5307912a3e 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 94e803c109 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 56e564ddf5 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new f262f1324c 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 97426bd3c1 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 19a82fb123 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 8ffbbc92ee 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new a03398ca7e 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 0f59dffd17 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 525532b8f3 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 444aececee 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new bed8ef6a42 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new e963165e3c 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new ad9a789ccd 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 0b25d5aa10 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new c672fd7499 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new e192a66f8e 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new c465d66047 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 40b9073650 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 1a47a816d6 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 3cd4dbca77 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 39bfa66f21 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 1aa01191cb 87: onsuccess: #567: 1: Success after binutils: 8 commits new e0ff28adff 88: onsuccess: #569: 1: Success after glibc: 10 commits new ec347c2585 89: onsuccess: #570: 1: Success after linux: 11 commits new fed377228d 90: onsuccess: #572: 1: Success after binutils: 15 commits new a7f6c58097 91: onsuccess: #574: 1: Success after glibc: 3 commits new dba7d1e11e 92: onsuccess: #575: 1: Success after linux: 34 commits new 100ce21e48 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 29ea301e62 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new a000c011ed 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new befb26d69d 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new aca0690a23 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 62bc4158ef 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 8169404e1c 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 215d329b19 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new a41198e345 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new ea04f6bd58 102: onsuccess: #586: 1: Success after binutils: 5 commits new 2e3ebe7915 103: onsuccess: #589: 1: Success after binutils: 3 commits new 00a28c7bcf 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 392dfa6a66 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new ad747f2e3d 106: onsuccess: #593: 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 (8df8571f42) \ 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 1688 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 52564 -> 53736 bytes 04-build_abe-gcc/console.log.xz | Bin 234632 -> 234392 bytes 06-build_abe-linux/console.log.xz | Bin 8948 -> 8428 bytes 07-build_abe-glibc/console.log.xz | Bin 237496 -> 235732 bytes 08-build_abe-gdb/console.log.xz | Bin 51832 -> 51668 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2268 -> 2280 bytes 11-check_regression/console.log.xz | Bin 10364 -> 11272 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 35 +- 11-check_regression/mail-body.txt | 185 ++-- 11-check_regression/results.compare | 108 +- 11-check_regression/results.compare2 | 1300 +++++++++++++++++----- 11-check_regression/results.regressions | 101 +- 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 | 187 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 101 +- sumfiles/gdb.log.xz | Bin 1681668 -> 1806128 bytes sumfiles/gdb.sum | 1804 ++++++++++++++++++++++++++++--- 29 files changed, 2977 insertions(+), 934 deletions(-)