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 3a4ba3286d 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards 565ed408f9 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards 358415b291 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards 76ca7ae149 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards 096e3364c1 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards e04a25c24d 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards 321ca7dce3 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards 89e8142a2a 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards 82e863b267 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards c1f38a25ad 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards ca1be3d808 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards ba3ffaf26d 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards 59b58f2458 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards aa45f46948 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards 4fb4a4ccde 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards 6c1406bdad 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards d53245db61 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards 50a7e43746 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards dc2f557f9e 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards 93fc55dc3f 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards c29b7c1387 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards 2f72f67ce7 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards c959474c10 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards d45cd934ba 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards aac8d4ded8 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards 3881b33829 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards 713f075059 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards 3bd0b2f9e9 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards 495f5ce3c0 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards 9a880d6754 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards b93e0ec421 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards ea30d2e851 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards 116f00f03c 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards 3345dad698 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards 8be9365a6e 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards 74bcd6ec58 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards 053fb47850 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards 5912e1bfed 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards 12d2394e2d 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards 46e93da1cc 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards a559700e4e 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 7fcf16fa7f 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards d96545cd2c 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 9a7549f65e 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards 5afb1b897d 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards 2ad891f9e7 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards bf7b2c67e6 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards 43c7e387c7 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 8fec4a5fe4 122: onsuccess: #909: 1: Success after linux: 2753 commits discards cea5bb2510 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 1b736a3f91 120: onsuccess: #906: 1: Success after binutils: 29 commits discards d81386facb 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards 1f168f8b71 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards 522bd830d1 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards 0648bbdec6 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards 59ef81e4ae 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards 5dafb6c11f 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards 68f4912e5e 113: onsuccess: #898: 1: Success after linux: 3 commits discards eebb324897 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 7fe83776ca 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards 58bf2aa830 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards b7fff3e916 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards 92ad5e4a3f 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 359bbdbb1d 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards 2665b55eaa 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 33aaac5e2f 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 618207bb71 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 8bcca0c9ab 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards a6a51b3b8a 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 7447f9cf98 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 17b0fa61b1 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards f59accd4cc 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 6d2a385134 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards b2561ee7ad 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards 520b483b2c 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 2504ca9086 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 806f524c37 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards de4a1ac978 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 255620fff2 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards e23146f17c 91: onsuccess: #870: 1: Success after binutils: 5 commits discards f62540aa3c 90: onsuccess: #867: 1: Success after binutils: 4 commits discards e4789b7dd4 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 8f4b1433e3 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards da085a5ea1 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards f0e1e469ed 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards 5c663949dc 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards ce21ef4674 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards a956263448 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards e07422c0a7 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards e6235b54b1 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards efefe7e519 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 1cde08022b 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards b8d23f4aa4 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 8d9a032e1e 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 0df3843b62 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards cf6273e7c6 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 37cf9381dd 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards ce31cf5b90 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 93592bfa8a 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 71632caffb 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 776c71a9c3 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new d29aab3649 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new baf63f9374 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 8e45cf8318 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 8a349fce16 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new f66d34b5e9 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new da982363a0 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new f2a4b01495 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 6f74782a11 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new b9bacb53e4 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 4891abdbd1 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new fd3ab69275 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 4603c4f4cd 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 4198f254d9 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new b1c7663439 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new ed204a8f47 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new 918bd0b513 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 54807bb6c4 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new 62d3eb47af 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new c9f319d134 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 620a4d9a6a 89: onsuccess: #864: 1: Success after binutils: 25 commits new 208c2e1a33 90: onsuccess: #867: 1: Success after binutils: 4 commits new ad136f1e74 91: onsuccess: #870: 1: Success after binutils: 5 commits new 2bec6111b6 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new b07f453db5 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new b1be9cd75d 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 5f873be54d 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new 07ce3e5573 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new f0542f65c1 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new ee3178ab39 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new c037ff2663 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new a85539a1e2 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 7d0266a307 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 24adb244df 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 8f98462001 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new af96f83d4b 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 7addba83ce 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 8d92983a97 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new e1dab45d2c 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new d108c28582 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new a31c4642a1 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 35ad4cc377 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 913f25bdea 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new 1d8dc159c2 112: onsuccess: #896: 1: Success after binutils: 24 commits new 583a3f6262 113: onsuccess: #898: 1: Success after linux: 3 commits new 2d736bde24 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new c65a62eb09 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new a2baadf393 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new 336ae52467 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new 0c78c7da23 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 7fcc5a95dc 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new 717bb4100a 120: onsuccess: #906: 1: Success after binutils: 29 commits new b72d9f35b4 121: onsuccess: #908: 1: Success after glibc: 2 commits new b920d83ffa 122: onsuccess: #909: 1: Success after linux: 2753 commits new 3ea34c6db1 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new 667ef1db2e 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new b8784513b7 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new 1438d4a4a2 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 5887e9a626 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new be62ee8eb3 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 00c3c336d5 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new f4ab346e6b 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new 4eefa3e271 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new 91c019165f 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new dfdfe6ab83 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new 811a945b8b 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new 18291a296d 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new f8118c5215 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new 676f826649 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new db0f4420de 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new 8a0dad98a8 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new 9d026625df 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new 105737eeb1 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new 4b6b91aaeb 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new 24d2171f86 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 448c1f5262 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new 70579854b3 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new d936a9779b 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 775ad162c7 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new 9bbfc6b89f 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new f9cd5e9de1 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new e0482a6222 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new e3d65a7304 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new c7cb81bc87 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 73b7a567d4 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new 5a971abafc 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new d6182b087f 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new c11350b760 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new b4329c0c2b 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new c5aa6f8178 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 4a30fcea8d 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new c00809500f 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new 15d72a0d24 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 3a6013ad33 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new fea8394455 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new ab440dd6a6 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new fed1c7b92e 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new c36dec4b99 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new d4137ef51c 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new db5ee4c1f8 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new 85d3dab980 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new 689a2771e8 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new e1b124fdf9 171: onsuccess: #964: 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 (3a4ba3286d) \ 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 1764 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 38748 -> 39840 bytes 04-build_abe-gcc/console.log.xz | Bin 213556 -> 214660 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8520 -> 8652 bytes 07-build_abe-glibc/console.log.xz | Bin 244004 -> 244548 bytes 08-build_abe-gdb/console.log.xz | Bin 38528 -> 39676 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3840 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2140 -> 3324 bytes 11-check_regression/console.log.xz | Bin 9264 -> 9088 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 41 +- 11-check_regression/mail-body.txt | 165 +- 11-check_regression/results.compare | 84 +- 11-check_regression/results.compare2 | 575 ++-- 11-check_regression/results.regressions | 84 +- 12-update_baseline/console.log | 30 +- 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 | 167 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 84 +- sumfiles/gdb.log.xz | Bin 1986104 -> 2000192 bytes sumfiles/gdb.sum | 4651 +++++++++++++++---------------- 31 files changed, 2792 insertions(+), 3145 deletions(-)