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 50c374cb11 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards 25131db109 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards 93fd6aed58 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards 131058b1a6 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards d1ff07599b 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards 1ca2958d11 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 7834bd6939 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards 840a095038 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards a8dfa82225 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards 4258dff709 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards fe5cefe794 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards dc40399b93 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards f3b01d7e42 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 8074b299c5 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 5b151456fc 121: onsuccess: #908: 1: Success after glibc: 2 commits discards ee6c829dff 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 274b41bf43 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards 7fba3c1d40 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards 34b05783b6 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards d41905908c 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards 6da539c1c4 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards 72d12662cf 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards f0a7fb62c1 113: onsuccess: #898: 1: Success after linux: 3 commits discards e5e9de9185 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 341ceaa38b 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards 53c0d69d39 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 83ebdf922b 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards 96cbb99403 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 9df0cbc193 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards 2fdcf76ade 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards d0f26d0bae 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 45f2109c68 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 5e57e863ba 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards c34f24b49f 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 580d5cdd1a 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 82bda93607 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards db181db2a9 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 259871e4a3 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards 3bb7a851c9 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards 0aacf8b463 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards db44f2d0c9 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards e0d695a214 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 910d9f240e 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 212fddafd7 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 7fcfb916e8 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 762bfceebc 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 9caa578d02 89: onsuccess: #864: 1: Success after binutils: 25 commits discards cb619f07a0 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards f33f458b24 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 8aa5c1082e 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards 680c219548 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards a81e9363a6 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 0232e09115 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards 3567d1e301 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards e052ac5f1b 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards e2eab12db7 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards f733d8b75e 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards f52068877a 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 56b1c4ca41 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 5c576ba5d4 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards b9a7f781dd 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards be8e37d585 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards ccca4bdc6d 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 0aa28805a7 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 7f030193f8 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 8ed8fbd24f 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards 7daa429e82 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards 918b8cb2bf 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 651b997ffe 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards ce0e53f5e9 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards b4b5c29425 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 14699d351c 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 2c9f55a5d9 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 084cc73ea9 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 64cc5f74ef 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 0ffa101099 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards bfc135694d 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards 77ffd255a7 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards a6e3d2b88d 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards 8a8e94bc12 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 068ad5785b 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 499bc522ee 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards cac8a6ad99 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 08cd2e39e1 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards bdf5e8d9d5 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards b34f3513c4 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards c5b9aad5be 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 2430412568 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 8bb5a1c336 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards c68c1ea5fc 46: onsuccess: #818: 1: Success after binutils: 10 commits discards a385df332a 45: onsuccess: #815: 1: Success after binutils: 6 commits discards ae8e473a02 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards f35474b15f 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] discards b14461f8c7 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards cd1632c617 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] discards e75692f868 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] discards 9da9ac6dbd 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards fffe6a9d30 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] discards 9ef29c2ac7 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] discards 07b51480d7 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] discards ed8008ebd0 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 8dd86ce78b 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 161f467d62 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] new 05bd1d7d7f 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] new 911ea2dd80 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] new 4adb29a29c 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 4ea889f317 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] new d049ad8e78 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] new 0ee72e8b12 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 519c85cb02 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new 09ca03462f 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 76f2d489c9 45: onsuccess: #815: 1: Success after binutils: 6 commits new 3bde4d9ae5 46: onsuccess: #818: 1: Success after binutils: 10 commits new 3ef5b40b70 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 187e5f1d88 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 4609df099a 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 11f830dbab 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new ba545975c9 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 4844e2e587 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 3990eaecdd 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new fd7074c791 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 827710da9c 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 2c8405a833 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new d77485fb0e 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new ce78ee1520 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new 433986793f 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 4e12e7c0bc 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 64874512de 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new a3bb3c17e5 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new f60e3043f9 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new f97462bdf1 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new 801bc9c6df 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new b7d9f7136e 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new e748073483 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new bbf6a1fe15 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new aa1abd991b 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new de26b8aed8 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new e9f2c11fe5 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 0511065164 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 3e36c20f38 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new 0ee7d0be14 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 3c5d6499b7 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 3d0f83f89f 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new aa505db7bb 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 06f7314d18 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new f83e89c497 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new f4f98f7702 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new cbcb32f244 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new d579e26205 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new e192c678f8 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new 3e8d69eebf 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new f2a3effa0f 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new f5ed0365ea 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new 0e4fc112bb 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 768eefe62b 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new e7b0b363d5 89: onsuccess: #864: 1: Success after binutils: 25 commits new 1389e05901 90: onsuccess: #867: 1: Success after binutils: 4 commits new a76d2b235e 91: onsuccess: #870: 1: Success after binutils: 5 commits new 4896f71a8c 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 444ad0c16a 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 0873e3416d 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 570def11b5 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new ad47bfbe72 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 7ed48fccdf 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new e9f3ff6804 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new cbc3b4aa02 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 50fc77c652 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 7ed5aa2430 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 53122647fd 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 21a6696e39 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new 31280d1c19 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 5b659c6c33 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new c700466dd8 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new d8227d0dd6 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new 1b19b62547 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new b06ab700a7 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new af4b2ed736 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new e7b0ca967d 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new 2be4bb3fc6 112: onsuccess: #896: 1: Success after binutils: 24 commits new 7c49d1c986 113: onsuccess: #898: 1: Success after linux: 3 commits new d995c68a65 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new 8c56f65175 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new d18e2dc66c 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new e2a99a35fe 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new 6f3b2c79af 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 0e9832e440 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new f5773321c7 120: onsuccess: #906: 1: Success after binutils: 29 commits new c8bb4ad1af 121: onsuccess: #908: 1: Success after glibc: 2 commits new fcc683cc9d 122: onsuccess: #909: 1: Success after linux: 2753 commits new a5563be103 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new 41729abfc9 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new 091f6ec538 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new 3a97ab2a9f 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new a22f31f1e0 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 13d5ca341d 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 65806d21ef 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new 7d6bf25dd3 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new 8a2e0e1536 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new 79ffb2b0c4 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new 8c2d353c9f 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new 7120fa9c2f 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new f8bebd3343 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new bed3a9a477 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 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 (50c374cb11) \ 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 1728 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39988 -> 39900 bytes 04-build_abe-gcc/console.log.xz | Bin 216204 -> 214964 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8328 -> 8340 bytes 07-build_abe-glibc/console.log.xz | Bin 244616 -> 244540 bytes 08-build_abe-gdb/console.log.xz | Bin 39472 -> 39692 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3836 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2024 -> 2028 bytes 11-check_regression/console.log.xz | Bin 19208 -> 12060 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 41 +- 11-check_regression/mail-body.txt | 164 +- 11-check_regression/results.compare | 68 +- 11-check_regression/results.compare2 | 6858 ++++++++---------------------- 11-check_regression/results.regressions | 68 +- 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 | 166 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 68 +- sumfiles/gdb.log.xz | Bin 1898308 -> 1897336 bytes sumfiles/gdb.sum | 7048 +++++++++++++++---------------- 29 files changed, 5384 insertions(+), 9199 deletions(-)