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 5e55c844b7 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 60cc7ac203 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards eb3e435c15 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 65ea87532e 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards ba1088e2d3 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 78fdc24161 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 3d9931332b 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 05c0210e94 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 516e9177eb 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards e87991fd67 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards 21242955dd 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 0bbe52f740 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 14a2d83bdc 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards b04951e510 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 184ffdab5a 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 2ebaf30772 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 19adbec431 90: onsuccess: #867: 1: Success after binutils: 4 commits discards c0364d35b9 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 637fe972da 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards c36d838f7b 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 04c34843c6 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards e7bd6298a4 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards 6fba97daec 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards c3d8854c20 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards 0b5e105e3f 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 2cfb77adea 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards 65868ec242 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards eae9fcef49 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards 159478fdd7 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards c606f832aa 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 2e45a7181c 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 867e5c7a65 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards f780fe86ff 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 4c3e829c1d 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 38c2b7c61e 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 18e18c28d3 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 7c474c6b68 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards afa2d15a04 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards 790a024f13 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 7520d0bc26 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 13d9eb8fc1 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards f1de64f557 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 9c8d9ad2e0 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards e076369ddf 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards ffa0327c37 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 82a590a648 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards b1dc27891e 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards a814e2d11d 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards 3e59b2b183 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards ea1a09ca5f 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards 5956db3354 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 0408a6702a 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards bce2f84b3b 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 647b5b138a 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards a9b158b556 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 9c09ca5570 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 5a7c8bbc7f 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards d5522283d6 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 1ef3593e71 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 3fd4ca616d 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards e29cd10848 46: onsuccess: #818: 1: Success after binutils: 10 commits discards d39c41347d 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 111db10005 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards d5d6ad7f1d 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] discards d851f9520a 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 619e377dab 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] discards aabdf310a6 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] discards 8229bcae28 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 4c5c471697 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] discards 06db1fbc99 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] discards d42325bcb0 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] discards 3c759b4229 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 9e5bea651c 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] discards a98b72040c 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 5667da1f02 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards affa3e9d89 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gli [...] discards c6f78aca5b 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 0903cb8543 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gdb [...] discards a79beeabd9 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 78a6e2cf08 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gli [...] discards 36b936cec2 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gdb [...] discards c90f97d488 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 4f2cca5c8a 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 1c97c3883b 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gdb [...] discards ff3baa4769 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 commits discards 48a7575162 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 commits discards 03c43fb06d 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 7c3ab5bc95 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 079be35533 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 57ac660c55 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b29a34231b 16: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a2f46afd06 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1bd62370e1 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a230034dc4 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 95fb8cc0ea 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 382812faa6 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f46f49bc51 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 718e8f0404 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b80978d34d 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a16ff75ec0 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 10f09ca276 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new cb118498ac 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new d2caa214e3 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 4de03b3819 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7777547def 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 136c351327 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1304302254 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4ad987d3ad 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2580d3129c 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4bca88925a 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d4a559f294 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0d043b72d0 16: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 022194a730 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6e2d82c28a 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cc424f9094 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d680f54bc6 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new b29aa21fd7 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 commits new bff4f5c692 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 commits new ea14dc32d2 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gdb [...] new ab01f4cddb 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 23456b06db 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new deabb5d711 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gdb [...] new abd9997b9b 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gli [...] new 22216f2875 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 314fe13ca4 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gdb [...] new b489a3b36c 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new ebb3443c3f 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gli [...] new b273ed8bc7 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new e504378141 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 9b75e05df0 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] new 28e5ab9b12 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 5a8b25cdc0 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] new c84d83c352 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] new ed38a9a0dc 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] new ea77e5ca0f 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 72cdc55e4d 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] new 7227df7482 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] new 2267ec191d 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 76549875b1 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new 636427ebc9 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 0c53adc8f6 45: onsuccess: #815: 1: Success after binutils: 6 commits new 17b4ccbfc6 46: onsuccess: #818: 1: Success after binutils: 10 commits new 7095f1930d 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new ab05792c58 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new ee4602f52d 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new a80c1214da 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new 48b5fd63b3 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 312c2e7090 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 94604a760d 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 30558656b2 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 5d4515b504 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new deb945a077 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new b291fc1e75 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new 479e841216 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new 3dd576168b 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 0fc3d7a3f5 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 5070d144e9 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 42cc43f418 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 754ce92ba4 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 505f883892 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new eb65861598 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 535592bf9e 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new ecd880d924 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new 1c9ea48226 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new 828723d4b4 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 4194ed6f8d 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new b756b850b2 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 9f7d5e1790 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new d634edc348 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new 68e83a3ccf 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new a53eacd219 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 5959de1333 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 9c4f01bb85 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 3d5ecbe4d7 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 685ed993ab 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new 903dd4fbd7 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 313c0bc66d 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 59cc4fe408 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new b4fb8fa593 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new 6b0476a72c 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new b37d67ff1a 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 44463a661c 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new ca0ed74c47 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 01a6f6a615 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 471f71fe3c 89: onsuccess: #864: 1: Success after binutils: 25 commits new bf7847a057 90: onsuccess: #867: 1: Success after binutils: 4 commits new 0e6d3fa84d 91: onsuccess: #870: 1: Success after binutils: 5 commits new 9fb7dafae5 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 7611195a4a 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 814bbfd657 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 91a521cc1b 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new 81e1cedcf1 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 73eb5c691f 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new 56da772439 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new e309ba43b9 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new aa275fb812 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new fa6cc66b2b 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 03e18a364e 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 2bff7ea3b4 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new a769e77959 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 4b10fc542c 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new b640a6f5a8 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new b783bb2990 107: onsuccess: #888: 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 (5e55c844b7) \ 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 1712 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 39464 -> 40100 bytes 04-build_abe-gcc/console.log.xz | Bin 214864 -> 213100 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9460 -> 8560 bytes 07-build_abe-glibc/console.log.xz | Bin 244840 -> 244296 bytes 08-build_abe-gdb/console.log.xz | Bin 39376 -> 38532 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3860 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2428 -> 2032 bytes 11-check_regression/console.log.xz | Bin 16428 -> 13276 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 56 +- 11-check_regression/mail-body.txt | 154 +- 11-check_regression/results.compare | 92 +- 11-check_regression/results.compare2 | 7277 +++++++++++++----------------- 11-check_regression/results.regressions | 92 +- 12-update_baseline/console.log | 62 +- 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 | 156 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 92 +- sumfiles/gdb.log.xz | Bin 1939844 -> 1886188 bytes sumfiles/gdb.sum | 7470 +++++++++---------------------- 30 files changed, 5872 insertions(+), 9627 deletions(-)