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 4ba41f4b6b 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards c439ca5a3a 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards d7944f758d 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 4b8c3a1a9f 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards 71d470d579 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards 0a21d696a7 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 142bf9ed89 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards e9286ccf29 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 7b9f63c134 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards bfdc41f53e 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards ef35ce3ea4 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 14f8093266 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 026791b718 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 5284d8bd21 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards c80bc5b02a 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 4670e00cd1 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards c235004dd6 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards aac6475f94 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards f683c9248c 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards 879d167f00 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 6a4f6c9a76 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards a03aef25e0 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 929372fe15 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards 7d6c8a959a 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 789e726a6c 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards cd774e457d 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards b00b9b675d 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 891cb42639 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards e6ce6e51a2 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards ea8ca43e5d 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 62fb0e71ff 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 061ce0b135 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards dc595cb313 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards fdaaab8016 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 429ecb06e6 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 176a5240d7 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards d3dd7a9001 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 88479ee2db 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 6a4c5492ca 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 58d8a98fbe 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 28565990a5 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 8eaa8206dc 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards 929ff4a9bf 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards 65710defc3 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards 6264f034e6 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards 85a8ec2a40 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 509988900c 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 725f98bb92 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 03901e4fbb 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 6da465229a 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards e5bac98419 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 801641a069 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards 5bb0029571 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards e513571b2d 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards a4f18cb537 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 6ee0bce9ac 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 15709d4cdc 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 8741a65961 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards feba8e80d3 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] discards 7fe7a0967b 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards bb7424703b 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] discards 16e53b70d3 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] discards 21b988c361 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 42168d1ade 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] discards 689808f548 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] discards 61ee23fb22 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] discards c1b873760c 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 2c6fa4bfbe 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] discards 5d933c1399 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 4fbcbd9507 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 00767a68c4 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gli [...] discards 92f5333437 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 3fb57cee23 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gdb [...] discards f6dc43cecb 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 251d271898 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gli [...] discards 6027d731e9 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gdb [...] discards ab95a836b0 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards a6e8c62035 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards d505a45eca 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gdb [...] discards 6bee1cdd2f 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 commits discards 3b705ce61c 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 commits discards 1d4b5c95df 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 21c902b4d3 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c3ebd28fd0 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a178af253b 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 17074fefc5 16: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 74162bb2db 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dda9b394b9 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f5ef66f879 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 63b4c60d20 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9d89175894 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 070adbc710 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e74142e7d9 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 19cee36f22 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 07dec14691 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 78eff10d9c 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 22832059d2 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards a60de4793e 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 3f4a3548f1 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards b3d2b09086 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 3ced2039a4 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 80c53e8bbb 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 3d129c7b13 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 50bc0073df 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new d0228f0945 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 933dc37769 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 5d2b836bba 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 5f079d3637 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 982a69c76e 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a988bf7e49 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a5fa4e6eaa 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 383cbc2072 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 412244dddf 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3e3cb558a6 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b2d8f08caf 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b85968a6ad 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e8f06b98bf 16: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 071d57b4d9 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cd192fd56c 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 601f8133af 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c6500dec7d 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 72d8b73ee3 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 commits new c90ff499d4 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 commits new e747942eb2 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gdb [...] new 158039f1a3 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new be465f5c2f 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 5de6c34e00 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gdb [...] new abbc1134da 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gli [...] new a15e7fb1c9 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 3f9848ea36 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gdb [...] new b6e9dffb6e 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 2a99bd23df 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gli [...] new b31fa866ce 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 8693e0c547 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 4c38ddbada 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] new 4755224520 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new e0e8424e35 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] new 90e3089bda 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] new 28a46abbd1 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] new 1832f4b951 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new ea0f72a60f 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] new b79701fb58 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] new 0ba7632866 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new ff1d29496c 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new ed22546a11 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 8a1dedf047 45: onsuccess: #815: 1: Success after binutils: 6 commits new c7a7e1639e 46: onsuccess: #818: 1: Success after binutils: 10 commits new 00443ed386 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 7c5ec7c297 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new cbf5a5905b 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new e182ba591c 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new bca064a51a 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 6659e8dc64 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 5e060ee0f8 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 239dfd79e6 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 71ef36960b 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 107b80e5d3 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 96780d642c 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new 1e91fcb056 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new b0c58620b4 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 5dd7a66446 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new a054e8484f 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new dfbdab6ca4 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 9a52460ed7 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new bd2f3be73e 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new faac25706a 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new d9b4696311 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new 536e97dc99 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new 200bc3202c 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new 16bb9d0653 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 7ba6bb73d3 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new 9d16d262d1 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 5fec246642 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 2b07e7eff5 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new 224a0c27a0 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 7cb35a8087 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 81a80d8df0 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 04934976fa 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new ec35e7ffaa 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 82da8cc358 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new 5b7c3d8a5f 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new ef1520365b 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new d2dde702b9 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new b2e7aa6b0a 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new 69fce1947e 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new abedefe44b 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 237a911152 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new 70414e1704 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new b32cf201a4 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 98396b0a73 89: onsuccess: #864: 1: Success after binutils: 25 commits new fe17aa4107 90: onsuccess: #867: 1: Success after binutils: 4 commits new 3b0ccbf7c1 91: onsuccess: #870: 1: Success after binutils: 5 commits new 2f99ad83b5 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 7ae7082d6c 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 7d0e42904d 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 7ebd6425cb 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new 56ff40b5e1 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 3d5424e9c3 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new f5fbcdf59a 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new bde6416378 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new d418d5c80e 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 7a963cb462 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new c64cb8f73b 102: onsuccess: #883: 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 (4ba41f4b6b) \ 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 -> 1868 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 40416 -> 39388 bytes 04-build_abe-gcc/console.log.xz | Bin 215344 -> 214924 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9468 -> 8500 bytes 07-build_abe-glibc/console.log.xz | Bin 244096 -> 243212 bytes 08-build_abe-gdb/console.log.xz | Bin 39568 -> 39040 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3872 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2604 -> 2144 bytes 11-check_regression/console.log.xz | Bin 15056 -> 13804 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 34 +- 11-check_regression/mail-body.txt | 160 +- 11-check_regression/results.compare | 75 +- 11-check_regression/results.compare2 | 4225 +++++++++-------- 11-check_regression/results.regressions | 75 +- 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 | 162 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 75 +- sumfiles/gdb.log.xz | Bin 1946888 -> 1960264 bytes sumfiles/gdb.sum | 7880 ++++++++++++++----------------- 30 files changed, 6125 insertions(+), 6651 deletions(-)