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 0ce2c3e0a4 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards ea63aa2da4 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 1be540b80d 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards b0eac0901e 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards c8d342bf0e 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 5467cc2f0c 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards c2b75c2dba 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 78281c27c9 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 9a2700da3d 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards b9a970d2b7 91: onsuccess: #870: 1: Success after binutils: 5 commits discards cd9a74c933 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 00a4463ec7 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 19216daec9 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards 08d9a0c730 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 6fac315511 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards 4e6d0cd82d 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards 17e3119502 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 51d615d2ac 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards 6f4bac7569 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards dc9e08359f 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards e4399422a0 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards fc54faea84 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards a1aa110ff6 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards a8fea98cfd 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards e23efc1178 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards c78d7d4b30 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 619a1e06e2 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 31865ed3d3 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 8216597cab 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 11fe78d28b 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 25e88dad0a 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards 7fd5055771 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards 664b434fa8 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 7c6603bd13 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 387b839d7d 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards 645c3f14fb 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 731a20cd3a 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards e7fd31b070 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 75d54aa2f5 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 44917dec87 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 8b73d5fcd2 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards 939af40ee8 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards a1ec40d400 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards 47bd5a77b2 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards defc769414 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 8c7a26b26b 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 8d668f8821 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 4a333928cb 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 121dd2c060 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 100a5305d4 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 7bf4c06e0e 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards 121e176570 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 353f2c70f9 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards f5999a488d 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 643c47daec 46: onsuccess: #818: 1: Success after binutils: 10 commits discards a01c49f503 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 4b88ebecc0 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards fd428a333c 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] discards def41406b5 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards aee1131fc1 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] discards 3613bfb7f1 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] discards 70411fab2c 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 371702888c 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] discards cee5fc89e9 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] discards 220b699171 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] discards 82c0dcd1f1 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 0d12ab0f14 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] discards 293ea44d97 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 3fcb6f2d47 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 3c004e0c1b 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gli [...] discards 9972d77533 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 745502011f 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gdb [...] discards 360afd2a6a 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 86ab74c083 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gli [...] discards bf4e4ca20d 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gdb [...] discards 9d9cdf12fb 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 2f861d84e8 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards bb740053be 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gdb [...] discards 613651fbe7 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 commits discards 17b2600124 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 commits discards 9f035b8ae7 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards fe101efa4c 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 29fdfc1fde 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 47b85d6024 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e449b7c4bd 16: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7d1a9268f4 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6f40a0af21 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 563127ec21 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d578a38c37 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bf09e5434e 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fb62460fb6 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8309b855df 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 404489d8c1 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a22bf65e28 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 166ee42ea0 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards cec24a45a5 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 87f69bcb2c 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 64f8972077 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 919d7af760 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards dfbb308679 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 13fc7bd1a2 0: update: binutils-gcc-linux-glibc-gdb: 1 new 412ca146c5 0: update: binutils-gcc-linux-glibc-gdb: 1 new 3ced2039a4 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new b3d2b09086 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 3f4a3548f1 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new a60de4793e 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 22832059d2 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 78eff10d9c 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 07dec14691 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 19cee36f22 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e74142e7d9 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 070adbc710 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9d89175894 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 63b4c60d20 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f5ef66f879 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new dda9b394b9 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 74162bb2db 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 17074fefc5 16: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a178af253b 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c3ebd28fd0 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 21c902b4d3 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1d4b5c95df 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 3b705ce61c 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 commits new 6bee1cdd2f 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 commits new d505a45eca 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gdb [...] new a6e8c62035 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new ab95a836b0 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 6027d731e9 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gdb [...] new 251d271898 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gli [...] new f6dc43cecb 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 3fb57cee23 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gdb [...] new 92f5333437 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 00767a68c4 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gli [...] new 4fbcbd9507 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 5d933c1399 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 2c6fa4bfbe 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] new c1b873760c 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 61ee23fb22 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] new 689808f548 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] new 42168d1ade 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] new 21b988c361 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 16e53b70d3 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] new bb7424703b 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] new 7fe7a0967b 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new feba8e80d3 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new 8741a65961 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 15709d4cdc 45: onsuccess: #815: 1: Success after binutils: 6 commits new 6ee0bce9ac 46: onsuccess: #818: 1: Success after binutils: 10 commits new a4f18cb537 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new e513571b2d 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 5bb0029571 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 801641a069 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new e5bac98419 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 6da465229a 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 03901e4fbb 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 725f98bb92 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 509988900c 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 85a8ec2a40 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 6264f034e6 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new 65710defc3 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new 929ff4a9bf 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 8eaa8206dc 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 28565990a5 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 58d8a98fbe 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 6a4c5492ca 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 88479ee2db 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new d3dd7a9001 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 176a5240d7 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new 429ecb06e6 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new fdaaab8016 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new dc595cb313 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 061ce0b135 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new 62fb0e71ff 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new ea8ca43e5d 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new e6ce6e51a2 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new 891cb42639 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new b00b9b675d 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new cd774e457d 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 789e726a6c 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 7d6c8a959a 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 929372fe15 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new a03aef25e0 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 6a4f6c9a76 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 879d167f00 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new f683c9248c 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new aac6475f94 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new c235004dd6 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 4670e00cd1 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new c80bc5b02a 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 5284d8bd21 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 026791b718 89: onsuccess: #864: 1: Success after binutils: 25 commits new 14f8093266 90: onsuccess: #867: 1: Success after binutils: 4 commits new ef35ce3ea4 91: onsuccess: #870: 1: Success after binutils: 5 commits new bfdc41f53e 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 7b9f63c134 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new e9286ccf29 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 142bf9ed89 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new 0a21d696a7 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 71d470d579 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new 4b8c3a1a9f 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new d7944f758d 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new c439ca5a3a 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 4ba41f4b6b 101: onsuccess: #882: 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 (0ce2c3e0a4) \ 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 1684 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 39212 -> 40416 bytes 04-build_abe-gcc/console.log.xz | Bin 215180 -> 215344 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8532 -> 9468 bytes 07-build_abe-glibc/console.log.xz | Bin 243204 -> 244096 bytes 08-build_abe-gdb/console.log.xz | Bin 39000 -> 39568 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3856 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2048 -> 2604 bytes 11-check_regression/console.log.xz | Bin 8684 -> 15056 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 41 +- 11-check_regression/mail-body.txt | 165 +- 11-check_regression/results.compare | 85 +- 11-check_regression/results.compare2 | 3858 ++++++++++++++-- 11-check_regression/results.regressions | 85 +- 12-update_baseline/console.log | 40 + 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 | 167 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 85 +- sumfiles/gdb.log.xz | Bin 1960716 -> 1946888 bytes sumfiles/gdb.sum | 7682 +++++++++---------------------- 30 files changed, 6099 insertions(+), 6159 deletions(-)