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 c952536c4c 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards df4c14325b 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 214fe23f93 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards 3cbceb62d8 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 36f78cdd59 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 6141b24b69 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 93018fcd42 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 917ee565f2 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards ba41f3d2d1 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards a073f09d95 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 7029eb2c55 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards be92be4401 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 6042ef85bf 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 8ccaf0fa57 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards af02fadfe5 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 495c57ff5e 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 5ba84af996 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 5af2dd5247 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards e9524b1286 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards d055839011 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards 630774d594 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards 14a86f627c 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 6b5ef3e5ef 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards 399b227369 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 35453b7274 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards c77658794d 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 21aa03ce94 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards 3ea4ba1b3f 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 03f3585da8 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards f120d5013f 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards f6b50a49f9 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 41701fb52d 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 2676e7c295 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards e02c5daeb1 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards d6d0fc0200 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 669cacd361 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards 3f0e93b2ef 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards 18911e2356 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards a9171d1d8a 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 55021dffbc 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards 6022f4e04a 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards fbb6d18e27 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards f4df7530ef 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards c461123088 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 9b5a0848d7 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 9a60c13264 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards f29c08436f 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards 168597f741 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards bf019d3b3a 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards 879f215d9d 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards e273d01a22 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 6547cdd52e 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 8452e3eb21 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 48c4260cc0 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 3b31e99f2d 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 474bbe0e97 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards 20b26f8d86 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 70b29f8647 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards becce1f01f 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards b6d145fc7c 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 6e275f8f7e 45: onsuccess: #815: 1: Success after binutils: 6 commits discards fb70142ba1 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 642ab0f439 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] discards aafd714559 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 841e405cd5 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] discards da6d0e1128 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] discards ad4d0545d6 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards e1ee00b390 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] discards 042cec11ab 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] discards 60a05e466a 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] discards 1aa2f5cb88 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 560590d5cc 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] discards 09111511e8 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 4158702c53 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards d0e1ee09fe 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gli [...] discards ed0872448b 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards f1bc339adb 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gdb [...] discards 04b4273dfc 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 0b3ce0df8c 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gli [...] discards 91fdd6cffa 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gdb [...] discards f09a1a9dc0 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 36f90cfb00 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 7a7c0f0fba 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gdb [...] discards b9dd34f267 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 commits discards c89487c9db 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 commits discards 4a1d9abc1f 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 200ca4c060 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e8a5a19dad 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6dc617ba40 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 68cfd1e558 16: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards dc9a3ef5e6 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b42412a704 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 267769de36 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2d3a5ccd38 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8ba37ed19a 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8b177fc4cd 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d732a8eb55 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 39880f9295 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b632c6339f 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 4e6a4e56d7 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards ccad609bc6 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new c81601e59d 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 10f09ca276 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new a16ff75ec0 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new b80978d34d 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 718e8f0404 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f46f49bc51 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 382812faa6 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 95fb8cc0ea 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a230034dc4 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1bd62370e1 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a2f46afd06 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b29a34231b 16: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 57ac660c55 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 079be35533 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7c3ab5bc95 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 03c43fb06d 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 48a7575162 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 commits new ff3baa4769 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 commits new 1c97c3883b 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gdb [...] new 4f2cca5c8a 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new c90f97d488 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 36b936cec2 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gdb [...] new 78a6e2cf08 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gli [...] new a79beeabd9 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 0903cb8543 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gdb [...] new c6f78aca5b 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new affa3e9d89 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gli [...] new 5667da1f02 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new a98b72040c 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 9e5bea651c 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] new 3c759b4229 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new d42325bcb0 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] new 06db1fbc99 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] new 4c5c471697 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] new 8229bcae28 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new aabdf310a6 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] new 619e377dab 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] new d851f9520a 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new d5d6ad7f1d 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new 111db10005 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new d39c41347d 45: onsuccess: #815: 1: Success after binutils: 6 commits new e29cd10848 46: onsuccess: #818: 1: Success after binutils: 10 commits new 3fd4ca616d 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 1ef3593e71 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new d5522283d6 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 5a7c8bbc7f 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new 9c09ca5570 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new a9b158b556 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 647b5b138a 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new bce2f84b3b 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 0408a6702a 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 5956db3354 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new ea1a09ca5f 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new 3e59b2b183 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new a814e2d11d 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new b1dc27891e 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 82a590a648 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new ffa0327c37 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new e076369ddf 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 9c8d9ad2e0 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new f1de64f557 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 13d9eb8fc1 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new 7520d0bc26 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new 790a024f13 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new afa2d15a04 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 7c474c6b68 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new 18e18c28d3 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 38c2b7c61e 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 4c3e829c1d 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new f780fe86ff 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 867e5c7a65 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 2e45a7181c 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new c606f832aa 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 159478fdd7 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new eae9fcef49 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new 65868ec242 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 2cfb77adea 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 0b5e105e3f 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new c3d8854c20 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new 6fba97daec 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new e7bd6298a4 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 04c34843c6 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new c36d838f7b 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 637fe972da 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new c0364d35b9 89: onsuccess: #864: 1: Success after binutils: 25 commits new 19adbec431 90: onsuccess: #867: 1: Success after binutils: 4 commits new 2ebaf30772 91: onsuccess: #870: 1: Success after binutils: 5 commits new 184ffdab5a 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new b04951e510 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 14a2d83bdc 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 0bbe52f740 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new 21242955dd 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new e87991fd67 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new 516e9177eb 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 05c0210e94 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 3d9931332b 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 78fdc24161 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new ba1088e2d3 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 65ea87532e 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new eb3e435c15 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 60cc7ac203 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 5e55c844b7 106: onsuccess: #887: 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 (c952536c4c) \ 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 1688 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 39516 -> 39464 bytes 04-build_abe-gcc/console.log.xz | Bin 213320 -> 214864 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8764 -> 9460 bytes 07-build_abe-glibc/console.log.xz | Bin 243352 -> 244840 bytes 08-build_abe-gdb/console.log.xz | Bin 39056 -> 39376 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3840 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2636 -> 2428 bytes 11-check_regression/console.log.xz | Bin 18480 -> 16428 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 34 +- 11-check_regression/mail-body.txt | 103 +- 11-check_regression/results.compare | 62 +- 11-check_regression/results.compare2 | 856 +--- 11-check_regression/results.regressions | 62 +- 12-update_baseline/console.log | 52 +- 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 | 105 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 62 +- sumfiles/gdb.log.xz | Bin 1916896 -> 1939844 bytes sumfiles/gdb.sum | 8315 +++++++++++++++++++++++-------- 31 files changed, 6614 insertions(+), 3093 deletions(-)