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 bed3a9a477 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards f8bebd3343 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards 7120fa9c2f 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards 8c2d353c9f 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards 79ffb2b0c4 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards 8a2e0e1536 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards 7d6bf25dd3 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 65806d21ef 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards 13d5ca341d 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards a22f31f1e0 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards 3a97ab2a9f 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards 091f6ec538 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 41729abfc9 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards a5563be103 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards fcc683cc9d 122: onsuccess: #909: 1: Success after linux: 2753 commits discards c8bb4ad1af 121: onsuccess: #908: 1: Success after glibc: 2 commits discards f5773321c7 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 0e9832e440 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards 6f3b2c79af 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards e2a99a35fe 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards d18e2dc66c 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards 8c56f65175 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards d995c68a65 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards 7c49d1c986 113: onsuccess: #898: 1: Success after linux: 3 commits discards 2be4bb3fc6 112: onsuccess: #896: 1: Success after binutils: 24 commits discards e7b0ca967d 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards af4b2ed736 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards b06ab700a7 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards 1b19b62547 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards d8227d0dd6 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards c700466dd8 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 5b659c6c33 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 31280d1c19 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 21a6696e39 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards 53122647fd 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 7ed5aa2430 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 50fc77c652 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards cbc3b4aa02 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards e9f3ff6804 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards 7ed48fccdf 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards ad47bfbe72 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 570def11b5 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 0873e3416d 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 444ad0c16a 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 4896f71a8c 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards a76d2b235e 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 1389e05901 90: onsuccess: #867: 1: Success after binutils: 4 commits discards e7b0b363d5 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 768eefe62b 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards 0e4fc112bb 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards f5ed0365ea 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards f2a3effa0f 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards 3e8d69eebf 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards e192c678f8 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards d579e26205 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards cbcb32f244 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards f4f98f7702 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards f83e89c497 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards 06f7314d18 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards aa505db7bb 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 3d0f83f89f 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 3c5d6499b7 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 0ee7d0be14 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 3e36c20f38 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 0511065164 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards e9f2c11fe5 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards de26b8aed8 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards aa1abd991b 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards bbf6a1fe15 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards e748073483 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards b7d9f7136e 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards 801bc9c6df 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards f97462bdf1 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards f60e3043f9 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards a3bb3c17e5 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 64874512de 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 4e12e7c0bc 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards 433986793f 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards ce78ee1520 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards d77485fb0e 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards 2c8405a833 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 827710da9c 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards fd7074c791 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 3990eaecdd 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 4844e2e587 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards ba545975c9 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 11f830dbab 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards 4609df099a 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 187e5f1d88 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 3ef5b40b70 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 3bde4d9ae5 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 76f2d489c9 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 09ca03462f 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 519c85cb02 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] discards 0ee72e8b12 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards d049ad8e78 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] discards 4ea889f317 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] discards 4adb29a29c 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 911ea2dd80 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] discards 05bd1d7d7f 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] discards 161f467d62 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] new a11625465f 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] new 63ee2265e1 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] new e64396e767 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] new 90b1918879 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 3b22c4c814 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] new 62385b5c56 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] new b70d70b8cf 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 188ea6ced1 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new a0762bafc8 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new eb5088e596 45: onsuccess: #815: 1: Success after binutils: 6 commits new 9b0d632005 46: onsuccess: #818: 1: Success after binutils: 10 commits new 27cb1574f9 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new aff0527791 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 3ddae2828b 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 0d2355a215 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new 7bd41692cd 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 641ef6ec5b 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 55a79e8a27 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 41cca541f8 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new add5efd03c 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new a68c63ea1f 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 27a0b81456 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new e7b328462e 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new b4e5ec7212 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 8136de2f46 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 73947b7d1c 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 5c55489442 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 165e74f600 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 72d22804da 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new 55fe18e4cb 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new c008b72248 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new 91927b5146 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new 93997aea55 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new 454b9c9f8a 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new e29c1c7d5e 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new 1576b84e8b 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 0604bae656 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new ce235eefe3 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new 1f56abf876 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 466b1069b1 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 974f240487 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 2f7676ec05 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new f106a81044 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 4146c77473 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new cd232a2343 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 20794de3d2 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 7617dba4ae 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new 1f670c48f6 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new b71f81e7a3 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new be17b85a38 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new aeade31949 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new f4a03a8460 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 2d9b826ddf 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 96e903de65 89: onsuccess: #864: 1: Success after binutils: 25 commits new 07f596f319 90: onsuccess: #867: 1: Success after binutils: 4 commits new 902b21478a 91: onsuccess: #870: 1: Success after binutils: 5 commits new 9263cc2319 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 63b3fe10d9 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 58a842eead 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 8162c5f901 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new e5cf027093 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 0e0ec0541e 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new 03d78aedd3 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 894eb6f9c1 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new ea67820f66 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 5c91c5198d 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 9eb94f0546 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new d010c1ee48 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new 2170719316 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 07bbe2cef4 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 3fe9b0378e 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 5c5b223012 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new b137ac24b0 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 5cbcd9205d 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 8b9f1af0ec 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new a9d3e47513 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new 50ff95163d 112: onsuccess: #896: 1: Success after binutils: 24 commits new 655b3134f6 113: onsuccess: #898: 1: Success after linux: 3 commits new 7c634795f2 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new a2f6ae24ee 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new 104ac6f914 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new d4a29175c1 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new 979d76a328 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 8a198804f7 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new 43c48cd183 120: onsuccess: #906: 1: Success after binutils: 29 commits new 0ea05c6f4c 121: onsuccess: #908: 1: Success after glibc: 2 commits new fe15a2a98b 122: onsuccess: #909: 1: Success after linux: 2753 commits new b8387c0894 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new 1562991759 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new ee7a2a9468 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new cc0ee2c01b 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 800db0f6bb 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 1f31e3e93e 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new e338e2ad19 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new 348f4df890 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new 3bf040971e 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new d70a52571d 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new 51969add25 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new 4b08b381e2 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new ffbf92354d 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new 5e10fb1439 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new ad0b2e9094 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits

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 (bed3a9a477) \ 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 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 39900 -> 40896 bytes 04-build_abe-gcc/console.log.xz | Bin 214964 -> 215940 bytes 06-build_abe-linux/console.log.xz | Bin 8340 -> 8340 bytes 07-build_abe-glibc/console.log.xz | Bin 244540 -> 244604 bytes 08-build_abe-gdb/console.log.xz | Bin 39692 -> 39264 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2028 -> 2020 bytes 11-check_regression/console.log.xz | Bin 12060 -> 17276 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 53 +- 11-check_regression/mail-body.txt | 139 +- 11-check_regression/results.compare | 71 +- 11-check_regression/results.compare2 | 6977 +++++++++++++++++++------------ 11-check_regression/results.regressions | 71 +- 12-update_baseline/console.log | 56 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 141 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 71 +- sumfiles/gdb.log.xz | Bin 1897336 -> 1924760 bytes sumfiles/gdb.sum | 4495 ++++++++++++++++++-- 28 files changed, 8747 insertions(+), 3369 deletions(-)