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 166cb04685 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards 9b90f8e402 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards 9df782cb70 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards f563847f64 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards 15a96a2046 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 947d6d8189 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards a170934fc9 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards 1f93cc48e2 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards 97d8290c12 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards e65836e2c1 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards fcab80cf52 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards faf24dd2a7 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards df356a2192 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards 8aab6f1991 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards fa28e07243 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards d1f47aa94a 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards 1af23b2088 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards 0c6087b9b8 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards 4f629221e7 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards 17ea06a09b 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards a083f028a0 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards 5d8ebda583 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards f09e6a685d 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards 70ac3ca5c3 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards 3f7438b70d 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards 4f8ddf7765 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards b303d633cf 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards 26fd568d3e 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards 699cce0dc8 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards 413be06c56 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards bffb2337c9 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards 34d7c3e793 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards 94ff64c50a 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 98462306f1 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards db5998feb1 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards df5c5fec6f 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards ce092523e9 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards 8c1045154f 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 46d944db7a 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards 7cd2c908a8 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 62089d3629 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 6c8abcc84f 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 9e22412863 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 493dbe0987 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards 6c0bf1287d 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards 83a675ade6 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards 5a808b3124 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards 08ec0609e6 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards 13c102b8f3 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards f902d30785 113: onsuccess: #898: 1: Success after linux: 3 commits discards ef0de8f22c 112: onsuccess: #896: 1: Success after binutils: 24 commits discards fc39ac8e97 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards f9d1bf6406 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 63da88ce12 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards 6beba94a6d 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 2a839a95d5 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards 173d699406 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards e65ac79481 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 1fdf32015f 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 8efe2cf1dd 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards 47c1c3237c 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 5cb8575bea 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards f100ce5977 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 7f5bfb23ef 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards c0327ec99d 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards c61628c7f9 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards 79ab61c8e0 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 73f509bfea 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 0ea96aab8b 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards c35b8a0c67 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards b3f5e33d4c 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 574770347d 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 8d212f6a1e 90: onsuccess: #867: 1: Success after binutils: 4 commits discards b28088c88d 89: onsuccess: #864: 1: Success after binutils: 25 commits discards c62f78d9e3 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards ba5703907c 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 4d1fec7a3f 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards f9b32b2c8a 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards 13a545957a 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 3ab70b798b 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards cca8d2454c 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 03e930e865 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards 7b1b1110c5 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards c21766d941 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards a4af1a5f0a 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 2d0ae8858f 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 5c69f5ed4f 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 4d28d4ae12 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 6d00e6f836 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 84fe11a8d2 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 49cc863fbf 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 7feb27dd61 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 2a6ce70eff 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards 8ebc933c9a 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards 2278852f16 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards bceb17ea4b 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards df5d68497e 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards a28eb47d96 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 32cb4cb9af 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 8f1ef9f283 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards eeb06a907d 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 7dc34b50ec 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 17bcaf4e13 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 022daef032 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new 874d34c603 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new ca4b89ec10 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new 8ba01e46d1 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new e52ccb4650 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new 3172656104 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 6901a597d2 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new c0a21d9b7a 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new b009670786 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new fbb6696782 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new 2fc8318365 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 55767f6f18 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 39510ea213 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 07c296d57e 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 87c6063c57 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 2c10c34898 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new 5b85054348 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 2676d5ac2a 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new b2cc7d92b4 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new af0e871e82 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new 064c18cb6f 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new d3081c6f86 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new a294260330 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new f83961d929 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 009c4f24d8 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new fd7b85f708 89: onsuccess: #864: 1: Success after binutils: 25 commits new 2e5f6b08c0 90: onsuccess: #867: 1: Success after binutils: 4 commits new e3ff26b942 91: onsuccess: #870: 1: Success after binutils: 5 commits new 9f8f758e7e 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 4b02bb909a 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new ab32fd11fc 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new a38d413fa5 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new 747a5e28f1 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 1bdf7d2a90 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new b40e1437a3 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new efb3a95f78 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new aa34a68765 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new f8409e3de1 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new ab5d413383 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 31f4f80b2f 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new f33c0b9c74 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new b4ee71a67c 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 42e8c6fac3 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new d6517958b6 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new 4d021fff7f 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 0dc9fc4f29 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 4dc6eb8fa6 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new c5926d3831 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new 5c5f23ac5f 112: onsuccess: #896: 1: Success after binutils: 24 commits new 97b0d4c79a 113: onsuccess: #898: 1: Success after linux: 3 commits new 64adc935ae 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new 4a3d5fa09d 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new 7eb264cba5 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new 1748ae7a4d 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new cd99a130f2 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 3bf29e4e1e 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new 64b2371371 120: onsuccess: #906: 1: Success after binutils: 29 commits new 594f426b6e 121: onsuccess: #908: 1: Success after glibc: 2 commits new 440d4e9a21 122: onsuccess: #909: 1: Success after linux: 2753 commits new a6888c845f 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new d4e6ef8993 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new 3a4c0911a8 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new 0e348e58d9 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new e83d100747 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 0bda1346f2 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 74c99ffa26 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new 0ad3b3bec4 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new f7078a792d 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new 401c9b34d6 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new b6a03c38b0 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new 6efac65da7 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new 21a211c106 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new fb96fc1979 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new 839bf05504 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new 60d1f4b02f 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new f6f0496d9a 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new 424655850d 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new 559f871ecb 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new 5d032450de 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new aa94402dd9 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 00930c9ee8 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new 0274c78f62 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new bd01dece88 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 340167ae00 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new e6c93d8903 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new a47bcc2d39 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new 9c5128a8f2 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new 55e6771741 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 990f6f0deb 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new a136a4a150 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new bcbf67fc09 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 3def5f6f2f 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new 38897a7adf 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new cdf6b21159 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new bda2e79d3e 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 79f967cc5c 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new 8300b255b3 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new 57c45e5b49 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 8efc53b1f0 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new 17315082a2 163: onsuccess: #956: 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 (166cb04685) \ 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 1948 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39148 -> 39008 bytes 04-build_abe-gcc/console.log.xz | Bin 215980 -> 213196 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8564 -> 8328 bytes 07-build_abe-glibc/console.log.xz | Bin 246936 -> 244508 bytes 08-build_abe-gdb/console.log.xz | Bin 38692 -> 39044 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3852 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2128 -> 2032 bytes 11-check_regression/console.log.xz | Bin 20300 -> 22372 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 33 +- 11-check_regression/mail-body.txt | 161 +- 11-check_regression/results.compare | 78 +- 11-check_regression/results.compare2 | 2287 ++++-- 11-check_regression/results.regressions | 78 +- 12-update_baseline/console.log | 44 +- 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 | 163 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 78 +- sumfiles/gdb.log.xz | Bin 2001804 -> 1855568 bytes sumfiles/gdb.sum | 11517 ++++++------------------------ 30 files changed, 4220 insertions(+), 10267 deletions(-)