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 a9ed307378 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards 7f2869167f 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards a5b8bb98b4 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards e735a10994 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards caead402e9 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards ef00775c8c 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards 0eb50d8020 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards e192229f84 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards a524e3098b 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards c274ba4721 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards 870ab9749a 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards 25063e12bf 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards 4c1b6788bd 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards 6d233fa1d5 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards af3cfb52d7 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards bc25f3cdbb 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards 77b23b1269 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards 2a452d2e46 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards e9cc900b10 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards ef5705ac0e 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards 1078943944 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards 5b8044c7c3 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 31dec99ffa 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards 8327a5aa01 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 941648df72 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards 678009d716 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards 9052a700d0 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards db56b96456 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards 8d6e0e7eba 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 3b0d7a5e83 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 8dda0238ac 121: onsuccess: #908: 1: Success after glibc: 2 commits discards e6318381de 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 451fdbfb5d 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards 111b7063ab 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards 1a65ba8a23 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards 2d8e861370 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards fdfef64f8f 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards 263b4730c7 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards 322eb813b0 113: onsuccess: #898: 1: Success after linux: 3 commits discards e7ec3250ed 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 0b474190ee 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards 1b02170e9a 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 6f801486cb 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards 6f117f3c37 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 3b0d3747e0 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards ece327d816 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 372dcf9a61 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards dd338e0521 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards e6ad5eb607 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards 4e5c3ed07d 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 9fd2e63918 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards ace527602f 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 2c52e40cf6 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 57297913a4 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards 872d260516 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards 804e059320 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 883818e83f 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 09a2b2ad4a 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 4a0ccf3cf9 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards db10bcf2d7 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards e0e2552bab 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 0f9cdf23b3 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 009242c025 89: onsuccess: #864: 1: Success after binutils: 25 commits discards dfdab4172f 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards 4960c6fee6 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 3d27a2dd81 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards 674d087e17 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards 6e934c46e6 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards f964999450 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards 1e8994a53a 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards f7f1a8a565 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards 3966bf6a22 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 0d94376e61 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards 468beaba4e 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 93b63d0731 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 43a2630d5f 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 651f875fd9 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 296f34ae28 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards d2720c94a7 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards f4117d2540 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 294fce2907 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 5e5d1ee223 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards b13a994114 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards dcf41c926b 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 105e83bc13 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 34774bdf64 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards 26fd27904a 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 667e65f98a 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 13c11162fd 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards c2e1512930 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 3b851214f8 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards f01a184834 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards 3169470c78 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards 268cf8f196 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards 528e2d72c8 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards 1c0971cab7 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards cef5ffdae9 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 0fc8f1acd6 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 4d119709f2 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 09dc990d7e 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 6557f40df8 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 4f8e3a6e6a 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 8169dadb2d 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 0d8e733df1 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new c3540d4766 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new b63bbd8ae1 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 86c94b01f0 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 8aecd530d2 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new 2800a51723 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new 03d0aef9fe 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 8519839e1d 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 4c0a8cc2b1 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new af071c6571 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 910b29fca8 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 9b23ed1a90 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new 4820ed10c8 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new bc02631830 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new a70b83e124 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new bd6726bdd5 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new a94586c9b9 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 9335366e35 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new 9991f70666 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 0f496fd2f2 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 7f1595713e 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new 48be5a8e1d 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new f83ea7fa84 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new e6871b4b7a 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new f1433c0d38 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new dc8f572f62 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 0f2da2ab9f 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new 76f90b733f 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new fc0dc095a3 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 103d60a027 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new f1bf77811f 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new 957d4b08fa 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new 653acf67ac 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 1adeeb837f 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new 697b2265c3 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new a032fc559f 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new cc13f9015b 89: onsuccess: #864: 1: Success after binutils: 25 commits new 659e1def81 90: onsuccess: #867: 1: Success after binutils: 4 commits new 6ad2b64d57 91: onsuccess: #870: 1: Success after binutils: 5 commits new f4e5ba8353 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 0cd66654a8 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 221ca6655f 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new f128fbf132 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new 9e7ca285fe 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 244db21ee4 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new 57635ad3f0 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new b475cdc267 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new ce2f61a914 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new d91fcd75d9 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 83307d0637 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 261ff4822d 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new fd9d6ad5f9 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 51061cdb61 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new e58892ee23 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 309accb302 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new 760596b0d3 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 7a22e4faf5 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 6ed7db1278 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new dca09c87e5 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new fa48c6ce39 112: onsuccess: #896: 1: Success after binutils: 24 commits new 6d06ac5310 113: onsuccess: #898: 1: Success after linux: 3 commits new 0b20593ac5 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new 033d8ed6ab 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new 77267b48f2 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new 11962d6988 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new e2c45540f9 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new a7d7c0e0c0 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new 3331b92154 120: onsuccess: #906: 1: Success after binutils: 29 commits new 81c5078530 121: onsuccess: #908: 1: Success after glibc: 2 commits new f07fd68831 122: onsuccess: #909: 1: Success after linux: 2753 commits new 8da3a7b374 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new e97362d025 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new 7096b3e7b3 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new 68c6340663 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 5da80ea7f4 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 33d94c44be 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 6406049b83 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new 63143cbfac 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new 0085d1fd82 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new 75d448727c 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new f50bbba42d 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new 72910a7393 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new a11c0f4e17 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new e8ca847659 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new 91fde85c7e 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new bbf5cbc6e2 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new 79fde50a58 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new 6b29bba91f 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new 098becbbb2 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new 4fc83e9fda 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new aa2e19167b 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 44a57ea2a0 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new 10fe937bc6 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new 042604bff7 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 7de9925ce7 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new 93d64503ee 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new c24ebdecc0 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new 8b922043ba 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new 875db35c2b 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 191e1e9378 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...]
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 (a9ed307378) \ 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 1764 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 39108 -> 39104 bytes 04-build_abe-gcc/console.log.xz | Bin 213192 -> 213524 bytes 06-build_abe-linux/console.log.xz | Bin 9496 -> 8684 bytes 07-build_abe-glibc/console.log.xz | Bin 245412 -> 245488 bytes 08-build_abe-gdb/console.log.xz | Bin 39076 -> 38736 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3832 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2028 -> 2108 bytes 11-check_regression/console.log.xz | Bin 9076 -> 11032 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 31 +- 11-check_regression/mail-body.txt | 129 +++--- 11-check_regression/results.compare | 64 ++- 11-check_regression/results.compare2 | 605 +++++++++++++++++++++++----- 11-check_regression/results.regressions | 64 ++- 12-update_baseline/console.log | 60 +-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 131 +++---- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 64 ++- sumfiles/gdb.log.xz | Bin 1882560 -> 1927428 bytes sumfiles/gdb.sum | 672 +++++++++----------------------- 29 files changed, 970 insertions(+), 898 deletions(-)