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 b783bb29909 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards b640a6f5a84 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 4b10fc542c2 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards a769e779599 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 2bff7ea3b4c 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 03e18a364eb 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards fa6cc66b2b7 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards aa275fb8129 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards e309ba43b91 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 56da7724393 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] discards 73eb5c691f9 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] discards 81e1cedcf1b 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] discards 91a521cc1b6 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] discards 814bbfd6577 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] discards 7611195a4a4 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] discards 9fb7dafae56 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] discards 0e6d3fa84d1 91: onsuccess: #870: 1: Success after binutils: 5 commits discards bf7847a0571 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 471f71fe3c3 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 01a6f6a6157 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] discards ca0ed74c47c 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] discards 44463a661ca 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] discards b37d67ff1a5 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] discards 6b0476a72cf 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] discards b4fb8fa5931 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] discards 59cc4fe4089 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] discards 313c0bc66df 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 903dd4fbd75 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 685ed993ab3 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 3d5ecbe4d77 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] discards 9c4f01bb852 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] discards 5959de1333b 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] discards a53eacd2198 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] discards 68e83a3ccf3 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] discards d634edc3487 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] discards 9f7d5e1790c 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] discards b756b850b2d 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] discards 4194ed6f8da 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] discards 828723d4b4e 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] discards 1c9ea48226b 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards ecd880d9244 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] discards 535592bf9e7 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] discards eb65861598e 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 505f883892a 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] discards 754ce92ba4c 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] discards 42cc43f4186 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] discards 5070d144e9d 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] discards 0fc3d7a3f5d 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] discards 3dd576168b1 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] discards 479e8412168 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] discards b291fc1e755 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] discards deb945a0772 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 5d4515b504a 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 30558656b24 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 94604a760d4 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 312c2e70900 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 48b5fd63b36 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards a80c1214da1 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] discards ee4602f52d5 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards ab05792c582 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 7095f1930d6 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 17b4ccbfc66 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 0c53adc8f69 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 636427ebc99 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 76549875b18 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] discards 2267ec191dc 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 7227df74820 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] discards 72cdc55e4dc 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] discards ea77e5ca0fe 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards ed38a9a0dc5 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] discards c84d83c352d 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] discards 5a8b25cdc09 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] discards 28e5ab9b12f 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 9b75e05df0c 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] discards e504378141b 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards b273ed8bc7e 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards ebb3443c3fd 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] discards b489a3b36c2 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 314fe13ca4d 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] discards 22216f28752 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards abd9997b9bb 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] discards deabb5d7116 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] discards 23456b06dbe 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards ab01f4cddb8 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards ea14dc32d2f 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] discards bff4f5c6926 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] discards b29aa21fd70 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] discards d680f54bc6a 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards cc424f90943 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 6e2d82c28af 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 022194a7306 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 0d043b72d0b 16: onsuccess: 1: Successful build after binutils/gcc/glibc [...] discards d4a559f2942 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 4bca88925a5 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 2580d3129c4 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 4ad987d3ad7 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 13043022546 11: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 136c3513276 10: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 7777547defa 9: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4de03b3819c 8: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d2caa214e39 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new f2b46242dc1 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 6adf561555d 8: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 05e36a3a7c6 9: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 669b43737de 10: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 25a98c17e31 11: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 875c0c9a1b4 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 92febf28b36 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 2d3bc82a411 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new f635cf163a1 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new f01a1481290 16: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new 4afdfc69e0a 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 9047bfb392a 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new d9942448382 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new dd39e607bd0 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new d45d57129bc 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] new 157b38aec53 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] new 506e3356611 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] new a87f289d142 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 3bc84502cc1 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 3e664e59fc2 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] new c28297bf811 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] new 655eee17618 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 69ce0c7d33c 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] new bbde7e309c0 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new cd4f354a888 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] new 4d9b9c91cb9 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new ac81414b15c 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 0fa04323b8c 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] new ff30f395d59 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new b91738ae7af 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] new 035747ec9f8 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] new 4be997e57a5 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] new ebfd75fb6f3 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 70aa9c04116 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] new fecefe96d2d 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] new 035d3ff0cb1 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new fbb5c2408dc 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] new ee7eb8bc489 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 9d2228c03b8 45: onsuccess: #815: 1: Success after binutils: 6 commits new 0c43d24b899 46: onsuccess: #818: 1: Success after binutils: 10 commits new cb59db10aa1 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new be1f6b9595e 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 7778b31f3ef 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 3b90dbc510d 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] new 0ed2cc7f1bf 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new b94c70003ea 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 9e28044c91d 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 4257f166c70 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 8154077931c 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 226e69ad3d4 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 4e8e8f4ecb7 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] new 0a703d22b94 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] new b29b448e8ff 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] new 998c525c029 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] new ff20eb5abf5 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] new ed8bec921b4 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] new e69cd2f2e88 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] new 665b5280991 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] new 76afea8bd1e 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new c044e587eab 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] new 24eb8358cd0 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] new 79f57d92e93 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 99fdd99a021 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] new 7a400e26c0d 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] new 3c2404e9fc5 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] new 79f90493d26 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] new 61c195737d2 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] new 94d201bafe7 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] new 652723c6116 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] new 22215c4722e 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] new dacd5ac69bf 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] new b90813fdd5a 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] new 62ce0d0fc3f 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new cdf3497171f 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 345887f98b2 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 24bf2a16896 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] new 71f4ef31f0e 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] new 12df62a6c84 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] new fc974256542 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] new f057e78ff06 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] new 30dfa599c35 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] new bcd4926b3e1 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] new 3234d0b01f4 89: onsuccess: #864: 1: Success after binutils: 25 commits new b957f7583d6 90: onsuccess: #867: 1: Success after binutils: 4 commits new 2cd725acbfe 91: onsuccess: #870: 1: Success after binutils: 5 commits new e5bbd8971d4 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] new e39ecbfa81e 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] new f3f7747bac7 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] new 9cb1c9dffe0 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] new 5f71a0c023e 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] new 54952b51d40 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] new 6ddb43a3413 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new 182ea5ec9fa 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new a2233a0d33d 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 5ec35146a95 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 58aff58d46d 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 479403ce7b1 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 82c0173921f 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new b52ca505526 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 9773f9329c4 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 52fc1919e7c 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 90ded0a9a29 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...]
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 (b783bb29909) \ 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 1692 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 40100 -> 38936 bytes 04-build_abe-gcc/console.log.xz | Bin 213100 -> 213400 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8560 -> 8768 bytes 07-build_abe-glibc/console.log.xz | Bin 244296 -> 244892 bytes 08-build_abe-gdb/console.log.xz | Bin 38532 -> 38708 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3840 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2032 -> 2020 bytes 11-check_regression/console.log.xz | Bin 13276 -> 13936 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 55 +- 11-check_regression/mail-body.txt | 186 +- 11-check_regression/results.compare | 94 +- 11-check_regression/results.compare2 | 546 ++- 11-check_regression/results.regressions | 94 +- 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 | 188 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 94 +- sumfiles/gdb.log.xz | Bin 1886188 -> 1936228 bytes sumfiles/gdb.sum | 7715 ++++++++++++++++++++++--------- 30 files changed, 6278 insertions(+), 2784 deletions(-)