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 08ac843d7a 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards a375945d1a 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards bd9c37956f 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards 2a5dea7260 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 3398ca7d53 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards f51f565068 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards 9864394f5a 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards 6d1753e861 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards 44548eaa21 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards ba7d86a14d 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards 0c53058da5 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards 020c47a0ca 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards ae02ab9d22 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards 5c57843110 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards bdbaa97a1f 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards 65927e0210 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards 259a302bf1 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards c51e439daf 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards 0ec7c6ded7 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards ab5481b564 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards 43f4f62b0a 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards 0ce6c91a5a 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards 2ace7e4fec 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards e31d6f3a43 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards c8ce14c66e 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards a47dfeeb6b 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards 18f56d1d45 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards d1d4654a19 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards 515f0bcc30 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards 601845116c 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards 834a9b17b1 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards da8a113d23 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 8a4e37f68a 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards e8a17a145d 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards ef4b3b8798 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards 5a1c186093 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards 6d51ceb0d3 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 38a4763e40 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards 8a027479ad 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards b781db7cf5 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 29971eacde 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 16594c051c 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 15a3fb1424 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards cc308fe9b9 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards 2e744d50d0 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards 12eca3cb7b 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards cfcc0a7232 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards 62c6e0efdf 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards 25a920a526 113: onsuccess: #898: 1: Success after linux: 3 commits discards 02d20ad6db 112: onsuccess: #896: 1: Success after binutils: 24 commits discards be290eeae7 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards 0fd777d3a0 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards a47e65b42c 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards 978a8c667f 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards f1734d999e 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards 5a2768f681 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 66669b782f 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 6605b793e4 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 343359ad2b 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards 01e92d0c84 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 9428c6a34d 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 261436c423 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards ee5a9c1052 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 9ec8f60dbb 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards 0ffd679f26 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards ef1fcbe197 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 7c068250a2 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards cb9a531346 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards a5f5911394 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 1faf16ae5d 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 594d177c6d 91: onsuccess: #870: 1: Success after binutils: 5 commits discards ed98c738bd 90: onsuccess: #867: 1: Success after binutils: 4 commits discards b3d70a9c6e 89: onsuccess: #864: 1: Success after binutils: 25 commits discards c740d6c087 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards 58ac4a46c4 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 0731f34ccb 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards 15dafe79c5 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards 3d9d3e455a 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 4ccb34dd33 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards a669a5780b 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 407e300286 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards 8962fbe887 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 4285781179 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards 903e71be1f 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 4e07992e81 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 5dfbae8da5 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards d95c529bb1 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 164f740339 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 620816841e 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards e995b6b659 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 3787ecfcc7 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 63fa8be7fa 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards 599294400c 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards 91d1cfc951 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 7bbd3df293 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 306749d9e4 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards d7a98e3722 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 06fc5f98c7 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 8252dcce0a 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards bea414f4f6 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards def0926c1c 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 4979321966 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new eeb06a907d 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 8f1ef9f283 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 32cb4cb9af 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new a28eb47d96 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new df5d68497e 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new bceb17ea4b 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new 2278852f16 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new 8ebc933c9a 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 2a6ce70eff 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new 7feb27dd61 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 49cc863fbf 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 84fe11a8d2 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new 6d00e6f836 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 4d28d4ae12 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 5c69f5ed4f 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 2d0ae8858f 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new a4af1a5f0a 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new c21766d941 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new 7b1b1110c5 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 03e930e865 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new cca8d2454c 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new 3ab70b798b 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new 13a545957a 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new f9b32b2c8a 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 4d1fec7a3f 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new ba5703907c 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new c62f78d9e3 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new b28088c88d 89: onsuccess: #864: 1: Success after binutils: 25 commits new 8d212f6a1e 90: onsuccess: #867: 1: Success after binutils: 4 commits new 574770347d 91: onsuccess: #870: 1: Success after binutils: 5 commits new b3f5e33d4c 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new c35b8a0c67 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 0ea96aab8b 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 73f509bfea 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new 79ab61c8e0 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new c61628c7f9 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new c0327ec99d 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 7f5bfb23ef 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new f100ce5977 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 5cb8575bea 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 47c1c3237c 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 8efe2cf1dd 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new 1fdf32015f 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new e65ac79481 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 173d699406 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 2a839a95d5 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new 6beba94a6d 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 63da88ce12 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new f9d1bf6406 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new fc39ac8e97 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new ef0de8f22c 112: onsuccess: #896: 1: Success after binutils: 24 commits new f902d30785 113: onsuccess: #898: 1: Success after linux: 3 commits new 13c102b8f3 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new 08ec0609e6 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new 5a808b3124 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new 83a675ade6 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new 6c0bf1287d 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 493dbe0987 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new 9e22412863 120: onsuccess: #906: 1: Success after binutils: 29 commits new 6c8abcc84f 121: onsuccess: #908: 1: Success after glibc: 2 commits new 62089d3629 122: onsuccess: #909: 1: Success after linux: 2753 commits new 7cd2c908a8 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new 46d944db7a 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new 8c1045154f 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new ce092523e9 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new df5c5fec6f 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new db5998feb1 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 98462306f1 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new 94ff64c50a 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new 34d7c3e793 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new bffb2337c9 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new 413be06c56 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new 699cce0dc8 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new 26fd568d3e 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new b303d633cf 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new 4f8ddf7765 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new 3f7438b70d 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new 70ac3ca5c3 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new f09e6a685d 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new 5d8ebda583 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new a083f028a0 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new 17ea06a09b 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 4f629221e7 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new 0c6087b9b8 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new 1af23b2088 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new d1f47aa94a 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new fa28e07243 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new 8aab6f1991 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new df356a2192 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new faf24dd2a7 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new fcab80cf52 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new e65836e2c1 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new 97d8290c12 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 1f93cc48e2 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new a170934fc9 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new 947d6d8189 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new 15a96a2046 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new f563847f64 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new 9df782cb70 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new 9b90f8e402 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 166cb04685 162: onsuccess: #955: 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 (08ac843d7a) \ 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 1776 -> 1948 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 38664 -> 39148 bytes 04-build_abe-gcc/console.log.xz | Bin 214896 -> 215980 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8836 -> 8564 bytes 07-build_abe-glibc/console.log.xz | Bin 244804 -> 246936 bytes 08-build_abe-gdb/console.log.xz | Bin 38368 -> 38692 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3844 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2048 -> 2128 bytes 11-check_regression/console.log.xz | Bin 24076 -> 20300 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 40 +- 11-check_regression/mail-body.txt | 181 +- 11-check_regression/results.compare | 83 +- 11-check_regression/results.compare2 | 4651 ++++++-------- 11-check_regression/results.regressions | 83 +- 12-update_baseline/console.log | 56 +- 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 | 183 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 83 +- sumfiles/gdb.log.xz | Bin 1950080 -> 2001804 bytes sumfiles/gdb.sum | 10307 +++++++++++++++++++++++------- 31 files changed, 10272 insertions(+), 5449 deletions(-)