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 3cb5367c98 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards bc298639c3 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards e4e0f96818 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards a1773aae42 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards 1ff67fef10 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards 9559f2d219 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards e660ff79a9 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards b55999e064 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards d5f4f4f8e7 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards b7ae61a36c 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards 763b042108 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 46a51801b1 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards 4f9dbeb122 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 38ee423f04 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards c8a1ee09b2 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards 1d9a0fdef2 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 66453b40e4 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards d712070185 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards f956b45f04 122: onsuccess: #909: 1: Success after linux: 2753 commits discards e3827a02a2 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 615a084a0a 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 6d024a73d4 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards ba6f68e57c 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards e5018f8995 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards 8d596e252c 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards 11b7b16566 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards b873b00094 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards c6cf2a1c06 113: onsuccess: #898: 1: Success after linux: 3 commits discards f4c9d21066 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 8e1c9a299b 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards bbad15e66e 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 054465f844 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards 993406c98b 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards a3077c633d 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards 51e1f1d96f 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards d3bc6c359a 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards cf7217bbd5 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 9157dd2a4d 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards f693008436 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards bff8e5b49d 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards d1b50a0aec 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 449b4d8736 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 4908c122c2 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards 86562f4e35 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards fe0aed2018 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 03e38b4dca 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards c1a1120d09 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 7e106e6ae9 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 4696f9d650 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards ff92f8f6f8 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 93f03f14a5 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 348b74cc2e 89: onsuccess: #864: 1: Success after binutils: 25 commits discards f91da11fb3 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards ef065fab3a 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards d24dd31f17 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards 2b64aa0240 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards 660d6d2838 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 5e32c14897 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards c3d6ab7124 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 2335536ba4 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards d481bfdfb0 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 8c46abb9af 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards 3f220486ed 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards ce505cf04b 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 8857228dfa 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 8f78dfb536 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards f04fab091c 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards a8fc589079 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 64bbfe2024 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 186cfc9972 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 1c8bc9a03c 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards 1c774a1552 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards eb36c6ee9a 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards dcff8e252c 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 6b9ae2968f 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards f74822e3f5 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards aab01c9bac 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 4c15b9c490 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 346342699c 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 7b39a4df3f 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 64b0983523 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards d01a411999 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards 635cd90aa4 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards 30d9a7ed37 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards 964f7a5f71 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 8651568c7a 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 6fd5e737e5 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards b85b13a1ab 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards bca27792d4 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards ac6072180f 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards fb9de554b4 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards f0cddc0b0c 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards f625579334 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards af22b80f43 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 0c05be067a 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 9e438753c2 45: onsuccess: #815: 1: Success after binutils: 6 commits discards ab0359234d 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 4bc5274cca 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] discards 909c33f399 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 03a10ca83d 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] discards 8f5c21241f 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] new 9df91e36a4 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] new 778306bad9 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] new a2cff50d78 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 1ddda772c1 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new bd5cbdbd0d 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 879744cd8d 45: onsuccess: #815: 1: Success after binutils: 6 commits new 94d8eea2b1 46: onsuccess: #818: 1: Success after binutils: 10 commits new 77dd1c191e 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 3fd66cd31f 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 3a3d798a42 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 2db51156f9 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new da643950c1 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 80ce888d73 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new b43216c40d 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 1a2cb55e07 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 95cc18222a 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new a0dad0056f 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new be724a86ab 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new d9913a7d62 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new c5e9779eef 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 2fbf299aaa 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 7f37bbf944 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 4c762952a5 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 06852e8fd6 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new f297875f2a 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new 00cefc679a 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 59b2f9b926 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new dff7732110 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new fa33a39d31 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new cf8648424b 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new fa9ac4674d 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new 972e05a721 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 6ed08fa9f9 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 0dca6f35fc 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new b11a2815cc 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 8d66b2ab97 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 526d3f56be 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 26cf9acc5d 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new ee651a1d33 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 708c6bc208 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new 7571129d16 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new add0f0cdf5 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 304207814b 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new 68a39643a7 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new ffa259e045 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new b86e180536 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 0d6c6b4c67 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new 066a5b9fe6 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 98d5fd9224 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 6018c57543 89: onsuccess: #864: 1: Success after binutils: 25 commits new f702c02fa7 90: onsuccess: #867: 1: Success after binutils: 4 commits new 4f8c6d0a6d 91: onsuccess: #870: 1: Success after binutils: 5 commits new a6d42ff9b7 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 5386e51eee 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 058bf3c26b 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 2fc434cc74 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new b94a065342 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 540478dd55 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new b7c3fcb273 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new e542ce1061 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 668c2cf3b5 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 592f93b133 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 534becb22c 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 25ee8313d4 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new 276ee3da04 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 5a311c2b4a 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 31f239d3bc 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new dad5433a0d 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new f75a67be89 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 64c5a0b2d7 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 096b6194c1 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 9928009691 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new ed627e978e 112: onsuccess: #896: 1: Success after binutils: 24 commits new 840779a306 113: onsuccess: #898: 1: Success after linux: 3 commits new f42ab7acc4 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new 468da1ea7e 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new c4a99fc49c 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new b3b15f8af3 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new 139a158226 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new f6899e7edd 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new 6f670d7656 120: onsuccess: #906: 1: Success after binutils: 29 commits new 6f581fb281 121: onsuccess: #908: 1: Success after glibc: 2 commits new fefb6331c3 122: onsuccess: #909: 1: Success after linux: 2753 commits new f907804fea 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new fa57e73d6e 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new b3c6d838e4 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new c5aa3e2613 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 2fbc285bf5 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new a617d94db0 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 7c7edfbf11 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new e359c87472 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new b8ca54a115 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new 505f871e01 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new 5ffaa273f6 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new f75c5e2c13 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new 041165f30a 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new 502be231f2 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new a393bb6b8c 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new 30fec44d37 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new 6c8c759f7e 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new 209f35c60d 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new 86e5368409 141: onsuccess: #928: 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 (3cb5367c98) \ 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 1760 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 39856 -> 40740 bytes 04-build_abe-gcc/console.log.xz | Bin 214304 -> 216528 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8992 -> 8696 bytes 07-build_abe-glibc/console.log.xz | Bin 244936 -> 244832 bytes 08-build_abe-gdb/console.log.xz | Bin 39592 -> 39280 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3852 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2036 -> 2036 bytes 11-check_regression/console.log.xz | Bin 13940 -> 14992 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 47 +- 11-check_regression/mail-body.txt | 172 +- 11-check_regression/results.compare | 82 +- 11-check_regression/results.compare2 | 3465 +++++++------- 11-check_regression/results.regressions | 82 +- 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 | 174 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 82 +- sumfiles/gdb.log.xz | Bin 1903172 -> 1930128 bytes sumfiles/gdb.sum | 7772 ++++++++++++++++--------------- 30 files changed, 6093 insertions(+), 5869 deletions(-)