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 ad0b2e9094 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards 5e10fb1439 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards ffbf92354d 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards 4b08b381e2 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards 51969add25 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards d70a52571d 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards 3bf040971e 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards 348f4df890 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards e338e2ad19 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards 1f31e3e93e 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 800db0f6bb 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards cc0ee2c01b 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards ee7a2a9468 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 1562991759 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards b8387c0894 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards fe15a2a98b 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 0ea05c6f4c 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 43c48cd183 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 8a198804f7 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards 979d76a328 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards d4a29175c1 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards 104ac6f914 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards a2f6ae24ee 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards 7c634795f2 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards 655b3134f6 113: onsuccess: #898: 1: Success after linux: 3 commits discards 50ff95163d 112: onsuccess: #896: 1: Success after binutils: 24 commits discards a9d3e47513 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards 8b9f1af0ec 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 5cbcd9205d 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards b137ac24b0 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 5c5b223012 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards 3fe9b0378e 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 07bbe2cef4 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 2170719316 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards d010c1ee48 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards 9eb94f0546 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 5c91c5198d 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards ea67820f66 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 894eb6f9c1 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 03d78aedd3 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards 0e0ec0541e 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards e5cf027093 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 8162c5f901 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 58a842eead 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 63b3fe10d9 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 9263cc2319 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 902b21478a 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 07f596f319 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 96e903de65 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 2d9b826ddf 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards f4a03a8460 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards aeade31949 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards be17b85a38 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards b71f81e7a3 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 1f670c48f6 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards 7617dba4ae 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 20794de3d2 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards cd232a2343 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 4146c77473 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards f106a81044 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 2f7676ec05 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 974f240487 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 466b1069b1 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 1f56abf876 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards ce235eefe3 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 0604bae656 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 1576b84e8b 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards e29c1c7d5e 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards 454b9c9f8a 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards 93997aea55 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 91927b5146 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards c008b72248 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards 55fe18e4cb 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 72d22804da 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 165e74f600 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 5c55489442 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 73947b7d1c 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 8136de2f46 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards b4e5ec7212 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards e7b328462e 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards 27a0b81456 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards a68c63ea1f 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards add5efd03c 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 41cca541f8 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 55a79e8a27 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 641ef6ec5b 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 7bd41692cd 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 0d2355a215 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards 3ddae2828b 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards aff0527791 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 27cb1574f9 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 9b0d632005 46: onsuccess: #818: 1: Success after binutils: 10 commits discards eb5088e596 45: onsuccess: #815: 1: Success after binutils: 6 commits discards a0762bafc8 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 188ea6ced1 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] discards b70d70b8cf 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 62385b5c56 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] discards 3b22c4c814 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] discards 90b1918879 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards e64396e767 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] discards 63ee2265e1 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] new 85ac40b32c 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] new fbbe982e44 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] new ed90b8c609 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 9d486366da 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] new 2241f3173e 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] new acebb389bb 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new a03c66c88b 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new 4d24ca2707 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 19bd6bbfa7 45: onsuccess: #815: 1: Success after binutils: 6 commits new 3a2c5fc343 46: onsuccess: #818: 1: Success after binutils: 10 commits new d33a2900f8 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 967996f378 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 61c341ba26 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 33064957e3 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new d6bd327350 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new f323de28c4 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new d891ab89bb 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new c96f704b70 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 4ea49f504b 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 96552e7ace 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 52666f9b3d 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new fb2905991c 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new b87a79e453 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 5f69691cee 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new cda044c3b3 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 021bd2c6b8 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new cab933d049 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 7b118f8b07 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new ce7a511257 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 4849261237 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new f14df500a7 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new 26365be145 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new 205bb9ff83 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new c7f7dba7f9 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new fd69dff7be 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new b330bad48a 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 8ad626bc5b 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new 67af1663a6 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new c78e4bf4a6 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 48e2b4c7ed 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new dccae019a1 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 5330299815 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new a788abcd4f 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new b9e671e884 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 34ced97312 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 819fca775b 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new d0b88600bb 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new a989c90484 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new 5d9e082cd0 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 857c854c22 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new 5ccfde8ea7 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 356fad483d 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new b7508e4304 89: onsuccess: #864: 1: Success after binutils: 25 commits new 90c42634e2 90: onsuccess: #867: 1: Success after binutils: 4 commits new e9b71f6f77 91: onsuccess: #870: 1: Success after binutils: 5 commits new d863419de2 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new f5e4ab8ed7 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 1ebf71d191 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 80b85bbf68 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new 3318ab7f28 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 29d4fe6462 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new 840aa4cd4b 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 33eb9b7f6d 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new cc0f01eb3e 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 56bc32d36b 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 3f2f60b9f3 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new b6b0fc014c 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new 0c8310cd71 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 55154b62b2 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new bb724d7f23 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 286d1327f7 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new b8ddf19101 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 52cefc4e38 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 3de5d3f4af 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new e0b3ee73df 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new 7aa901e88f 112: onsuccess: #896: 1: Success after binutils: 24 commits new 85d11754f1 113: onsuccess: #898: 1: Success after linux: 3 commits new c567e58d50 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new fae56e62f6 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new 0340b4589a 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new 65d092da0c 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new ac69966688 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 24d6978340 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new fb839ebba3 120: onsuccess: #906: 1: Success after binutils: 29 commits new 048b21ec7c 121: onsuccess: #908: 1: Success after glibc: 2 commits new 996c67fcca 122: onsuccess: #909: 1: Success after linux: 2753 commits new 23fc8df094 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new d869dff1b8 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new c875d79f78 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new bf9537b664 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 94b7f8e4e1 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new dbb5a93753 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 8e5ca795d2 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new 87cd1d1e1c 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new 3667fff076 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new 38dd215c8d 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new db6b6aecd1 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new 326387d232 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new f54813fb71 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new 57d1f51bc6 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new 94a2480ae1 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new b1722bdda2 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 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 (ad0b2e9094) \ 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 1732 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 40896 -> 39892 bytes 04-build_abe-gcc/console.log.xz | Bin 215940 -> 215700 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8340 -> 8312 bytes 07-build_abe-glibc/console.log.xz | Bin 244604 -> 244928 bytes 08-build_abe-gdb/console.log.xz | Bin 39264 -> 39512 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3836 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2020 -> 2028 bytes 11-check_regression/console.log.xz | Bin 17276 -> 12904 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 37 +- 11-check_regression/mail-body.txt | 158 +- 11-check_regression/results.compare | 87 +- 11-check_regression/results.compare2 | 7092 ++++++++++++----------------- 11-check_regression/results.regressions | 87 +- 12-update_baseline/console.log | 60 +- 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 | 160 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 87 +- sumfiles/gdb.log.xz | Bin 1924760 -> 1938348 bytes sumfiles/gdb.sum | 7427 +++++++++++++++++++++---------- 29 files changed, 8317 insertions(+), 6920 deletions(-)