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 a8f0b471d8b 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards adad5d1f90b 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards bece1d8f55b 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards db517bafeb6 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards 39cced6f3c7 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards f9201ee87cd 113: onsuccess: #898: 1: Success after linux: 3 commits discards 8929eb22386 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 24e033176b4 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards e092c2035e9 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 9cee59df8a9 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards b1ea62d8fa0 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 2334c6c7e01 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards f10dc9e3da4 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 440cf464712 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 3a245f0519f 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 7947fff0b82 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 69b0ebd33f7 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards fd3fac4b326 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 8bcd2fdcb37 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards bccea8976e4 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 1bacfb2c2e5 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] discards 3c24fbb22fc 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] discards dc460c3d544 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] discards 45a56708fc5 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] discards cea4acff3a5 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] discards c9dfb823b73 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] discards 6364313562b 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] discards 9718cfeb7be 91: onsuccess: #870: 1: Success after binutils: 5 commits discards c7621f82bf3 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 8f386e5a2f9 89: onsuccess: #864: 1: Success after binutils: 25 commits discards a35d11b83ad 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] discards 0d4626fb18e 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] discards 49211ff3363 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] discards 795b600fc54 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] discards 5591b7aace9 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] discards a63f0cb649a 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] discards 8a99567a507 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] discards 2399a05a484 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 8f89233b32c 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 9f6bf3a1e50 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 4964474ee48 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] discards 37d8e74f000 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] discards 6d57f2e77e8 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] discards e31451503a0 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] discards d05e961af83 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] discards 6e6376913fc 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] discards cba56b89270 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] discards 0ed9c343b7d 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] discards 203c1eccf41 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] discards 8a608d68d0f 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] discards 63e119564ef 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 9b1bbd1b6a5 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] discards c90c29caada 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] discards 9e0d520dc46 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards e74abb1d895 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] discards 5118edb5f4b 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] discards 7c5c0799776 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] discards 9a27aa6d7f1 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] discards 0a64edd383e 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] discards 10859d6c0e4 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] discards a767e695992 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] discards 01029e04024 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] discards ccf9868b4ef 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards ed7ef0d8ac0 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 87726b1c61e 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards e59115382da 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards c01383bebd9 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards f4ca5f6914b 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards eb60b64964f 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] discards cc5bb032c74 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards c6f6dcdaa2d 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 2ca60b64df5 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards b2d0905f982 46: onsuccess: #818: 1: Success after binutils: 10 commits discards dc4e9c0c2d8 45: onsuccess: #815: 1: Success after binutils: 6 commits discards fd1a45cccf4 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards be57e7e7148 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] discards 04ae5ca8641 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 89ec3424f31 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] discards e92c53aeb4c 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] discards dad32ae933d 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 4e4b1c02a3a 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] discards ca2c408aebf 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] discards b6e5c96b268 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] discards fd4c8b50017 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards d6eea6a46c1 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] discards 0645552dc4b 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 25469902132 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 73fd5447718 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] discards e632732dd51 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 850c2950abb 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] discards 04c8a7b58e9 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 0e2854a94d5 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] discards 8b06e9b6740 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] discards 0b32557e8a4 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 8d7e07d66b2 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 2396c62d0f0 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] discards a92c629bce0 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] discards 0857af93735 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] discards 4ad5d71b77a 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 6e846e9aa51 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 9339caed597 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 7dcc028a887 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new dd1d1eaae8a 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new ae0b12a91c5 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 86c8fa8e667 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] new c06ae3c4b46 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] new 5565fcc6877 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] new 91d0d3909de 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 69eb417f080 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 0f3bafe4c2a 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] new a11b776d37a 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] new 3d6ff43e380 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new f87aabee4e6 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] new 07c9bbdbb73 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 6502b326fb4 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] new 84f9fbbdfb2 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new e1bb70ce2ec 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new ad714522bec 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] new 45a2c2d5726 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 7d6bcd35291 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] new 7f5ec853dfc 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] new 553dc5b93d6 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] new cf9c93c5363 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new cbac6fd6b8a 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] new cdf6bb5faca 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] new 321255b304c 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 34828040848 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] new 889cab2623e 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 4db3d31d60c 45: onsuccess: #815: 1: Success after binutils: 6 commits new 5d2402ded33 46: onsuccess: #818: 1: Success after binutils: 10 commits new db565b2bb30 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 7ce52ccba86 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 036f6f0250e 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 390602f40c9 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] new ebc6748a88f 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new dbc50f2e784 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new eca03ca748c 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 309abbf5435 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 547ac092b61 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new be7ded638e8 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 547708ecf14 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] new 62d85943a5b 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] new a6cfb6fc576 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] new f016c4461d7 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] new 757a61a7b20 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] new 6ce2a019f40 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] new 08c433d0427 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] new 910835c03b1 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] new 10e23afa9b4 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new a2093589220 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] new 30be0587ee9 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] new ac57123f297 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new e22402e0460 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] new 93b58de014f 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] new 32f8caa337a 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] new 55210b7eeb0 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] new f42c1547c06 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] new c77c5585599 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] new 485b0ac53c2 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] new b9e3cfa7f27 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] new 3653213ad8d 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] new 9691215959c 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] new 178c61177f2 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 2fba8e9a37b 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 3e4c35d17de 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 062173cabf0 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] new ae297a0da72 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] new e574a236d29 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] new 5d1df18d11c 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] new 79bbcf55c67 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] new 71a717ed979 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] new ee254b81b16 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] new d2d53cfde0d 89: onsuccess: #864: 1: Success after binutils: 25 commits new 87d096b0fa4 90: onsuccess: #867: 1: Success after binutils: 4 commits new d94737ed337 91: onsuccess: #870: 1: Success after binutils: 5 commits new e102b92447b 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] new 12b00034766 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] new 3a76aa12894 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] new 9205dcbb325 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] new 6614d01fdc4 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] new 3823859f38d 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] new d11fbf43c27 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new 249e637bc97 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 49a4f565176 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new a77ca1c1b99 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 7d60cd193cd 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 179eedfeaf8 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 3925d352a97 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new af5cda71c92 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new cd78b4c0fd2 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 3adb27c2cca 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 6f49114aabe 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 91677603d8c 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new d17ac1e6780 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 3576a0ac107 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new ebe6d6c4502 112: onsuccess: #896: 1: Success after binutils: 24 commits new 638f8ba9ed5 113: onsuccess: #898: 1: Success after linux: 3 commits new 29e38151330 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 9bd6235af67 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 7f0ae07f194 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new e9a0445fa48 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new 63460a572e4 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 4e4022aa46d 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...]

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 (a8f0b471d8b) \ 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 1736 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 39596 -> 39156 bytes 04-build_abe-gcc/console.log.xz | Bin 214268 -> 213120 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8736 -> 8296 bytes 07-build_abe-glibc/console.log.xz | Bin 242868 -> 243504 bytes 08-build_abe-gdb/console.log.xz | Bin 38960 -> 38984 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3836 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2120 -> 2132 bytes 11-check_regression/console.log.xz | Bin 20512 -> 9056 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 25 +- 11-check_regression/mail-body.txt | 123 +- 11-check_regression/results.compare | 62 +- 11-check_regression/results.compare2 | 5940 ++----------------------------- 11-check_regression/results.regressions | 62 +- 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 | 125 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 62 +- sumfiles/gdb.log.xz | Bin 1847748 -> 1907924 bytes sumfiles/gdb.sum | 5613 ++++++++++++++++++----------- 30 files changed, 4068 insertions(+), 8052 deletions(-)