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 c64cb8f73b 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 7a963cb462 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards d418d5c80e 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards bde6416378 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards f5fbcdf59a 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards 3d5424e9c3 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards 56ff40b5e1 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 7ebd6425cb 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 7d0e42904d 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 7ae7082d6c 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 2f99ad83b5 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 3b0ccbf7c1 91: onsuccess: #870: 1: Success after binutils: 5 commits discards fe17aa4107 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 98396b0a73 89: onsuccess: #864: 1: Success after binutils: 25 commits discards b32cf201a4 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards 70414e1704 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 237a911152 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards abedefe44b 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards 69fce1947e 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards b2e7aa6b0a 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards d2dde702b9 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards ef1520365b 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards 5b7c3d8a5f 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 82da8cc358 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards ec35e7ffaa 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 04934976fa 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 81a80d8df0 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 7cb35a8087 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 224a0c27a0 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 2b07e7eff5 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 5fec246642 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 9d16d262d1 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 7ba6bb73d3 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards 16bb9d0653 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards 200bc3202c 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 536e97dc99 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards d9b4696311 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards faac25706a 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards bd2f3be73e 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 9a52460ed7 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards dfbdab6ca4 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards a054e8484f 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 5dd7a66446 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards b0c58620b4 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards 1e91fcb056 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards 96780d642c 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards 107b80e5d3 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 71ef36960b 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 239dfd79e6 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 5e060ee0f8 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 6659e8dc64 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards bca064a51a 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards e182ba591c 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards cbf5a5905b 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 7c5ec7c297 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 00443ed386 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards c7a7e1639e 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 8a1dedf047 45: onsuccess: #815: 1: Success after binutils: 6 commits discards ed22546a11 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards ff1d29496c 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] discards 0ba7632866 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards b79701fb58 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] discards ea0f72a60f 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] discards 1832f4b951 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 28a46abbd1 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] discards 90e3089bda 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] discards e0e8424e35 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] discards 4755224520 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 4c38ddbada 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] discards 8693e0c547 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards b31fa866ce 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 2a99bd23df 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gli [...] discards b6e9dffb6e 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 3f9848ea36 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gdb [...] discards a15e7fb1c9 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards abbc1134da 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gli [...] discards 5de6c34e00 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gdb [...] discards be465f5c2f 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 158039f1a3 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards e747942eb2 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gdb [...] discards c90ff499d4 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 commits discards 72d8b73ee3 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 commits discards c6500dec7d 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 601f8133af 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cd192fd56c 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 071d57b4d9 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e8f06b98bf 16: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b85968a6ad 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b2d8f08caf 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3e3cb558a6 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 412244dddf 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 383cbc2072 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a5fa4e6eaa 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a988bf7e49 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 982a69c76e 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5f079d3637 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 5d2b836bba 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 933dc37769 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards d0228f0945 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 50bc0073df 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 3d129c7b13 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new e9bfd41982 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new c7ae72253f 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new b9984df9f3 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 8311cfe71c 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 3da6f87c58 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 81826cdbbb 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new c24a80f7e3 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b67b9b9292 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2cffaea3bc 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new dd92aab549 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 922701312c 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1d0fd60368 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bbbb9f88fc 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4e34bdd4a7 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0d4a21b739 16: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 52f34f049a 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e71a259631 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4bead6a1f1 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c12eb70a37 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new b5ecde8d03 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 commits new d4001cf451 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 commits new 63f6f67aba 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gdb [...] new 41850eb8eb 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new a7dc0be315 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 3299c3632c 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gdb [...] new 89ea0ba10e 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gli [...] new 27cd634760 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 0d39790fb2 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gdb [...] new 8de8924fcf 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new d800f5026e 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gli [...] new c41b541130 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 3113c1ef8e 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 9b553a4ee9 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] new d3c49a38b1 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 193a409445 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] new 32a2b9e059 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] new 54befb6c15 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] new c83003eed9 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 9591d0bc79 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] new ff59dc4453 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] new 0ef9cf7518 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 2a64d677bc 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new 0dc3526f61 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new cb3c68f51d 45: onsuccess: #815: 1: Success after binutils: 6 commits new e9514c6dfc 46: onsuccess: #818: 1: Success after binutils: 10 commits new bd1415ed79 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new a9680d427a 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new b8b0373ba7 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 5ee9f7c7f1 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new c9a3e67b4c 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 766871ca0b 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new ecd1077eb9 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 7768251f14 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 9931a9cd76 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new c37337a3d1 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new b291b2bb91 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new 28a8e3a8ed 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new b48f656bb4 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new bcfa2c4ff4 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new f192488dde 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 7951b0663b 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 9e9ac5adc4 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 052b87fef1 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new 1ab82a2136 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new cc18c11327 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new c1eff0722c 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new c65cd87cdf 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new a9ce0a7424 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 0247f62103 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new 23b3be85b5 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 2b9f2c0cc0 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 870779c9ab 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new 57f44d123d 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new f6ac0e6a64 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 4b417e87ed 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 5c890e2443 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 6d9fd679d5 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 75a2999b12 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new ee16fabed9 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 537691bc5a 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new f4872e2a96 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new c794f38c3b 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new 4f5a103149 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new cf59a34cb3 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 082ebaa733 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new d729771c05 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 56850db3b1 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new aacde7d407 89: onsuccess: #864: 1: Success after binutils: 25 commits new b92e0a7854 90: onsuccess: #867: 1: Success after binutils: 4 commits new 210d357159 91: onsuccess: #870: 1: Success after binutils: 5 commits new 944a2f0550 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new ca21b8d614 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 1f1f9c8334 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new e7f8efcee5 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new 080525b284 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 8a00005727 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new f6cea5a500 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 4a615b9397 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 91e9d0df2e 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new e050d37966 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new c54e836966 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new fd9d421ae6 103: onsuccess: #884: 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 (c64cb8f73b) \ 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 1868 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 39388 -> 39312 bytes 04-build_abe-gcc/console.log.xz | Bin 214924 -> 212764 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8500 -> 8564 bytes 07-build_abe-glibc/console.log.xz | Bin 243212 -> 243600 bytes 08-build_abe-gdb/console.log.xz | Bin 39040 -> 38872 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3832 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2144 -> 2024 bytes 11-check_regression/console.log.xz | Bin 13804 -> 11820 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 27 +- 11-check_regression/mail-body.txt | 143 +- 11-check_regression/results.compare | 68 +- 11-check_regression/results.compare2 | 3389 ++++++--------- 11-check_regression/results.regressions | 68 +- 12-update_baseline/console.log | 44 +- 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 | 145 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 68 +- sumfiles/gdb.log.xz | Bin 1960264 -> 1878280 bytes sumfiles/gdb.sum | 6791 ++++++++++++------------------- 30 files changed, 3993 insertions(+), 6798 deletions(-)