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 b1722bdda2 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards 94a2480ae1 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards 57d1f51bc6 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards f54813fb71 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards 326387d232 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards db6b6aecd1 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards 38dd215c8d 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards 3667fff076 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards 87cd1d1e1c 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 8e5ca795d2 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards dbb5a93753 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 94b7f8e4e1 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards bf9537b664 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards c875d79f78 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards d869dff1b8 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards 23fc8df094 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 996c67fcca 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 048b21ec7c 121: onsuccess: #908: 1: Success after glibc: 2 commits discards fb839ebba3 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 24d6978340 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards ac69966688 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards 65d092da0c 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards 0340b4589a 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards fae56e62f6 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards c567e58d50 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards 85d11754f1 113: onsuccess: #898: 1: Success after linux: 3 commits discards 7aa901e88f 112: onsuccess: #896: 1: Success after binutils: 24 commits discards e0b3ee73df 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards 3de5d3f4af 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 52cefc4e38 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards b8ddf19101 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 286d1327f7 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards bb724d7f23 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 55154b62b2 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 0c8310cd71 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards b6b0fc014c 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards 3f2f60b9f3 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 56bc32d36b 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards cc0f01eb3e 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 33eb9b7f6d 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 840aa4cd4b 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards 29d4fe6462 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards 3318ab7f28 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 80b85bbf68 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 1ebf71d191 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards f5e4ab8ed7 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards d863419de2 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards e9b71f6f77 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 90c42634e2 90: onsuccess: #867: 1: Success after binutils: 4 commits discards b7508e4304 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 356fad483d 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards 5ccfde8ea7 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 857c854c22 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards 5d9e082cd0 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards a989c90484 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards d0b88600bb 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards 819fca775b 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 34ced97312 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards b9e671e884 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards a788abcd4f 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards 5330299815 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards dccae019a1 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 48e2b4c7ed 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards c78e4bf4a6 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 67af1663a6 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 8ad626bc5b 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards b330bad48a 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards fd69dff7be 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards c7f7dba7f9 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards 205bb9ff83 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards 26365be145 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards f14df500a7 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 4849261237 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards ce7a511257 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 7b118f8b07 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards cab933d049 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 021bd2c6b8 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards cda044c3b3 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 5f69691cee 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards b87a79e453 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards fb2905991c 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards 52666f9b3d 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards 96552e7ace 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 4ea49f504b 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards c96f704b70 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards d891ab89bb 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards f323de28c4 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards d6bd327350 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 33064957e3 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards 61c341ba26 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 967996f378 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards d33a2900f8 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 3a2c5fc343 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 19bd6bbfa7 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 4d24ca2707 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards a03c66c88b 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] discards acebb389bb 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 2241f3173e 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] discards 9d486366da 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] discards ed90b8c609 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards fbbe982e44 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] new 9248b0239d 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] new 88bc4a20a8 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new f4c81f0547 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] new d4838d98fe 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] new f9949838e2 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 516040f15a 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new bc361893be 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 1a434dd6ce 45: onsuccess: #815: 1: Success after binutils: 6 commits new bb2e658899 46: onsuccess: #818: 1: Success after binutils: 10 commits new 251a721a9c 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 0b23cc3e8a 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new cbb3bc4280 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new ff8babba1c 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new 2d66395dc6 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new fda083ab4f 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 6a9b0f2c61 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 39702c447c 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 505d0b4228 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 2eae3bafdb 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 1ca8f672c1 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new 0af751d60e 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new 07e4cab27f 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 65a0d97b22 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new cf9214e68e 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 7bc170527b 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new f21ad3bb19 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new edd7b8588f 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new d66a4f02a2 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 41b920a496 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new ab269f3970 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new 01689beba1 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new 555aec250b 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 2a36d2dcc2 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new d7858fbedb 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 81a17e070c 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 718b1e4f2c 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new 076c071756 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 0e0d7950f8 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 390338cb61 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 2ce51e25be 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new efc3b81e5e 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 66a153b83b 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new 4dbcb2a840 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new e340e72258 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new a00f0f871e 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new 7fd0e6b7d4 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new d147f1dd12 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new d23422872b 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new d1f244b735 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new fe123c7578 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new ee3e0cecd4 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 4c918596e2 89: onsuccess: #864: 1: Success after binutils: 25 commits new d8bce3dc7b 90: onsuccess: #867: 1: Success after binutils: 4 commits new 4cbfa3f594 91: onsuccess: #870: 1: Success after binutils: 5 commits new 882cf21681 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new cacb22bdce 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 2e756f994e 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 5890b61c15 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new 280df4aa36 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 422de3bf1d 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new 1330514fdf 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 8cb4956232 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new acb77c1fb2 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 59a96e4a91 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 330f8e0436 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 51a4ca9710 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new ea597c86e6 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 4db64d2c84 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new b150378612 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new bf1aa7e42f 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new d17ce9be16 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new e5ec19d117 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 33d7fb9d20 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 795ad2a077 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new c7063cacef 112: onsuccess: #896: 1: Success after binutils: 24 commits new 5746e7da6e 113: onsuccess: #898: 1: Success after linux: 3 commits new 6608b7e69f 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new 7f67c718d3 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new 0852153e47 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new b97f166b77 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new 05ec2c33ae 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new fde0c1555d 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new 1f1bf04a9b 120: onsuccess: #906: 1: Success after binutils: 29 commits new 7aaa1c4061 121: onsuccess: #908: 1: Success after glibc: 2 commits new 24f97a0f1e 122: onsuccess: #909: 1: Success after linux: 2753 commits new f804bc508e 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new b0a0a5a8b0 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new 019289c39e 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new 0b22dd4935 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 6c1ed05953 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 84a211ccd1 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 2e98934e06 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new 0c6a0a0aac 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new 3a4bdcf420 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new d2ee614d83 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new c91be79af9 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new 31f717e783 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new 4351e8b02e 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new 43a58b45d4 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new 19838cdbbe 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new c59f30f585 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new b7634efd00 139: onsuccess: #926: 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 (b1722bdda2) \ 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 1744 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 39892 -> 40112 bytes 04-build_abe-gcc/console.log.xz | Bin 215700 -> 213896 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8312 -> 9188 bytes 07-build_abe-glibc/console.log.xz | Bin 244928 -> 244504 bytes 08-build_abe-gdb/console.log.xz | Bin 39512 -> 39376 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3888 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2028 -> 2032 bytes 11-check_regression/console.log.xz | Bin 12904 -> 10276 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 35 +- 11-check_regression/mail-body.txt | 166 +- 11-check_regression/results.compare | 79 +- 11-check_regression/results.compare2 | 4017 ++++++----------------- 11-check_regression/results.regressions | 79 +- 12-update_baseline/console.log | 64 +- 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 | 168 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 79 +- sumfiles/gdb.log.xz | Bin 1938348 -> 1955372 bytes sumfiles/gdb.sum | 5411 +++++++++++++------------------ 31 files changed, 3718 insertions(+), 6434 deletions(-)