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 e428cfd90a 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards cda52e39cd 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards bb9699e583 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 756753d794 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 05dbdc2e5c 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 8061595ef6 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards c29162bab0 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards c70a2c4797 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards 52118d7777 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards e98cd96f6c 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 47deec3147 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards ef6801d830 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 3a3cc37885 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 1f18e056f9 91: onsuccess: #870: 1: Success after binutils: 5 commits discards ec33bea0b7 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 851b6b20b0 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 146a248ee9 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards 09a8bd4df8 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards a68555e9d6 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards 17318b7659 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards d497a96179 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 5ce35c0c48 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards f8708d5a45 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 30caf88efa 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards d25866320f 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards e57a5d2ece 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards d2a78a7d5d 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards e0079abaa0 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 7f86bc7fbb 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards d5ad105be8 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 5dfc6c4055 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 8df28e5cfc 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 86098d6592 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 1bd91ffc72 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards ae63ff2024 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards 2d546a01cb 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards 468865250c 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 3da1104c6d 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 78336dddd7 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards fef7116ad7 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards ba9e674ebe 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 56cd414b81 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 9f77b18d2f 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 945d81eb67 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 3a41c7e4f9 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards 09f70a3c15 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards 02d5e3ce47 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards 8cdc6511d7 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards 7982579770 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 96483ac007 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 9d1968ca3d 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 21e3377857 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 173af1004f 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 00607c35a3 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 0691a818c5 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards 32777bbac2 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 786980a2e4 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 8ea1b962f3 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards ac6949f256 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 5b2b02033b 45: onsuccess: #815: 1: Success after binutils: 6 commits discards bfbe9cdd36 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 1fd8b4329d 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] discards ce25736efa 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 2454b590a4 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] discards 169b4b3f7a 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] discards 319ec36513 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 4ffd1ae34e 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] discards b8db35566f 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] discards 381616ce7b 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] discards 09d22cc188 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards da4736c897 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] discards 22e00c71c0 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 713230eb65 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 73f8f47f1f 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gli [...] discards ed7d70ad4c 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 14f35064ff 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gdb [...] discards d340311c85 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards def9b557ba 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gli [...] discards f841098c31 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gdb [...] discards 39664eac68 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 5cfaae1a96 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 43d0b5c066 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gdb [...] discards c72cd118ca 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 commits discards 6516ad2b07 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 commits discards f4412a5b52 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 7e13ae8dba 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards eaa1138a16 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a76276b89d 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0103ef5058 16: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ad274aee4b 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards eb1f6195c9 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b1907b5356 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0282c281fb 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5f38684789 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e0f323a8d0 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fdc4c57ea7 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 51ad7fcf21 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c15b46172f 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 2c7403c80e 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards f0ee9ce0c5 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 1ebc9239a2 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 6b0fb00dcf 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new ccad609bc6 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 4e6a4e56d7 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new b632c6339f 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 39880f9295 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d732a8eb55 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 8b177fc4cd 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8ba37ed19a 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2d3a5ccd38 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 267769de36 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b42412a704 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new dc9a3ef5e6 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 68cfd1e558 16: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 6dc617ba40 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e8a5a19dad 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 200ca4c060 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4a1d9abc1f 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new c89487c9db 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 commits new b9dd34f267 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 commits new 7a7c0f0fba 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gdb [...] new 36f90cfb00 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new f09a1a9dc0 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 91fdd6cffa 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gdb [...] new 0b3ce0df8c 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gli [...] new 04b4273dfc 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new f1bc339adb 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gdb [...] new ed0872448b 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new d0e1ee09fe 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gli [...] new 4158702c53 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 09111511e8 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 560590d5cc 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] new 1aa2f5cb88 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 60a05e466a 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] new 042cec11ab 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] new e1ee00b390 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] new ad4d0545d6 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new da6d0e1128 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] new 841e405cd5 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] new aafd714559 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 642ab0f439 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new fb70142ba1 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 6e275f8f7e 45: onsuccess: #815: 1: Success after binutils: 6 commits new b6d145fc7c 46: onsuccess: #818: 1: Success after binutils: 10 commits new becce1f01f 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 70b29f8647 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 20b26f8d86 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 474bbe0e97 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new 3b31e99f2d 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 48c4260cc0 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 8452e3eb21 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 6547cdd52e 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new e273d01a22 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 879f215d9d 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new bf019d3b3a 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new 168597f741 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new f29c08436f 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 9a60c13264 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 9b5a0848d7 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new c461123088 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new f4df7530ef 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new fbb6d18e27 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new 6022f4e04a 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 55021dffbc 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new a9171d1d8a 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new 18911e2356 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new 3f0e93b2ef 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 669cacd361 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new d6d0fc0200 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new e02c5daeb1 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 2676e7c295 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new 41701fb52d 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new f6b50a49f9 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new f120d5013f 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 03f3585da8 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 3ea4ba1b3f 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 21aa03ce94 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new c77658794d 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 35453b7274 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 399b227369 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new 6b5ef3e5ef 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new 14a86f627c 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new 630774d594 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new d055839011 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new e9524b1286 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 5af2dd5247 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 5ba84af996 89: onsuccess: #864: 1: Success after binutils: 25 commits new 495c57ff5e 90: onsuccess: #867: 1: Success after binutils: 4 commits new af02fadfe5 91: onsuccess: #870: 1: Success after binutils: 5 commits new 8ccaf0fa57 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 6042ef85bf 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new be92be4401 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 7029eb2c55 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new a073f09d95 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new ba41f3d2d1 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new 917ee565f2 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 93018fcd42 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 6141b24b69 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 36f78cdd59 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 3cbceb62d8 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 214fe23f93 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new df4c14325b 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new c952536c4c 105: onsuccess: #886: 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 (e428cfd90a) \ 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 1692 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 39852 -> 39516 bytes 04-build_abe-gcc/console.log.xz | Bin 215508 -> 213320 bytes 06-build_abe-linux/console.log.xz | Bin 8256 -> 8764 bytes 07-build_abe-glibc/console.log.xz | Bin 243396 -> 243352 bytes 08-build_abe-gdb/console.log.xz | Bin 38768 -> 39056 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3836 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2304 -> 2636 bytes 11-check_regression/console.log.xz | Bin 17720 -> 18480 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 22 +- 11-check_regression/mail-body.txt | 92 +- 11-check_regression/results.compare | 41 +- 11-check_regression/results.compare2 | 2684 +++++++----------- 11-check_regression/results.regressions | 41 +- 12-update_baseline/console.log | 50 +- 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 | 94 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 41 +- sumfiles/gdb.log.xz | Bin 1921028 -> 1916896 bytes sumfiles/gdb.sum | 4686 +++---------------------------- 30 files changed, 1575 insertions(+), 6230 deletions(-)