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 da77b21462 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards c809cecb73 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards 6c82e47f14 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards 508d536562 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards 07edcce430 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards 356504ec36 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards 3087c70da7 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards 754af37281 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards a7870626ff 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards 928b1b34dd 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards a7982744dc 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards 10395eab79 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards 0a295b51f1 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 737df30940 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards 5b42e6b5f7 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 3d9f634f41 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards be0eff5efe 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards ee5aacfcf6 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards db668394e2 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards fb33d50cee 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 411d220cc5 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 3cfef615cd 121: onsuccess: #908: 1: Success after glibc: 2 commits discards e6069108b0 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 19fa823fc7 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards c5291bb2bf 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards 84d808a5d4 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards 689f391848 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards 5a888abd18 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards 4e06d4cf48 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards 71c167d6df 113: onsuccess: #898: 1: Success after linux: 3 commits discards 98e09e4273 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 40401e9c07 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards a0d7a59b8a 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 6323a5b3fa 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards 3df07bdd0a 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards f2b94aa75d 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards 89bf97b7ec 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 6fd8a73a29 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 85614bce11 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 622664c1cb 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards 23f786c579 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 5bb5b921b4 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 6c4460290a 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 876a985277 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 1e1e7fbeb3 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards 45a8c1ce9a 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards ea4b27dff6 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards eeda7e03d1 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards c40cf77d59 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 2e12348fa6 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards c4c23a0ed9 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 2583aeb158 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 4eec281843 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 20eab1c217 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 7e6998dfba 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards caf79758ac 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 59cd1da4f9 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards 0563d06638 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards 824e8337b4 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 9fe8ab811c 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards 423408a4b6 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 305bb428cb 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards 463d0fd152 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 06bdc09c0b 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards f6b7a4b381 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards c811b389a0 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards c953ff5364 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 3c43953ee4 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards ffe2003fa1 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 4415b2d79f 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 9e41d9221d 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 9bb1b61bc6 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 28c613efde 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards cbc9618e71 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards 4ad7335289 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 96cd6c502b 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards c1d5aca205 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards 83b379d88e 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 75fab3ee99 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 51a943283f 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 909053c3a9 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 9e6d22da52 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 54303f234c 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards 8ad860df31 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards e834c926b0 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards 65eaa2ea74 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards 0447bf4853 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards ae9d99c9eb 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 5569ecf55f 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 91bc28461d 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards c7982b3163 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 67ffe562e6 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 4bcc5f9290 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards ad6972bc3b 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 3877160c34 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 601a51cd1b 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 7db1610c5f 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 31f118d5d5 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 0aa8c4b7cd 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 9bb005139f 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] discards 19d0f3657f 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new df10c7733e 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new b773a47d87 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new 58116e4693 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new c3077e7c84 45: onsuccess: #815: 1: Success after binutils: 6 commits new c93515b3da 46: onsuccess: #818: 1: Success after binutils: 10 commits new 1582403214 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 1775a0f458 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 04b717448e 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 9aa90a5a59 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new ac7ef0b577 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 62ba30436c 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 11be73dd32 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 85f5fe61da 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 7f0d7fd131 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new ec43f5d955 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 3eab7dd793 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new e1e90d61a7 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new fffe5abe17 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new beedd6b2e3 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new fb1c3a15bf 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new a6126c5c79 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 012aa721ff 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 52e2a43fcc 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new 5767e3a260 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 5b8284f17c 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new 20b63eb5e4 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new a2831c910c 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new b1468a8555 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 9d7b849a7e 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new f1938cc523 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 7bccad48db 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new a79dd8b20f 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new b4a28522f1 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 198f6d646b 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 840307cafa 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 7d36971db5 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 845c80a851 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 278cca1eca 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new c943836105 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 47082dcfe0 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new f10e15da71 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new d33a80aca0 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new 2609f0d650 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new 3a27746e7c 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new d861f7f6bc 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new 4b07e11584 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 4bb64b6621 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 160427677b 89: onsuccess: #864: 1: Success after binutils: 25 commits new 0ca16ad358 90: onsuccess: #867: 1: Success after binutils: 4 commits new 8a1811dd90 91: onsuccess: #870: 1: Success after binutils: 5 commits new dd847c6805 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new cb3bde1476 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 89d440bd31 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 4619ddb9a8 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new e5e9e8f2b6 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new b9e76d0d77 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new c00ebdff8d 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 148a8a24a3 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 5e9c03fc91 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 7301fa5d8e 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 10a8c1000f 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 6eb1845268 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new 4d089170f9 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 5fdaa6ea01 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new f3422cb5fa 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 032923d343 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new d398c62a2e 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 033ecf65a2 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 2d3987c43a 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new b2d8b08f85 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new 903617817d 112: onsuccess: #896: 1: Success after binutils: 24 commits new 79e10b6fba 113: onsuccess: #898: 1: Success after linux: 3 commits new aafd2358fb 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new 9060ebf013 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new f753118b2e 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new 51755eeedc 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new 76778e274d 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 49920cca41 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new e1ea228eda 120: onsuccess: #906: 1: Success after binutils: 29 commits new bf625bff63 121: onsuccess: #908: 1: Success after glibc: 2 commits new 6a1a6c60e4 122: onsuccess: #909: 1: Success after linux: 2753 commits new c3a4641499 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new 3c85d319bd 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new 6f8a811fa9 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new 28747f43c3 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 1ecfc56df7 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 3432d2d0df 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 855c129d37 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new 89614bd853 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new 2e6624ea34 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new eba58818f0 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new 8f66a4b45d 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new 3c0b389af9 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new 6fe3724ece 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new 0f87fcc601 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new 17b0eb7758 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new 78d197364d 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new e7f228bcc2 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new c9213a36e7 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new 17c8294e70 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new 9389bc42a0 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new ffa457e1f0 143: onsuccess: #931: 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 (da77b21462) \ 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 1752 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 39952 -> 40620 bytes 04-build_abe-gcc/console.log.xz | Bin 215980 -> 213668 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8308 -> 8868 bytes 07-build_abe-glibc/console.log.xz | Bin 244692 -> 244684 bytes 08-build_abe-gdb/console.log.xz | Bin 39652 -> 40016 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3948 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2240 -> 2256 bytes 11-check_regression/console.log.xz | Bin 18136 -> 15760 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 73 +- 11-check_regression/mail-body.txt | 201 +- 11-check_regression/results.compare | 82 +- 11-check_regression/results.compare2 | 2066 +++----- 11-check_regression/results.regressions | 86 +- 12-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 203 +- mail/mail-subject.txt | 2 +- manifest.sh | 37 +- results | 86 +- sumfiles/gdb.log.xz | Bin 1889436 -> 1878432 bytes sumfiles/gdb.sum | 8180 ++++++++++--------------------- 30 files changed, 3731 insertions(+), 7339 deletions(-)