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 4e4022aa46d 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 63460a572e4 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards e9a0445fa48 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 7f0ae07f194 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards 9bd6235af67 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards 29e38151330 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards 638f8ba9ed5 113: onsuccess: #898: 1: Success after linux: 3 commits discards ebe6d6c4502 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 3576a0ac107 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards d17ac1e6780 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 91677603d8c 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards 6f49114aabe 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 3adb27c2cca 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards cd78b4c0fd2 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards af5cda71c92 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 3925d352a97 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 179eedfeaf8 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 7d60cd193cd 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards a77ca1c1b99 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 49a4f565176 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 249e637bc97 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards d11fbf43c27 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] discards 3823859f38d 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] discards 6614d01fdc4 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] discards 9205dcbb325 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] discards 3a76aa12894 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] discards 12b00034766 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] discards e102b92447b 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] discards d94737ed337 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 87d096b0fa4 90: onsuccess: #867: 1: Success after binutils: 4 commits discards d2d53cfde0d 89: onsuccess: #864: 1: Success after binutils: 25 commits discards ee254b81b16 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] discards 71a717ed979 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] discards 79bbcf55c67 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] discards 5d1df18d11c 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] discards e574a236d29 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] discards ae297a0da72 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] discards 062173cabf0 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] discards 3e4c35d17de 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 2fba8e9a37b 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 178c61177f2 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 9691215959c 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] discards 3653213ad8d 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] discards b9e3cfa7f27 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] discards 485b0ac53c2 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] discards c77c5585599 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] discards f42c1547c06 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] discards 55210b7eeb0 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] discards 32f8caa337a 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] discards 93b58de014f 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] discards e22402e0460 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] discards ac57123f297 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 30be0587ee9 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] discards a2093589220 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] discards 10e23afa9b4 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 910835c03b1 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] discards 08c433d0427 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] discards 6ce2a019f40 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] discards 757a61a7b20 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] discards f016c4461d7 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] discards a6cfb6fc576 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] discards 62d85943a5b 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] discards 547708ecf14 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] discards be7ded638e8 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 547ac092b61 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 309abbf5435 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards eca03ca748c 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards dbc50f2e784 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards ebc6748a88f 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 390602f40c9 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] discards 036f6f0250e 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 7ce52ccba86 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards db565b2bb30 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 5d2402ded33 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 4db3d31d60c 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 889cab2623e 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 34828040848 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] discards 321255b304c 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards cdf6bb5faca 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] discards cbac6fd6b8a 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] discards cf9c93c5363 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 553dc5b93d6 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] discards 7f5ec853dfc 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] discards 7d6bcd35291 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] discards 45a2c2d5726 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards ad714522bec 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] discards e1bb70ce2ec 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 84f9fbbdfb2 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 6502b326fb4 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] discards 07c9bbdbb73 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards f87aabee4e6 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] discards 3d6ff43e380 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards a11b776d37a 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] discards 0f3bafe4c2a 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] discards 69eb417f080 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 91d0d3909de 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 5565fcc6877 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] discards c06ae3c4b46 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] discards 86c8fa8e667 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] discards ae0b12a91c5 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards dd1d1eaae8a 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 9d512b00cd1 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 14635ef32b2 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new d346315ec3f 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] new 23596e0ee06 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] new 8da1fe20776 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] new 53becd0dbd8 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 294b52e8637 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 5f17d889d92 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] new 01d47178b15 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] new b1f47703c11 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 3d75752755a 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] new b692075d66c 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 3fa39917346 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] new c3dc022244f 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 015f731f3f4 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 9d8311e3807 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] new e518c4a0c03 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 0ee8de1bc85 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] new c846d5a59a5 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] new a674fc99b3b 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] new 28d39d4f946 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 7e8c8cfb878 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] new 33ead69701a 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] new 5227568b2cf 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new cfb30db6a1a 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] new b131d25a14e 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new f91b69c2fd8 45: onsuccess: #815: 1: Success after binutils: 6 commits new 44c97836cee 46: onsuccess: #818: 1: Success after binutils: 10 commits new 62f6b88d42d 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 56dfd1f4465 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 46e60eedb9e 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new b9d71e75db2 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] new 79e4e0ae2e8 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new d2bd1191bf5 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 914ba0e47b7 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new aad06c8f191 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 79bccb5a67e 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 2585939c51e 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 564340684fb 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] new 8635b9b8da2 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] new 7cbe0dfd171 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] new 4ced5d95f77 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] new f5f381aaadf 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] new 3bd7d067a93 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] new fee5fbe741b 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] new 0ff1da21263 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] new ffdfd0e883a 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 444f75b3288 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] new 603db72123b 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] new 654cd8bc084 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 0868ad666bd 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] new 548d5763709 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] new 84974f8e23b 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] new ec86efe594e 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] new 92e230a273c 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] new 1459438ee6f 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] new 624873089c4 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] new ae1ec42ab50 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] new 00b1b3f8b85 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] new db203aea1ad 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] new c58ee28d934 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new ce9f4a5f7aa 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new e902473516c 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 21fbcf7ffc3 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] new 1e4172ef4e7 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] new a2b877bc31f 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] new 2e503941278 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] new fba67b46fdc 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] new 75bc739afec 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] new f1e0fa4e1e7 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] new ca80be52b2b 89: onsuccess: #864: 1: Success after binutils: 25 commits new 9d38e6ee295 90: onsuccess: #867: 1: Success after binutils: 4 commits new 6bc285d94cf 91: onsuccess: #870: 1: Success after binutils: 5 commits new 593a1a2993c 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] new 0ae56c66eeb 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] new 0fbe10da115 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] new a3cd3708eda 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] new d08012724cd 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] new da8c3e3871b 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] new 6ab3ec3de76 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new cc3003d4a2d 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 031bc3cf665 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new f6e4e9e56ee 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 8c6965d50a2 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 93ed892a914 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 714a0e929a8 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new c642d2b2f9c 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 10c30e9004c 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new b687db20685 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 7dcca6e1cf8 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new c166368289d 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new 1e3fcba9726 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new ac56cf95374 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 93e4873d5d8 112: onsuccess: #896: 1: Success after binutils: 24 commits new 94bd5daa93a 113: onsuccess: #898: 1: Success after linux: 3 commits new ed2147dcfe3 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 1e96977d340 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 620fd85b291 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new e70f43edc8b 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new bebdc1b5cc4 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 9257e3fe4fe 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 4af26210b87 120: onsuccess: #906: 1: Success after binutils: 29 commits

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 (4e4022aa46d) \ 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 1748 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39156 -> 39612 bytes 04-build_abe-gcc/console.log.xz | Bin 213120 -> 213296 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8296 -> 8488 bytes 07-build_abe-glibc/console.log.xz | Bin 243504 -> 244064 bytes 08-build_abe-gdb/console.log.xz | Bin 38984 -> 39024 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2132 -> 2032 bytes 11-check_regression/console.log.xz | Bin 9056 -> 17144 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 43 +- 11-check_regression/mail-body.txt | 134 +- 11-check_regression/results.compare | 72 +- 11-check_regression/results.compare2 | 4165 +++++++++++++- 11-check_regression/results.regressions | 72 +- 12-update_baseline/console.log | 42 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 136 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 72 +- sumfiles/gdb.log.xz | Bin 1907924 -> 1843764 bytes sumfiles/gdb.sum | 9520 +++++++------------------------ 27 files changed, 6546 insertions(+), 7746 deletions(-)