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_gcc/master-aarch64 in repository toolchain/ci/base-artifacts.
discards 9abf1a930f 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards bcd6aa9016 108: onsuccess: #850: 1: Success after gcc: 2 commits discards db20638946 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 8bffafecd1 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards eabf4df1a2 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards d61cb3aca2 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 2d8d0c6982 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 9a9565e019 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 5d9dc4e6bd 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards e3e61465cd 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards ee24fa3f6c 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards d23eb078d3 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards b2197af255 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 2c4aa0cf99 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 5027b91cfc 95: onsuccess: #835: 1: Success after binutils: 3 commits discards f92daecb5a 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 2248718406 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards fe29028eff 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 5129a46934 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 64d7ac0ed0 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 75ed4e89e4 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards e3690ed1d4 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 0c18f91019 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 56ac5f1fad 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards a9e9467731 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards eede216609 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards a870be6ae6 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 3b11b0d21e 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 52356fedf2 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 9a42989ceb 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards b9feeaf1a3 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 89282f50b3 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 9822481dd7 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 4aad54a61a 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards fa1e3801d1 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 5a025c43e8 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 86960f2c74 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards f1f7f89f05 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 452abe9979 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 3125db3119 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 1e0d6d41a8 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 10a3aacf15 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 8a37ed77b3 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 28ffaa3340 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards fbec24b720 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 007ec65610 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards b55537740e 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 9ebc974652 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 2ac6f3f6db 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 8522ed451c 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards 190dc613a4 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 0cfabf688e 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards f3aa878c8d 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 3d9d71971c 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 080e47f98c 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 34c1548fee 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards f39e4c2405 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 08f4766a55 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards 128532cc5c 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards 34f50a5183 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards b5a8378208 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 1e33d7214d 48: onsuccess: #782: 1: Success after binutils: 8 commits discards dba6ada688 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 7d750e9e21 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards c02992dbef 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards 89cfd9f790 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards e486d6bea1 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards ffcea228cb 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards e012d4f10b 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards 1c4384b4bf 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] discards 97c5c1cf15 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] discards 383986abf6 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] discards f242f82f0b 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] discards 86a29fcbbf 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 4c5bb5c220 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] discards ed7cb1324c 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] discards a2300543c3 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] discards 5265dd40ab 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] discards 9f9ae1abbd 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] discards 904c08e992 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] discards b1612b203b 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] discards 82d1259f59 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] discards ff794f2d9c 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] discards 62e303825e 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] discards 65e1bbb318 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] discards 39d230cb7d 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards e614e29735 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards f107215244 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 01200fe535 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b45ad2460d 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fe5cad9c36 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a91e1058f2 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cce2451f88 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 820bbe8ddd 16: onsuccess: 1: Successful build after binutils: 4 commits discards 620c4d6a2b 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ddf97679b3 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 394776522a 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e0bd16f984 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fdec3a6d01 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5143a2a689 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9abda65c52 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 14e517a884 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 020e53933f 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f19b7f0541 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9c64d821e7 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3d51c353ab 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 29abfcfeda 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e6919d13f2 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fb5eb77360 16: onsuccess: 1: Successful build after binutils: 4 commits new fd9acc9cc4 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a4b9e27e8c 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 10d90dd117 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 83440f0d21 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c51009788b 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b3075a9786 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 9a4800ef47 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 10707a7202 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 95fe11ada6 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] new 45543e6c18 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] new 0d45a682f4 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] new 056a9685a4 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] new 9d982a6dbd 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] new 40a4b3db7b 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] new 47e01716d6 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] new a0eb9590f4 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] new 3d04286749 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] new fd157804c3 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] new e9770ac82d 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] new 4a50c96234 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 6e83c1f1c5 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] new 8afef27606 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] new f41879fd36 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new a8b91012d7 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new d324c77b9f 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new 3bd60ff70a 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new 142b596b3a 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new 9a2c2dc8a3 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new f93d922b27 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 2ba2bce64a 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new 1a6c28c62a 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new 9ed94acc53 48: onsuccess: #782: 1: Success after binutils: 8 commits new b306044904 49: onsuccess: #785: 1: Success after binutils: 12 commits new 6e735a2784 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new 8ead1688b6 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new c46e7eaec4 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new a3f0d8a4f3 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 48d1391179 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 9616716c79 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 4741d7b9c3 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 2ae22612a0 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new d9aee993c2 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 8652610a6d 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 36b9cea829 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new faa18d91a4 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 0d830ac3c5 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 4c425eafc0 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 9113c130a3 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 9b7f5da59b 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new a5817f7135 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 29068dd850 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 84d282ab06 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 09821577c2 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 72ea62c71b 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 1cf9cdc33b 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 30af9242ae 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 04e41c2f89 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 565cb1cf0d 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 7de7e3ccd5 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 011377f788 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 65a5dd0218 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new e64c567383 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new c536862e8c 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new b924e5b6c2 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 507c4fdff7 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new b24a94b628 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new a60a61ca85 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 048fdf9a81 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 65f8facf93 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new cfe127e5f5 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 6b67e69cd3 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 5353b423c2 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 4764da1482 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 7d455ddd09 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 99dcfd3c16 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new ad975ba4a8 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new e605f9d36a 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new be13ed5634 94: onsuccess: #832: 1: Success after binutils: 5 commits new fc24ad80f4 95: onsuccess: #835: 1: Success after binutils: 3 commits new 4f272d27ed 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 64fd92fb1c 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 1476621d1e 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new d35bef84cd 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 71212f8ef3 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 2bf04a9ce9 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 587a307337 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 24fc975ffc 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new da9bacd9d6 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 56d5c493f6 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new fbaa214b4e 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 811c6cf824 107: onsuccess: #849: 1: Success after binutils: 5 commits new 2125151a10 108: onsuccess: #850: 1: Success after gcc: 2 commits new dc3671e94b 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new c40ffad94e 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...]
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 (9abf1a930f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/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 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 39900 -> 40332 bytes 04-build_abe-gcc/console.log.xz | Bin 213668 -> 213256 bytes 06-build_abe-linux/console.log.xz | Bin 9272 -> 8392 bytes 07-build_abe-glibc/console.log.xz | Bin 243764 -> 244092 bytes 08-build_abe-gdb/console.log.xz | Bin 39584 -> 40156 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3840 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2432 -> 2564 bytes 11-check_regression/console.log.xz | Bin 5836 -> 8416 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 8 + 11-check_regression/mail-body.txt | 28 + 11-check_regression/results.compare | 11 +- 11-check_regression/results.compare2 | 321 ++- 11-check_regression/results.regressions | 28 + 12-update_baseline/console.log | 56 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 30 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 28 + sumfiles/g++.log.xz | Bin 3753052 -> 3758720 bytes sumfiles/g++.sum | 42 +- sumfiles/gcc.log.xz | Bin 3315624 -> 3296532 bytes sumfiles/gcc.sum | 4712 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1082516 -> 1076572 bytes sumfiles/gfortran.sum | 205 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2268 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 231788 -> 231692 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 452336 -> 457544 bytes sumfiles/libstdc++.sum | 6 +- 42 files changed, 3080 insertions(+), 2454 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions