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 4af26210b87 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 9257e3fe4fe 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards bebdc1b5cc4 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards e70f43edc8b 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 620fd85b291 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards 1e96977d340 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards ed2147dcfe3 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards 94bd5daa93a 113: onsuccess: #898: 1: Success after linux: 3 commits discards 93e4873d5d8 112: onsuccess: #896: 1: Success after binutils: 24 commits discards ac56cf95374 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards 1e3fcba9726 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards c166368289d 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards 7dcca6e1cf8 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards b687db20685 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 10c30e9004c 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards c642d2b2f9c 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 714a0e929a8 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 93ed892a914 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 8c6965d50a2 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards f6e4e9e56ee 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 031bc3cf665 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards cc3003d4a2d 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 6ab3ec3de76 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] discards da8c3e3871b 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] discards d08012724cd 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] discards a3cd3708eda 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] discards 0fbe10da115 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] discards 0ae56c66eeb 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] discards 593a1a2993c 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] discards 6bc285d94cf 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 9d38e6ee295 90: onsuccess: #867: 1: Success after binutils: 4 commits discards ca80be52b2b 89: onsuccess: #864: 1: Success after binutils: 25 commits discards f1e0fa4e1e7 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] discards 75bc739afec 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] discards fba67b46fdc 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] discards 2e503941278 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] discards a2b877bc31f 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] discards 1e4172ef4e7 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] discards 21fbcf7ffc3 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] discards e902473516c 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards ce9f4a5f7aa 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards c58ee28d934 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards db203aea1ad 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] discards 00b1b3f8b85 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] discards ae1ec42ab50 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] discards 624873089c4 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] discards 1459438ee6f 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] discards 92e230a273c 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] discards ec86efe594e 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] discards 84974f8e23b 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] discards 548d5763709 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] discards 0868ad666bd 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] discards 654cd8bc084 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 603db72123b 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] discards 444f75b3288 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] discards ffdfd0e883a 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 0ff1da21263 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] discards fee5fbe741b 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] discards 3bd7d067a93 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] discards f5f381aaadf 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] discards 4ced5d95f77 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] discards 7cbe0dfd171 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] discards 8635b9b8da2 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] discards 564340684fb 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] discards 2585939c51e 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 79bccb5a67e 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards aad06c8f191 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 914ba0e47b7 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards d2bd1191bf5 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 79e4e0ae2e8 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards b9d71e75db2 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] discards 46e60eedb9e 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 56dfd1f4465 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 62f6b88d42d 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 44c97836cee 46: onsuccess: #818: 1: Success after binutils: 10 commits discards f91b69c2fd8 45: onsuccess: #815: 1: Success after binutils: 6 commits discards b131d25a14e 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards cfb30db6a1a 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] discards 5227568b2cf 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 33ead69701a 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] discards 7e8c8cfb878 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] discards 28d39d4f946 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards a674fc99b3b 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] discards c846d5a59a5 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] discards 0ee8de1bc85 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] discards e518c4a0c03 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 9d8311e3807 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] discards 015f731f3f4 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards c3dc022244f 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 3fa39917346 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] discards b692075d66c 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 3d75752755a 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] discards b1f47703c11 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 01d47178b15 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] discards 5f17d889d92 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] discards 294b52e8637 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 53becd0dbd8 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 8da1fe20776 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] discards 23596e0ee06 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] discards d346315ec3f 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] discards 14635ef32b2 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 9d724c1be1d 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 5f284d0d6d1 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] new b775e8a527a 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] new b25858bf1be 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] new 46ce2168eb1 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 5ebc5be6aad 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new b3a757e503a 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] new a0ae0b4b987 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] new 9271a44c207 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 96349960dad 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] new a26448a710d 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 2a57c42ac93 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] new c7e74e7b23e 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 9e5fb3e978c 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 943a8c52135 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] new f9d70e0df1c 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 6132ba97578 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] new f772fea8f88 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] new 6b95852e74c 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] new 2926f2391ed 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 33fa7383ce1 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] new 581e438c1de 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] new ce95236926d 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new f4954688cb8 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] new d7e1eb0ea70 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 4c280e199f5 45: onsuccess: #815: 1: Success after binutils: 6 commits new a4203360dcf 46: onsuccess: #818: 1: Success after binutils: 10 commits new 2f9dfc8beeb 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new b1e6d9c1455 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 90b27cb5c06 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new edd125336ef 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] new a04bfc6efbd 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new fbf823f2a0a 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new b45d4ddadec 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 63deb501a80 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new e9bdec05789 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new d55b5201618 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new e682e1604c2 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] new c16e1e0d559 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] new c1e46e10a5d 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] new c7ef276a217 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] new 749d83f6904 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] new 2c41b57fedd 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] new 6b31f069318 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] new ee55230920e 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] new ca783be11d8 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new b9d203400b4 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] new 2a8b22dee2f 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] new bdce056d614 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new aaaca6c80b1 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] new f1ff5eb4a0c 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] new c57bf026003 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] new 3854e619c19 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] new 1d90fd36ff7 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] new 1e82d4b6b8c 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] new 57f7bb2f416 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] new 5955b1b223c 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] new ffc511d8dc8 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] new 57eb331657a 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] new 497e23d7071 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 4d49b1b5852 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new d452d10667d 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 523f8b56847 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] new df65491b8d8 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] new 36dedbfd5d0 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] new 0dbcf2e1434 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] new 5a473017cf4 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] new 4d9c2bda4b9 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] new 97509fe0d52 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] new 40ffc9b2c80 89: onsuccess: #864: 1: Success after binutils: 25 commits new 98bf0199157 90: onsuccess: #867: 1: Success after binutils: 4 commits new 08560fb2b2a 91: onsuccess: #870: 1: Success after binutils: 5 commits new ffadbb23fbd 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] new 146386d2ea1 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] new 38e27e9315d 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] new 6fa9c27677f 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] new 4a0cafab124 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] new c09dc9d2d88 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] new 6ec8e6b2228 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new 989c564a518 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new acc05e4d012 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 3d30a88ed55 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 236ec7ea235 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 2cdb2351a38 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new d5024257414 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 30701784059 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 90a2d903ef2 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 897520f62d9 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 4badecb2961 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 73bf7ddd55e 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new ee036961aef 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 7d219d01d47 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 15c28704dc7 112: onsuccess: #896: 1: Success after binutils: 24 commits new adf6f365723 113: onsuccess: #898: 1: Success after linux: 3 commits new 5a77460876d 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 33cabbbd02f 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 5d96a34065f 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new 758e7ae794f 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new 0436a6d429b 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new ebec379df26 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 89dc8463e26 120: onsuccess: #906: 1: Success after binutils: 29 commits new 5f0086d8c85 121: onsuccess: #908: 1: Success after glibc: 2 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 (4af26210b87) \ 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 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 39612 -> 40884 bytes 04-build_abe-gcc/console.log.xz | Bin 213296 -> 216444 bytes 06-build_abe-linux/console.log.xz | Bin 8488 -> 8472 bytes 07-build_abe-glibc/console.log.xz | Bin 244064 -> 244300 bytes 08-build_abe-gdb/console.log.xz | Bin 39024 -> 38936 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3852 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2032 -> 2024 bytes 11-check_regression/console.log.xz | Bin 17144 -> 22700 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 30 +- 11-check_regression/mail-body.txt | 122 +- 11-check_regression/results.compare | 54 +- 11-check_regression/results.compare2 | 2940 +++++++++++- 11-check_regression/results.regressions | 54 +- 12-update_baseline/console.log | 34 +- dashboard/dashboard-generate.sh | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 124 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 54 +- sumfiles/gdb.log.xz | Bin 1843764 -> 1972392 bytes sumfiles/gdb.sum | 7784 ++++++++++++++++++++++++++++++- 26 files changed, 10663 insertions(+), 563 deletions(-)