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 1db64a02af 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 5b7b5cc73c 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards dc5e78cb99 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 7bff75c2c3 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards ce979a325d 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 22247ffede 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 2a2a53494f 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 3ce1638fb5 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 1aca64c9eb 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 4f142a7956 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 3357bee18b 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 938c0d94ab 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 4f420a60bc 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 7851e66b47 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 4cb80171ac 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards f3802c3136 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards a684c298e2 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 3ccfbd1509 92: onsuccess: #575: 1: Success after linux: 34 commits discards f090e05c55 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 3ba3513f0e 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 4c9610c6f2 89: onsuccess: #570: 1: Success after linux: 11 commits discards 1ff95332fd 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 06e4151a31 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 3fdff7de0e 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards e1adc67761 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards a54836e705 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards e54c5965c8 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 30feb48159 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards b764b18091 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 64aa0eff37 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards be54025432 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 3a72da97cf 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards e069523b1d 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards cf405d861d 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 9a15afda29 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards c64a2bc467 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 3675f85b4c 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 19b439838d 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards e61af1e346 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 04a96fde0d 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 381ac54d34 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards d25cdb621a 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards cf7d2a634b 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards e51b519ebd 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 9d50b8cb04 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards bd67b66e82 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 243437c8f8 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 58a77e215b 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards e86747475d 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 54dc7260d9 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards f0bd63a404 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards f4cfb86f7d 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards bed488e230 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards 97cc6990e7 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards fbe9814725 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 228c054662 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards b4f589b3a9 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 8846d48533 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 0b5978d88c 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 17ada6ed53 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards e8760df85d 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards 4db44fe2cc 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards 79c607dbb6 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards 16472ff5fc 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 98a5c97c67 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards 8ed26f9507 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards f47dd08111 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards f896b373fc 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards 01c16e7eea 41: onsuccess: #514: 1: Success after linux: 64 commits discards b7ca127724 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] discards bbf2398618 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 69e603fe57 38: onsuccess: #508: 1: Success after binutils: 3 commits discards cbaf8e8df9 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards 7b0937bf56 36: onsuccess: #505: 1: Success after glibc: 3 commits discards a7cdf91d38 35: onsuccess: #503: 1: Success after binutils: 11 commits discards 7cba5ea981 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 807204a254 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] discards 301cab0452 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 38a647b797 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards d9c536e863 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 56833249d0 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 225975314d 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] discards 16a4b71669 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards fe5fdfa37b 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] discards 57aa099be6 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 080c782ca8 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards 793c3b9f00 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 9768167bcd 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 2e02857576 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2ab426bbbb 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3aaf26bc43 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 748ee7127f 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e6611c13a6 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1cef97e362 16: onsuccess: 1: Successful build after binutils: 4 commits discards f84c288d9b 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bfb3591caa 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9c10596442 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b30ad4917b 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 26976d2de2 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 882d06af1b 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8c101959b5 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 383544c3e9 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b1aa44d9d6 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 17412a12af 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b03608a669 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0406d1e369 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c6025458f5 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4bc2a77155 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b918d8b9fe 16: onsuccess: 1: Successful build after binutils: 4 commits new 91b969a547 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 415d0f09e9 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f2fd2141bb 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ba3f5b4dd1 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0ba7a0c908 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 91b35e5c13 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new d9f790fcda 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new ff7a659082 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 1f9543003d 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 5a5dda1a0f 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] new b881389c6f 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 6b93d54e47 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] new e8ee9b0fa4 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new ba592ce233 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new c54bccf383 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 1b67bd6dde 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new e087290132 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] new dfc9fe24d2 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new d977bd1b1b 35: onsuccess: #503: 1: Success after binutils: 11 commits new 9c1e0c60a3 36: onsuccess: #505: 1: Success after glibc: 3 commits new 95ce16248f 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] new eaccc989b8 38: onsuccess: #508: 1: Success after binutils: 3 commits new d7c1276a26 39: onsuccess: #511: 1: Success after binutils: 8 commits new 2b57ee9a32 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new bbd7decf85 41: onsuccess: #514: 1: Success after linux: 64 commits new 30bd2bf4da 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new 59beaf5503 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 12fb5600f8 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new afb52b33fc 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new 48abc8928d 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new c4a3344285 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new f3eeee8d2d 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new fdf2d46cfd 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new bafb63c741 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new d645c9dfb1 51: onsuccess: #525: 1: Success after binutils: 8 commits new a1209fd78a 52: onsuccess: #528: 1: Success after binutils: 8 commits new b70f641e51 53: onsuccess: #531: 1: Success after binutils: 12 commits new d85ea5160c 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new e7599ba8ab 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 0e716356ef 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 060651ef69 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 4a00c19c6a 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 216cbdf4a7 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 846efb816e 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new efa8b13e6b 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 0c3f61bfe7 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 66f03b681e 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 6de3c1d820 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new d278fc6bff 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 476015a6f4 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 82ef83415f 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 4f14e4b900 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new e389f41ff4 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new c3d329262c 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 8645036adc 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 5d1b0b7873 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 029f20e4f5 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 3ef87d0334 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new fd7f4e035e 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 3b1cdd16f7 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 52e2f3b25f 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new c3feea65b9 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 882447bf62 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new c5fa724f56 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 592b5b350d 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new a5883c40e8 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 035c4488a3 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 3a0b11ac03 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new a991b79a69 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new ecff13d3a7 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 65b9a21bdb 87: onsuccess: #567: 1: Success after binutils: 8 commits new f6331971a3 88: onsuccess: #569: 1: Success after glibc: 10 commits new cef83e7fec 89: onsuccess: #570: 1: Success after linux: 11 commits new 199299aafd 90: onsuccess: #572: 1: Success after binutils: 15 commits new bb4694c132 91: onsuccess: #574: 1: Success after glibc: 3 commits new 8d77db6a72 92: onsuccess: #575: 1: Success after linux: 34 commits new d2b17d66fb 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 4bd2792fce 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 027410a90e 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 2b3672fe5c 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 94421aba98 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 37b007eaa6 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 3e4bbe4174 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 950c4279f1 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new d3edc10c38 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new eadea46d36 102: onsuccess: #586: 1: Success after binutils: 5 commits new 6a1eae0c85 103: onsuccess: #589: 1: Success after binutils: 3 commits new 66c9852a99 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 571a23d9e2 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 36e1f562e7 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 3ce19ad71f 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 864bf7ea7d 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 7c04fbb629 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 59d96d01f1 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...]
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 (1db64a02af) \ 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 1680 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 53764 -> 54272 bytes 04-build_abe-gcc/console.log.xz | Bin 237608 -> 236900 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8648 -> 8380 bytes 07-build_abe-glibc/console.log.xz | Bin 235828 -> 235784 bytes 08-build_abe-gdb/console.log.xz | Bin 52356 -> 52052 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3824 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2580 -> 2404 bytes 11-check_regression/console.log.xz | Bin 10332 -> 17288 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 24 +- 11-check_regression/mail-body.txt | 182 +- 11-check_regression/results.compare | 60 +- 11-check_regression/results.compare2 | 3013 +++++++++- 11-check_regression/results.regressions | 60 +- 12-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 184 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 60 +- sumfiles/gdb.log.xz | Bin 1785968 -> 1689220 bytes sumfiles/gdb.sum | 9621 +++++++++---------------------- 31 files changed, 5797 insertions(+), 7501 deletions(-)