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 b7634efd00 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards c59f30f585 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards 19838cdbbe 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards 43a58b45d4 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards 4351e8b02e 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards 31f717e783 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards c91be79af9 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards d2ee614d83 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards 3a4bdcf420 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards 0c6a0a0aac 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 2e98934e06 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards 84a211ccd1 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 6c1ed05953 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards 0b22dd4935 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards 019289c39e 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards b0a0a5a8b0 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards f804bc508e 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 24f97a0f1e 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 7aaa1c4061 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 1f1bf04a9b 120: onsuccess: #906: 1: Success after binutils: 29 commits discards fde0c1555d 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards 05ec2c33ae 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards b97f166b77 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards 0852153e47 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards 7f67c718d3 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards 6608b7e69f 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards 5746e7da6e 113: onsuccess: #898: 1: Success after linux: 3 commits discards c7063cacef 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 795ad2a077 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards 33d7fb9d20 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards e5ec19d117 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards d17ce9be16 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards bf1aa7e42f 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards b150378612 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 4db64d2c84 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards ea597c86e6 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 51a4ca9710 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards 330f8e0436 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 59a96e4a91 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards acb77c1fb2 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 8cb4956232 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 1330514fdf 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards 422de3bf1d 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards 280df4aa36 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 5890b61c15 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 2e756f994e 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards cacb22bdce 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 882cf21681 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 4cbfa3f594 91: onsuccess: #870: 1: Success after binutils: 5 commits discards d8bce3dc7b 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 4c918596e2 89: onsuccess: #864: 1: Success after binutils: 25 commits discards ee3e0cecd4 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards fe123c7578 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards d1f244b735 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards d23422872b 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards d147f1dd12 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 7fd0e6b7d4 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards a00f0f871e 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards e340e72258 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards 4dbcb2a840 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 66a153b83b 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards efc3b81e5e 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 2ce51e25be 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 390338cb61 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 0e0d7950f8 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 076c071756 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 718b1e4f2c 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 81a17e070c 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards d7858fbedb 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 2a36d2dcc2 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards 555aec250b 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards 01689beba1 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards ab269f3970 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 41b920a496 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards d66a4f02a2 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards edd7b8588f 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards f21ad3bb19 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 7bc170527b 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards cf9214e68e 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 65a0d97b22 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards 07e4cab27f 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards 0af751d60e 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards 1ca8f672c1 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards 2eae3bafdb 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 505d0b4228 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 39702c447c 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 6a9b0f2c61 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards fda083ab4f 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 2d66395dc6 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards ff8babba1c 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards cbb3bc4280 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 0b23cc3e8a 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 251a721a9c 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards bb2e658899 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 1a434dd6ce 45: onsuccess: #815: 1: Success after binutils: 6 commits discards bc361893be 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 516040f15a 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] discards f9949838e2 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards d4838d98fe 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] discards f4c81f0547 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] discards 88bc4a20a8 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 86ae334878 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 8f5c21241f 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] new 03a10ca83d 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] new 909c33f399 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 4bc5274cca 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new ab0359234d 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 9e438753c2 45: onsuccess: #815: 1: Success after binutils: 6 commits new 0c05be067a 46: onsuccess: #818: 1: Success after binutils: 10 commits new af22b80f43 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new f625579334 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new f0cddc0b0c 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new fb9de554b4 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new ac6072180f 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new bca27792d4 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new b85b13a1ab 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 6fd5e737e5 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 8651568c7a 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 964f7a5f71 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 30d9a7ed37 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new 635cd90aa4 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new d01a411999 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 64b0983523 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 7b39a4df3f 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 346342699c 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 4c15b9c490 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new aab01c9bac 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new f74822e3f5 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 6b9ae2968f 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new dcff8e252c 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new eb36c6ee9a 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new 1c774a1552 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 1c8bc9a03c 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new 186cfc9972 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 64bbfe2024 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new a8fc589079 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new f04fab091c 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 8f78dfb536 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 8857228dfa 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new ce505cf04b 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 3f220486ed 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 8c46abb9af 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new d481bfdfb0 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 2335536ba4 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new c3d6ab7124 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new 5e32c14897 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new 660d6d2838 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new 2b64aa0240 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new d24dd31f17 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new ef065fab3a 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new f91da11fb3 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 348b74cc2e 89: onsuccess: #864: 1: Success after binutils: 25 commits new 93f03f14a5 90: onsuccess: #867: 1: Success after binutils: 4 commits new ff92f8f6f8 91: onsuccess: #870: 1: Success after binutils: 5 commits new 4696f9d650 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 7e106e6ae9 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new c1a1120d09 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 03e38b4dca 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new fe0aed2018 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 86562f4e35 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new 4908c122c2 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 449b4d8736 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new d1b50a0aec 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new bff8e5b49d 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new f693008436 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 9157dd2a4d 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new cf7217bbd5 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new d3bc6c359a 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 51e1f1d96f 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new a3077c633d 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new 993406c98b 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 054465f844 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new bbad15e66e 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 8e1c9a299b 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new f4c9d21066 112: onsuccess: #896: 1: Success after binutils: 24 commits new c6cf2a1c06 113: onsuccess: #898: 1: Success after linux: 3 commits new b873b00094 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new 11b7b16566 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new 8d596e252c 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new e5018f8995 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new ba6f68e57c 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 6d024a73d4 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new 615a084a0a 120: onsuccess: #906: 1: Success after binutils: 29 commits new e3827a02a2 121: onsuccess: #908: 1: Success after glibc: 2 commits new f956b45f04 122: onsuccess: #909: 1: Success after linux: 2753 commits new d712070185 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new 66453b40e4 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new 1d9a0fdef2 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new c8a1ee09b2 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 38ee423f04 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 4f9dbeb122 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 46a51801b1 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new 763b042108 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new b7ae61a36c 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new d5f4f4f8e7 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new b55999e064 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new e660ff79a9 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new 9559f2d219 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new 1ff67fef10 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new a1773aae42 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new e4e0f96818 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new bc298639c3 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new 3cb5367c98 140: onsuccess: #927: 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 (b7634efd00) \ 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 1728 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 40112 -> 39856 bytes 04-build_abe-gcc/console.log.xz | Bin 213896 -> 214304 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9188 -> 8992 bytes 07-build_abe-glibc/console.log.xz | Bin 244504 -> 244936 bytes 08-build_abe-gdb/console.log.xz | Bin 39376 -> 39592 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3884 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2032 -> 2036 bytes 11-check_regression/console.log.xz | Bin 10276 -> 13940 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 48 +- 11-check_regression/mail-body.txt | 169 +- 11-check_regression/results.compare | 90 +- 11-check_regression/results.compare2 | 4308 +++++++++++++----- 11-check_regression/results.regressions | 90 +- 12-update_baseline/console.log | 38 +- 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 | 171 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 90 +- sumfiles/gdb.log.xz | Bin 1955372 -> 1903172 bytes sumfiles/gdb.sum | 7510 +++++++++---------------------- 30 files changed, 5827 insertions(+), 6735 deletions(-)