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 668ba4031a 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards 48972e4794 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards dc8c26ee60 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 1a8da83d40 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 8e5cabc6d0 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards a813ee454d 103: onsuccess: #589: 1: Success after binutils: 3 commits discards fb001163cc 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 70e0aaa658 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 1d95a0b1f7 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards cb26254986 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 89f1d325f9 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 09d7fc3674 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 8b9bb52389 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 929f839c27 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 9e37d22a2a 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards b498f589c8 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards e912af799b 92: onsuccess: #575: 1: Success after linux: 34 commits discards 55b05114cd 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 9b6cbe95f6 90: onsuccess: #572: 1: Success after binutils: 15 commits discards d0374efbc6 89: onsuccess: #570: 1: Success after linux: 11 commits discards 4c0d27f88e 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 2c56672076 87: onsuccess: #567: 1: Success after binutils: 8 commits discards b09efb9075 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 71b477fb8b 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards eba248d942 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 56c2be42c9 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards da52189e18 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards f7263bc448 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 489f47bc01 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 23a2e44bf0 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards d5b1c68dc0 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 0ee12b00b8 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 7c0db87b2a 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 6a9277b000 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 4f9075ccbf 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 4476589738 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards d2bc750403 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 7959fab7d9 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 6811b2353b 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards b9f5146236 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 4aa6da2055 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards e5b09a01b1 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards f37f0006c0 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 57762032cd 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 5d93d24849 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards c592ae3551 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 6fe6103c1a 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards f2da2285a4 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 9bd0b32d6d 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards 1459ee8e2f 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards eb962c875f 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 9e94cad1cf 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards b350f5abe6 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards b96dee6e3a 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 422e84d29a 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards ac7367f427 53: onsuccess: #531: 1: Success after binutils: 12 commits discards ceaec79148 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 480b2a41f2 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 13cc3ea22e 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards b5e8a7f26f 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards 2f294dbc58 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards b121a93594 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards 79d8eac418 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 5da6d10f34 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards be011e853a 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 76dc2b55db 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 0d0f247b1c 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards 2066cba80d 41: onsuccess: #514: 1: Success after linux: 64 commits discards 8e0b9ba28d 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] discards 71ba9f66bc 39: onsuccess: #511: 1: Success after binutils: 8 commits discards fa4de52c0a 38: onsuccess: #508: 1: Success after binutils: 3 commits discards 48bce7cd1d 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards e5fd55e5eb 36: onsuccess: #505: 1: Success after glibc: 3 commits discards cc65699a93 35: onsuccess: #503: 1: Success after binutils: 11 commits discards ae53fc446d 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 9e23ef111b 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] discards 751d16c613 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 1f7a28ac47 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards a0a79c33c5 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards df8a006f6c 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 33c9a812fa 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] discards 0a30f713d8 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 52de82f9db 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] discards 8be5b1effa 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 5b490c5a82 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards b5ed8468c6 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 50eb77d410 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards f81e4f9caa 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 45058311d9 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5a58cd66cc 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7bf6175d66 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c166289066 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b5fa12a764 16: onsuccess: 1: Successful build after binutils: 4 commits discards 5439856d79 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9296b48aa9 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fbeb692901 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9e3940b400 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 713c59108f 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9dd5d35ea3 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 69ed808efa 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 36b95f2a69 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 40fb1bf161 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 8c101959b5 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 882d06af1b 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 26976d2de2 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b30ad4917b 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9c10596442 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bfb3591caa 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f84c288d9b 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1cef97e362 16: onsuccess: 1: Successful build after binutils: 4 commits new e6611c13a6 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 748ee7127f 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3aaf26bc43 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2ab426bbbb 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2e02857576 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9768167bcd 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 793c3b9f00 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 080c782ca8 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 57aa099be6 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new fe5fdfa37b 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] new 16a4b71669 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 225975314d 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] new 56833249d0 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new d9c536e863 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 38a647b797 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 301cab0452 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 807204a254 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] new 7cba5ea981 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new a7cdf91d38 35: onsuccess: #503: 1: Success after binutils: 11 commits new 7b0937bf56 36: onsuccess: #505: 1: Success after glibc: 3 commits new cbaf8e8df9 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 69e603fe57 38: onsuccess: #508: 1: Success after binutils: 3 commits new bbf2398618 39: onsuccess: #511: 1: Success after binutils: 8 commits new b7ca127724 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new 01c16e7eea 41: onsuccess: #514: 1: Success after linux: 64 commits new f896b373fc 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new f47dd08111 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 8ed26f9507 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 98a5c97c67 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new 16472ff5fc 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 79c607dbb6 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new 4db44fe2cc 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new e8760df85d 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 17ada6ed53 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new 0b5978d88c 51: onsuccess: #525: 1: Success after binutils: 8 commits new 8846d48533 52: onsuccess: #528: 1: Success after binutils: 8 commits new b4f589b3a9 53: onsuccess: #531: 1: Success after binutils: 12 commits new 228c054662 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new fbe9814725 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 97cc6990e7 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new bed488e230 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new f4cfb86f7d 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new f0bd63a404 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 54dc7260d9 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new e86747475d 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 58a77e215b 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 243437c8f8 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new bd67b66e82 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 9d50b8cb04 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new e51b519ebd 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new cf7d2a634b 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new d25cdb621a 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 381ac54d34 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 04a96fde0d 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new e61af1e346 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 19b439838d 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 3675f85b4c 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new c64a2bc467 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 9a15afda29 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new cf405d861d 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new e069523b1d 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 3a72da97cf 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new be54025432 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 64aa0eff37 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new b764b18091 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 30feb48159 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new e54c5965c8 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new a54836e705 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new e1adc67761 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 3fdff7de0e 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 06e4151a31 87: onsuccess: #567: 1: Success after binutils: 8 commits new 1ff95332fd 88: onsuccess: #569: 1: Success after glibc: 10 commits new 4c9610c6f2 89: onsuccess: #570: 1: Success after linux: 11 commits new 3ba3513f0e 90: onsuccess: #572: 1: Success after binutils: 15 commits new f090e05c55 91: onsuccess: #574: 1: Success after glibc: 3 commits new 3ccfbd1509 92: onsuccess: #575: 1: Success after linux: 34 commits new a684c298e2 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new f3802c3136 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 4cb80171ac 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 7851e66b47 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 4f420a60bc 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 938c0d94ab 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 3357bee18b 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 4f142a7956 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 1aca64c9eb 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 3ce1638fb5 102: onsuccess: #586: 1: Success after binutils: 5 commits new 2a2a53494f 103: onsuccess: #589: 1: Success after binutils: 3 commits new 22247ffede 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new ce979a325d 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 7bff75c2c3 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new dc5e78cb99 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 5b7b5cc73c 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 1db64a02af 109: onsuccess: #596: 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 (668ba4031a) \ 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 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 53412 -> 53764 bytes 04-build_abe-gcc/console.log.xz | Bin 236148 -> 237608 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8584 -> 8648 bytes 07-build_abe-glibc/console.log.xz | Bin 235844 -> 235828 bytes 08-build_abe-gdb/console.log.xz | Bin 51736 -> 52356 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3884 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2276 -> 2580 bytes 11-check_regression/console.log.xz | Bin 15036 -> 10332 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 111 +- 11-check_regression/mail-body.txt | 190 +- 11-check_regression/results.compare | 162 +- 11-check_regression/results.compare2 | 1196 +----- 11-check_regression/results.regressions | 122 +- 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 | 192 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 122 +- sumfiles/gdb.log.xz | Bin 1790664 -> 1785968 bytes sumfiles/gdb.sum | 6808 +++++++++++++++++++------------ 30 files changed, 4789 insertions(+), 4202 deletions(-)