Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-norov-allmodconfig updated (70f1ada254 -> 8a993566a6)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-norov-allmodconfig in repository toolchain/ci/base-artifacts. from 70f1ada254 10: onsuccess: #38: 33: Success after binutils/gcc/qemu: 95 commits new 8a993566a6 11: onsuccess: #39: 33: Success after binutils/gcc/linux/qem [...] The 1 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 1712 -> 1940 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 29956 -> 32196 bytes 04-build_abe-stage1/console.log.xz | Bin 90928 -> 90192 bytes 05-build_abe-qemu/console.log.xz | Bin 31748 -> 31176 bytes 06-build_linux/console.log.xz | Bin 5012 -> 4880 bytes 08-check_regression/console.log.xz | Bin 2860 -> 4448 bytes 09-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 31 ++++++++++++++++--------------- 17 files changed, 33 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (6cf93a4feb -> 5d6475c55f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards 6cf93a4feb 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 3744ea3649 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards ab91e4b90f 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 5c1146216a 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 2a12462e9c 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 8e1398106c 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 8ef15db9ba 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 5edc62e084 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 6f0a0b9446 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 70b3063a31 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 210deb0d8a 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 69d9f93d35 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 2eba566b54 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards cac44c0077 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards c655dad470 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards dda2bfc9db 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards ace8fdd154 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards e04b33fd10 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards b16a78a43a 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 598a8fc9a6 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 27a2df9661 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 46090094ff 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 4dd3ae9783 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards fb2259f5c9 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards ea8feb0dc2 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards faed20e4e3 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 1aa99a1df9 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards b9fa43af76 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 9ca037e35b 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards b4391ae683 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards f1930121b7 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2f9624dcf5 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 3aca5cb934 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 2d85a3bbe7 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards fc8975484a 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards cbee85da6f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 5ead184d63 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 1b5b575c9b 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 01a4526e55 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 607d8be8be 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 7b659a6dc6 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards cd79f331a9 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 463c2415a2 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 04f433d638 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 168df31197 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards b85b0e3c0d 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 40d2110431 74: onsuccess: 1: Successful build after linux: 44 commits discards cbc1cb86e2 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 51a65f1885 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1bbf45f942 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards bbdd4f8eff 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 76e869f38d 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards c89ffff3a8 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d29b2b9a48 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5bd301bc33 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d2c9f51647 65: onsuccess: 1: Successful build after gcc: 4 commits discards a513d5cbcd 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0d292a008f 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 121aee6731 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 3f73fbdf99 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 2ce99b79df 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 993cb72303 59: onsuccess: 1: Successful build after glibc: 2 commits discards 57c6c1285a 58: onsuccess: 1: Successful build after binutils: 2 commits discards ce67293d4e 57: onsuccess: 1: Successful build after gcc: 7 commits discards e806de8a9a 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2c962715d3 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 68b0edb93d 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 20c2afa76a 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 9b4148e59d 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 112951b067 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ddee9d5821 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6379d45be9 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards da86da5704 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards d1543f6f77 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d57c27aff5 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards f4ec3fd84a 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8e0a1c2a82 44: onsuccess: 1: Successful build after linux: 34 commits discards 6e11926588 43: onsuccess: 1: Successful build after gcc: 2 commits discards a8d8faccf2 42: onsuccess: 1: Successful build after baseline build: no [...] discards 81ef9bd520 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c539472f53 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 790984d2df 39: onsuccess: 1: Successful build after gcc: 2 commits discards e472062a92 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c80680021c 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 659e8c9906 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 45451b5cdf 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c4e0195e55 34: onsuccess: 1: Successful build after gcc: 3 commits discards d955523345 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a2cd69e24a 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards b7f13cc06e 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards cfd427be33 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards f68ae2c1e0 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 59b14e1099 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards f0a438f08d 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5e5f3b1e3e 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 76af08d71a 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b9998e2af6 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6e855d2211 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b5d3969c9e 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 66aeb1d4f7 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9a007a697d 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ab546fb047 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5ef61bd60c 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 41cb28991c 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3ab0a9609d 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4a53f58c12 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d5d0928409 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 124cdba344 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4c133ed4ce 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 5f7ea2341a 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new ecac602032 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d8c4354ab9 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new c833845c65 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0ff8671492 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 571978ee12 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1ff6426099 34: onsuccess: 1: Successful build after gcc: 3 commits new f104ba6333 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3c74e9b921 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2e4944952a 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 89e91bbb89 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2457adf8ea 39: onsuccess: 1: Successful build after gcc: 2 commits new 87fdbeb9c5 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 21feff93c8 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d194034f4f 42: onsuccess: 1: Successful build after baseline build: no [...] new 60f5e63d05 43: onsuccess: 1: Successful build after gcc: 2 commits new d6ea50e69a 44: onsuccess: 1: Successful build after linux: 34 commits new c5f0a48026 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e86dd47a7e 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new c7b6ef3efa 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 48e9c64a9c 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 811969b231 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 64a876f04c 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4fbd438766 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 8d90c5a361 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new d57bbd87d5 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new ff9f5748ae 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 77916ccf3d 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7f6b0630ed 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bcc6b43c68 57: onsuccess: 1: Successful build after gcc: 7 commits new 116b5b8354 58: onsuccess: 1: Successful build after binutils: 2 commits new 380ddf4dd0 59: onsuccess: 1: Successful build after glibc: 2 commits new 48d089131e 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new eb6e1ad31b 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 72d95dbbe4 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 8851ea5153 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 31f45b1297 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d06e2643fe 65: onsuccess: 1: Successful build after gcc: 4 commits new cf31c7f78b 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new caf38f49ff 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3de7e02883 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 66a33e7cfd 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 5a23d1837c 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 37fd8a2758 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 46b674f4f2 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1524c123d5 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 1e7add6298 74: onsuccess: 1: Successful build after linux: 44 commits new fc30297416 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 10a8a1d168 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 051cb33928 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9c9ef65e5e 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 980a418e0a 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 3197963920 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 93387a15eb 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 0cd1e8b652 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 5a6adaa3ce 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new aad082b030 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 2aba92347f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new e0a7643bb4 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new c72faf8b42 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 1d979bd027 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new dc149f046a 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 3b5f0e7710 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 83d6addc9c 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new c70aeb9fa3 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new e158ba75d5 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 2a58e55a10 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 1e349ba238 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 429a1b3acc 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new a2173b3685 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new ac3c1521f3 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new d248acae62 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new e58ddd0aaa 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new ffc26f858b 101: onsuccess: #1693: 1: Success after glibc: 14 commits new c30657b383 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 5cfd242dfd 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new cb0843bb75 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 344492181a 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 9ed26614d5 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new f5b06f8877 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 26e0bcbb28 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 6586f883b0 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new eac536b4f4 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 36c48241d6 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new a3b1e74257 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 58177afed8 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new a8a5c7b274 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 9a52f4d367 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new d1494b368b 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 26e4ef8aac 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 71ec2b256a 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new f78c47a01b 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 95ee0fc2b2 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 5d6475c55f 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] 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 (6cf93a4feb) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] 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 1700 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 31136 -> 30104 bytes 04-build_abe-stage1/console.log.xz | Bin 91220 -> 91000 bytes 06-build_abe-linux/console.log.xz | Bin 9264 -> 8572 bytes 07-build_abe-glibc/console.log.xz | Bin 234064 -> 233576 bytes 08-build_abe-stage2/console.log.xz | Bin 225256 -> 223740 bytes 09-build_abe-gdb/console.log.xz | Bin 38260 -> 37248 bytes 10-build_abe-qemu/console.log.xz | Bin 31348 -> 31108 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3844 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2624 -> 2780 bytes 13-check_regression/console.log.xz | Bin 6456 -> 6736 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 14 + 13-check_regression/results.compare2 | 178 +-- 14-update_baseline/console.log | 66 +- 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 | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 43 +- sumfiles/g++.log.xz | Bin 2684556 -> 2677476 bytes sumfiles/g++.sum | 45 +- sumfiles/gcc.log.xz | Bin 2216340 -> 2212280 bytes sumfiles/gcc.sum | 2304 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 881176 -> 881336 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201032 -> 201184 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 422452 -> 422648 bytes sumfiles/libstdc++.sum | 2 +- 40 files changed, 1284 insertions(+), 1448 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap updated (b4a01dd19 -> 67ab8fd78)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap in repository toolchain/ci/base-artifacts. discards b4a01dd19 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 0c7db8b95 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards 028646771 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards 02b9d0369 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards b0f074f60 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 06a01b9eb 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards daeb8a5b4 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards bb43ccb84 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 37aff398d 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 27268b311 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards 48ef46032 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards dd66a9a09 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards f6115336a 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 710ab8bf2 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-271 [...] discards ac2560b9d 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 90ab6cf6c 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 7d812aba6 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards 7a648fd34 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards b27419266 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 0b3827bfd 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 14f8f9842 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards 7b072f3c0 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards cd765611f 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards d02a38712 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 3abec6e89 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards cd88d6e5e 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards a61f51706 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 034bdc50c 94: onsuccess: #1476: 2: Success after baseline build: no new [...] discards 871afe38a 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-2393 [...] discards 4c425eff6 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 68bd3a43d 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 05c5e18d9 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 420cb1307 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 909c73c5d 88: onsuccess: 1: Success after gcc: 20 commits discards af51d5fee 87: force: 1: Failure after gcc: Fix up dump_printf_loc forma [...] discards c8b101cf7 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 w [...] discards 3ad54daf7 85: onsuccess: 2: Success after binutils: 4 commits discards 55f0e81c4 84: onsuccess: 2: Success after gcc: 9 commits discards 362748323 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards eaa373f88 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 614ebd12c 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 453da941c 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 7e50d0667 79: onsuccess: 1: Successful build after gcc: 3 commits discards 7bcfedee4 78: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] discards 9825aa0e5 77: force: 2: Successful build after gcc: 32 commits discards 8286b19fa 76: onsuccess: 2: Successful build after binutils: 10 commits discards 1c0773722 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 2eb7e83f1 74: onsuccess: 2: Successful build after gcc: 13 commits discards d0ccf0e6d 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards d518f37e8 72: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] discards 4305c1976 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 0640f9b67 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 710a746a8 69: onsuccess: 2: Successful build after baseline build: no n [...] discards f0acdab2b 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards d852fa191 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 35901a6f1 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 7c9c21111 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 49ef3f4b0 64: onsuccess: 2: Successful build after gcc: 7 commits discards a3437e6f3 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 47d069817 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards e09d15511 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards eae241fdb 60: onsuccess: 1: Successful build after gcc: 15 commits discards 1fbb52378 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] discards 9d3e57b6a 58: force: 2: Successful build after gcc: tree.cc: Fix optimi [...] discards 13284a9a6 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 13dda1361 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 1bd3031ed 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d9a068ac4 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 85504b980 53: onsuccess: 2: Successful build after gcc: 5 commits discards 1cb9313b0 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards e7cc45425 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 5e6e195fd 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards e230a48d6 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 140279317 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards f9d0c0d00 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 0c88bf22a 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 1aa364261 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards ebfa06f4c 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards a143e8da5 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] discards 6b400dcf8 42: onsuccess: 2: Successful build after gcc: 2 commits discards 574e61d20 41: onsuccess: 2: Successful build after baseline build: no n [...] discards be1d773fd 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 410d49d15 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 32053bbaa 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards d8ff7357c 37: onsuccess: 2: Successful build after gcc: 2 commits discards 6a05039c9 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 2d7210eb8 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards af241c685 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards b05daff25 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 0e0be3443 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 07cdee283 31: onsuccess: 2: Successful build after gcc: 8 commits discards f6a1d89a5 30: onsuccess: 2: Successful build after gcc: 7 commits discards 79d422114 29: onsuccess: 2: Successful build after binutils: 5 commits discards ffc2ecb96 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards aa9f8871d 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards f0391a7a5 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits discards ca0df5ca1 25: onsuccess: binutils-gcc: 2 discards b9b5a2a33 24: onsuccess: binutils-gcc: 2 discards 3033ac14f 23: onsuccess: binutils-gcc: 2 discards 6251ce8e9 22: onsuccess: binutils-gcc: 2 discards a4bf7384d 21: onsuccess: binutils-gcc: 2 new 1780dbcd9 21: onsuccess: binutils-gcc: 2 new d0b018910 22: onsuccess: binutils-gcc: 2 new a22822825 23: onsuccess: binutils-gcc: 2 new bc6fa476c 24: onsuccess: binutils-gcc: 2 new 1119aa32d 25: onsuccess: binutils-gcc: 2 new 2317a5daa 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits new 7b51d6395 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits new ca130caa8 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 8769bf5d8 29: onsuccess: 2: Successful build after binutils: 5 commits new b9bd18933 30: onsuccess: 2: Successful build after gcc: 7 commits new 60c455035 31: onsuccess: 2: Successful build after gcc: 8 commits new 4550eefe7 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits new eed8b760e 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 92d1b83ca 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits new b7df55c6b 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 4421f3139 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 532a8e483 37: onsuccess: 2: Successful build after gcc: 2 commits new c1d9e354d 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 49ce0ba78 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new c8dd0ec39 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 86657901b 41: onsuccess: 2: Successful build after baseline build: no n [...] new 878a35098 42: onsuccess: 2: Successful build after gcc: 2 commits new 53c21f849 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] new f74cb85d2 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new dba31544e 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 5d01cec36 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new a71cfb7e6 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new d189e6371 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new f7fd24435 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new bd0e3bf48 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new dba43c324 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 50f4e186c 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 2c4bc77d8 53: onsuccess: 2: Successful build after gcc: 5 commits new 7f91eb55e 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 23066c9da 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 04b26f0f7 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 77fe35047 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new d495ab056 58: force: 2: Successful build after gcc: tree.cc: Fix optimi [...] new 6167c727d 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] new e17293034 60: onsuccess: 1: Successful build after gcc: 15 commits new 60e778f18 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 9bf36a5f2 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 58d988d91 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 93381ebab 64: onsuccess: 2: Successful build after gcc: 7 commits new b6a3ab8d3 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 20360c356 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new e3be52759 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 2438817e4 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 9ea677a3f 69: onsuccess: 2: Successful build after baseline build: no n [...] new 7ad023d37 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 0f04607f1 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 43df6b920 72: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] new 9c5690879 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new ecbffb255 74: onsuccess: 2: Successful build after gcc: 13 commits new 8e0525a22 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new bd421466d 76: onsuccess: 2: Successful build after binutils: 10 commits new e2410ccac 77: force: 2: Successful build after gcc: 32 commits new e5acbd0e2 78: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] new 5f888bef3 79: onsuccess: 1: Successful build after gcc: 3 commits new c1c0322e4 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new f746842b4 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 7108effab 82: onsuccess: 2: Success after binutils/gcc: 26 commits new a5a03b4dc 83: onsuccess: 2: Success after binutils/gcc: 7 commits new ac36f5b5a 84: onsuccess: 2: Success after gcc: 9 commits new 9c51a46a0 85: onsuccess: 2: Success after binutils: 4 commits new 8285bd1bb 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 w [...] new 39d27dfb3 87: force: 1: Failure after gcc: Fix up dump_printf_loc forma [...] new a25fe33f9 88: onsuccess: 1: Success after gcc: 20 commits new 93cbe7621 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 2db56f1d7 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 9b72c932c 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 3b6e02ff2 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 9f10f6a60 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-2393 [...] new ac5a7073a 94: onsuccess: #1476: 2: Success after baseline build: no new [...] new b815f7f95 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new f2bc968ba 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 6450cc818 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 5f576fb80 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 0d3de5cc4 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new a1315d1bc 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new a7c98ccea 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new 4bf4a5db3 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 527b8bfa9 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 034b51508 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 7baecdf34 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 081bd79ee 106: onsuccess: #1527: 2: Success after gcc: 2 commits new d0d9a13ca 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 190d99ca2 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-271 [...] new 6098220ea 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 2b5bba3c7 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new e801290bd 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 6d7c57dfa 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 59f04a673 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new d6b5d66ae 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 3a3afcab6 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new c04b8363a 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 43e7f01c2 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new 893b81c7f 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new dd8974de0 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 2162f752e 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 41fb894d1 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new 67ab8fd78 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 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 (b4a01dd19) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] 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 -> 1832 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2708 bytes 04-build_abe-binutils/console.log.xz | Bin 38520 -> 37596 bytes 05-build_abe-bootstrap/console.log.xz | Bin 267760 -> 269020 bytes 06-check_regression/console.log.xz | Bin 2212 -> 3072 bytes 07-update_baseline/console.log | 64 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 19 +++++----- 13 files changed, 48 insertions(+), 47 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (5e8c7fa77 -> c539172a8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-arm in repository toolchain/ci/base-artifacts. discards 5e8c7fa77 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/gd [...] discards 01e47905e 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/gd [...] discards 059b428c1 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 commits discards f32f289c4 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qemu [...] discards f926b061d 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/gl [...] discards 7939e7691 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 commits discards 3e32a723c 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: 1 [...] discards fca29f0e2 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/gd [...] discards 47f26fc32 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/gl [...] discards 30ad5734f 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/gd [...] discards adebe918f 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards f5d6d4a0a 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards efbe59256 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards b28c40b5e 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/gd [...] discards 8f756dffd 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...] discards 3f4cb1d0a 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] discards 3d6400690 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 53c02de73 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards f633a7284 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] discards bf99e1341 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 205a3efda 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] discards 0f4d9e84b 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] discards 6090bc9e0 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 5f275894e 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] discards dd2ef7b30 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] discards cc97c9002 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards b1ca56d41 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] discards a503f80fe 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] discards 7aaa3d243 95: onsuccess: #1529: 7: Success after baseline build: no new [...] discards 401108a42 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 6a04a36e0 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] discards ebed77e5a 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 899922a0b 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 5481bd6ec 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 359fffacb 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 3a56f1115 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards bfeae5946 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 134bd3920 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards f12f56882 85: onsuccess: 7: Success after gcc: 9 commits discards f3350d011 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards a865f02f6 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards c83db62bb 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 9611ebeb9 81: onsuccess: 7: Successful build after gcc: 2 commits discards b72a0e0af 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards a4180d90a 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards fb6fd79bd 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 2c9fc7d94 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards 770ec00e6 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards faf262815 75: onsuccess: 7: Successful build after linux: 44 commits discards b41b206a2 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 37b9adbe1 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 28d9853ea 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 73461b729 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards 8da4f0d04 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards af74fd920 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 94a48647a 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards e4fd571b6 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards b5916f3f8 66: onsuccess: 7: Successful build after gcc: 3 commits discards 825e04bb8 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards ea52b05a0 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 2f3941a82 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards 1c657e08d 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 342011460 61: onsuccess: 4: Successful build after gcc: 15 commits discards cc267f41c 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards a445c5174 59: force: 7: Successful build after gcc: 2 commits discards eca38ca1e 58: onsuccess: 7: Successful build after glibc: 2 commits discards 0cd274855 57: onsuccess: 7: Successful build after gcc: 7 commits discards f9fad0ac0 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 2d4d49f6a 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 69eda8d6d 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards a145fd369 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] discards 7d3885fbf 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 65a77ec24 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards db25c112a 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 6bb1ea241 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 7bf131156 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 1913bb8cf 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 056ee381c 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards a71e364a4 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 75532b6ba 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards 64bad5bd0 43: onsuccess: 7: Successful build after gcc: 2 commits discards 272c3b1ba 42: onsuccess: 7: Successful build after baseline build: no n [...] discards d8dbd2cc0 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 73c578f7d 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 703572dbc 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits discards 6f9d84a6a 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards 55cf2e6eb 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 535e0e5c2 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards e274fa173 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards c04c3831d 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards f81747f7d 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 648f2f701 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 7bfc1f74a 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 2d8f91733 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 82d42abc7 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 68f5c05c1 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards aa5985aa0 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 225d1fcbc 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 5851cd388 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 7265b8d7e 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 2c6c939d1 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2b3d0dfc0 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 8c3e41e4f 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 67488eda6 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c4f6366a2 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3fb29f3a8 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 46f17039d 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new d9231b56b 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 337d20bab 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 0a0d487ff 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new f6338891a 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 73663c26f 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 30a4322f5 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 03e473500 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new f45e37563 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 174c1d5b0 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 03db42732 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new 961a7c5b7 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits new a478951f3 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 2038eab10 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a6b8f3d56 42: onsuccess: 7: Successful build after baseline build: no n [...] new 56ea630b2 43: onsuccess: 7: Successful build after gcc: 2 commits new 616ba9bb8 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new ca754dcb8 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new c9937c3ee 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 736fd722b 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 90c0fd5bf 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 353376f06 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 35b31ca70 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 65195c736 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new c67abe0ab 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 47a435935 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] new 4e744d6bd 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new b8dd1f271 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 2faaf470d 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new dc554057b 57: onsuccess: 7: Successful build after gcc: 7 commits new 9cd0be568 58: onsuccess: 7: Successful build after glibc: 2 commits new 3721e88d0 59: force: 7: Successful build after gcc: 2 commits new 22f807393 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new f2913947d 61: onsuccess: 4: Successful build after gcc: 15 commits new 54adaefcb 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new d36c02923 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new db3cce83d 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 2168ddf65 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 858e9d3d9 66: onsuccess: 7: Successful build after gcc: 3 commits new edffeb57d 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 9d866b558 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new f16679777 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 9977d3477 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 2040636b5 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new 58b3a593b 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 4792568a0 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 9d0a807c6 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new eaedfb3c2 75: onsuccess: 7: Successful build after linux: 44 commits new 59b459cd0 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 8e7ec6d46 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new fe5ee6169 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7aea726ab 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 68afb6e76 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new 13c573e8f 81: onsuccess: 7: Successful build after gcc: 2 commits new 9add2c407 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 8050512e0 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new ebbbcbf6a 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 318f76a18 85: onsuccess: 7: Success after gcc: 9 commits new 56e2fb869 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new af68c2a27 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 78ea07b43 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new ab563607a 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new e364d050f 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new d23ea360c 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 8eca406a8 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 858b349a5 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] new 38eea0f0a 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new f06bced53 95: onsuccess: #1529: 7: Success after baseline build: no new [...] new 7490b73b7 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] new fe7001135 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] new 1f98db844 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 5e8d93cfe 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] new 25c72bc09 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] new fc3cda921 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 8aebb856e 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] new 1e77a03ec 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] new 5814db37c 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 8876dbb8f 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] new 5fb526b80 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 68bc42f93 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 1b22c91d0 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] new 1ca3e77ac 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...] new e33e0153d 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/gd [...] new 4d8333fa7 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 5510825a6 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 83faa030e 113: onsuccess: #1624: 7: Success after gcc: 6 commits new bde9c8c7e 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/gd [...] new 0c33f1f4c 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/gl [...] new 04ad383f7 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/gd [...] new 6b599d73e 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: 1 [...] new c0502f7ae 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 commits new 71772d31f 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/gl [...] new d27e458ab 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qemu [...] new 20f07cc7f 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 commits new 1dcb84613 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/gd [...] new 72909e451 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/gd [...] new c539172a8 124: onsuccess: #1637: 7: 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 (5e8c7fa77) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 1720 -> 1884 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2752 bytes 04-build_abe-binutils/console.log.xz | Bin 30796 -> 30148 bytes 05-build_abe-stage1/console.log.xz | Bin 91700 -> 91300 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 9240 -> 8564 bytes 08-build_abe-glibc/console.log.xz | Bin 234408 -> 234648 bytes 09-build_abe-stage2/console.log.xz | Bin 223808 -> 223416 bytes 10-build_abe-gdb/console.log.xz | Bin 38148 -> 37592 bytes 11-build_abe-qemu/console.log.xz | Bin 31096 -> 31236 bytes 12-check_regression/console.log.xz | Bin 3516 -> 4812 bytes 13-update_baseline/console.log | 40 ++++++++++++++++---------------- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 43 ++++++++++++++++++----------------- 22 files changed, 51 insertions(+), 50 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_eabi_stm32/gnu_eabi-master-arm_eabi-coremark-O3 updated (5f4282de6 -> 8a0620b81)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_gnu_eabi_stm32/gnu_eabi-master-arm_eabi-coremark-O3 in repository toolchain/ci/base-artifacts. from 5f4282de6 1: onsuccess: #308: 1: [TCWG CI] No change after gcc: 3183 commits new 8a0620b81 2: onsuccess: #309: 1: [TCWG CI] No change after binutils: 18 [...] The 1 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 1832 -> 1656 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30700 -> 29960 bytes 04-build_abe-stage1/console.log.xz | Bin 88960 -> 88672 bytes 06-build_abe-newlib/console.log.xz | Bin 16708 -> 16828 bytes 07-build_abe-stage2/console.log.xz | Bin 161488 -> 160680 bytes 08-benchmark/benchmark-build.log | 86 ++++++++++++------------- 08-benchmark/benchmark.log | 84 ++++++++++++------------ 08-benchmark/console.log.xz | Bin 3768 -> 3784 bytes 09-check_regression/console.log.xz | Bin 4032 -> 4048 bytes 09-check_regression/csv-results-0/perf.csv | 2 +- 09-check_regression/csv-results-0/results.csv | 12 ++-- 09-check_regression/results-brief.csv | 4 +- 09-check_regression/results-full.csv | 12 ++-- 09-check_regression/results-internal.csv | 12 ++-- 09-check_regression/results.csv | 12 ++-- 09-check_regression/results.log | 4 +- dashboard/dashboard-generate.sh | 2 +- dashboard/squad/Mean/results-metadata.json | 10 +-- dashboard/squad/coremark/results-metadata.json | 10 +-- dashboard/squad/dashboard-push-squad.sh | 10 +-- git/binutils_rev | 2 +- mail/jira-body.txt | 14 ++-- mail/mail-body.txt | 14 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 14 ++-- results_id | 2 +- 27 files changed, 154 insertions(+), 154 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[binutils-gdb] branch master updated (8e037eae682 -> 618ba27878a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 8e037eae682 gdb/csky add cskyv2-linux.xml for cskyv2-linux.c new 618ba27878a gdb/testsuite/tui: start GDB with "set filename-display basename" The 1 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: gdb/testsuite/lib/tuiterm.exp | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[gcc] branch master updated (af611afe5fc -> ab98b4c0725)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from af611afe5fc tree-optimization/106922 - extend same-val clobber FRE new ab98b4c0725 libstdc++: Micro-optimizaion for std::bitset stream extraction The 1 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: libstdc++-v3/include/std/bitset | 2 +- libstdc++-v3/testsuite/20_util/bitset/io/input.cc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_eabi_stm32/gnu_eabi-master-arm_eabi-coremark-O3 updated (164776201 -> 5f4282de6)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_gnu_eabi_stm32/gnu_eabi-master-arm_eabi-coremark-O3 in repository toolchain/ci/base-artifacts. from 164776201 0: init: #305: 1: [TCWG CI] No change after baseline build: n [...] new 5f4282de6 1: onsuccess: #308: 1: [TCWG CI] No change after gcc: 3183 commits The 1 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 1632 -> 1832 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30628 -> 30700 bytes 04-build_abe-stage1/console.log.xz | Bin 87216 -> 88960 bytes 06-build_abe-newlib/console.log.xz | Bin 16640 -> 16708 bytes 07-build_abe-stage2/console.log.xz | Bin 158608 -> 161488 bytes 08-benchmark/benchmark-build.log | 86 +++++++++++++------------ 08-benchmark/benchmark.log | 84 ++++++++++++------------ 08-benchmark/console.log.xz | Bin 3728 -> 3768 bytes 09-check_regression/console.log.xz | Bin 3500 -> 4032 bytes 09-check_regression/csv-results-1/perf.csv | 2 +- 09-check_regression/csv-results-1/results.csv | 12 ++-- 09-check_regression/results-brief.csv | 4 +- 09-check_regression/results-full.csv | 12 ++-- 09-check_regression/results-internal.csv | 12 ++-- 09-check_regression/results.csv | 12 ++-- 09-check_regression/results.log | 2 +- 10-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- dashboard/squad/Mean/results-metadata.json | 10 +-- dashboard/squad/Mean/results-metrics.json | 2 +- dashboard/squad/coremark/results-metadata.json | 10 +-- dashboard/squad/coremark/results-metrics.json | 2 +- dashboard/squad/dashboard-push-squad.sh | 10 +-- git/gcc_rev | 2 +- mail/jira-body.txt | 8 ++- mail/mail-body.txt | 8 ++- mail/mail-subject.txt | 2 +- manifest.sh | 22 +++---- results_id | 2 +- 30 files changed, 161 insertions(+), 147 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (8456b8ce7 -> d31b01214)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards 8456b8ce7 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/gd [...] discards 861d19996 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/gd [...] discards f7ee73432 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 45a334fdc 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qemu [...] discards 8475a9d9d 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/gl [...] discards 8bfcf6b56 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 commits discards bf08a1be5 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: 1 [...] discards 13038e0f7 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/gd [...] discards 34b584112 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/gl [...] discards 3d89ff490 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/gd [...] discards c8e163cd8 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards b619e5969 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards b204b9834 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-272 [...] discards 01ad7e1ba 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/gd [...] discards 2e1d3cc02 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/gd [...] discards 935ef9f5c 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddeed [...] discards e56a5b5ea 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/gl [...] discards 7dab3dd9f 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 43daac8e3 102: force: #1551: 1: Failure after gcc: 306 commits discards b91ac0c23 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 897d9f081 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] discards fde59d1d6 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards b5212831f 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] discards e6c6c12f2 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 40785e8ff 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 9bd71da96 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards d07fe3acc 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 68ac8df89 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards fb6791bc2 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 8dec077a7 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 3bd405c97 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards cbd822ea4 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 66099c488 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards b4096f116 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 49fb62b87 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 77b98e05a 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards 410cd9743 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards fd4a51413 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 18cf896e4 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards 80b7eff2b 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 26405ce06 80: onsuccess: 7: Successful build after linux: 44 commits discards bfc56dae8 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards c994cfa2b 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] discards 577ff9d57 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards bc62e785e 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 9ba83f0b0 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards 6f3e7d226 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards ebdd84aee 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards bf871d110 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 1f2666516 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards f4f50b15e 70: onsuccess: 7: Successful build after gcc: 4 commits discards 2dee12859 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 0dbb6d8e3 68: onsuccess: 7: Successful build after linux: 6 commits discards 6af975679 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] discards 9246cc021 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] discards 2403828f6 65: onsuccess: 7: Successful build after binutils: 3 commits discards f38df62a8 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards b85169dca 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 221b43786 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 4237bb4e9 61: onsuccess: 4: Successful build after gcc: 5 commits discards c6c129b17 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards 9a4d25044 59: force: 7: Successful build after gcc: 3 commits discards 0028e9d25 58: onsuccess: 7: Successful build after glibc: 2 commits discards a5d1d88c3 57: onsuccess: 7: Successful build after gcc: 7 commits discards 91258e94c 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards c053cb238 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards dbe0f5aed 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards 7e8e5bff7 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] discards 7053c27e5 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits discards 2ffbf8490 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 958f6ddbf 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards aca3208ce 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 01cd08ebb 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 65e02c151 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 5e063c97c 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards ed86f892d 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 7841b1263 44: onsuccess: 7: Successful build after linux: 34 commits discards 656786013 43: onsuccess: 7: Successful build after gcc: 2 commits discards a1a34a0b9 42: onsuccess: 7: Successful build after baseline build: no n [...] discards 3ef4f432f 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 3c5619787 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 868973779 39: onsuccess: 7: Successful build after gcc: 2 commits discards 4e46cdb26 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 5de0dd80d 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 15057592d 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards f7d855c62 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 178ae13f3 34: onsuccess: 7: Successful build after gcc: 3 commits discards 7ff5a3360 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards e8463f273 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards e32a2102c 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards bcee44477 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits discards aa99289a4 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards fd380d7bb 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 8549a509c 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 44f41fb47 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards fadac2212 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 78c579f75 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 5191dec20 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b56a98d10 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards dee7c6606 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards ddc5d4099 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 4186fda6a 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a29c7dda3 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new aad3b5e15 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a52d1483f 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e54c3c350 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d1e71d700 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e08615231 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new fcf17b9bd 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 371dee0e4 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 4d964c9d9 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 00027227c 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits new 9e65422e9 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new fe24e59d0 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 275eeba5b 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 96dff7504 34: onsuccess: 7: Successful build after gcc: 3 commits new c2956cebe 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new c5ea1c8ec 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a253f4362 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 91bb3e4c1 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7e728fde1 39: onsuccess: 7: Successful build after gcc: 2 commits new 98144ec80 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new c4b721b6f 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new d303748af 42: onsuccess: 7: Successful build after baseline build: no n [...] new 556e166de 43: onsuccess: 7: Successful build after gcc: 2 commits new 31b506061 44: onsuccess: 7: Successful build after linux: 34 commits new a855c68cf 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 6bef3ee9b 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 564ea2524 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new b6a43b517 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 95e6128fa 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 4dc3fe5d3 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a78f67d80 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 565c7052d 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits new 548219671 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] new 363a3153a 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 81727c1b2 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 82282b30c 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 0340c982f 57: onsuccess: 7: Successful build after gcc: 7 commits new bd458020e 58: onsuccess: 7: Successful build after glibc: 2 commits new ef434c3ce 59: force: 7: Successful build after gcc: 3 commits new d42dc9782 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new 618ae2e92 61: onsuccess: 4: Successful build after gcc: 5 commits new 1972a1035 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new e16367edf 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new d97a60d24 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new 60eb34fa4 65: onsuccess: 7: Successful build after binutils: 3 commits new 02f89aad1 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] new 107ff8dbd 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] new f537b8dc4 68: onsuccess: 7: Successful build after linux: 6 commits new d62357472 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new c8fcf1e8e 70: onsuccess: 7: Successful build after gcc: 4 commits new 27475acf5 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 1aeeb0e71 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 69d9f87bd 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 31ce7ece4 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 5015a1ca6 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new a8b436058 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 02801c10d 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new edf3bf8da 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] new e39e351b3 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 13459e860 80: onsuccess: 7: Successful build after linux: 44 commits new e3d143750 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 508ca7ff1 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new 3d5803b78 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new ee4391127 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 672efddc3 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new 74efb08d8 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 7b4c663d7 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 0e3461dea 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 359f0de92 89: onsuccess: 7: Success after gcc/glibc: 8 commits new c33a2b3bb 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 74c04770a 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 344338adc 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 5deae6edf 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new e91d3389d 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new a23688305 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new f63cecec6 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new a7f2177af 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 5264fb031 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] new a916a7f4b 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new b0ec6e7d9 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] new 33605b2d7 101: onsuccess: #1547: 7: Success after binutils: 82 commits new e5816a39c 102: force: #1551: 1: Failure after gcc: 306 commits new 156b59c02 103: onsuccess: #1552: 1: Success after gcc: 5 commits new ce9c716f7 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/gl [...] new 9ce6c9d63 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddeed [...] new 3ee0983d7 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/gd [...] new f11229b0f 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/gd [...] new 4384c3887 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-272 [...] new 05aeb874f 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 4e9785b49 110: onsuccess: #1559: 7: Success after gcc: 4 commits new ac9ab28e8 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/gd [...] new ac48bab8e 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/gl [...] new 392d3c3a0 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/gd [...] new 347e74702 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: 1 [...] new dc7f5130c 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 commits new b8f44d077 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/gl [...] new e9237fb76 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qemu [...] new a0f24e338 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 278c924f2 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/gd [...] new 8b09e699d 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/gd [...] new d31b01214 121: onsuccess: #1572: 7: 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 (8456b8ce7) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 1696 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 31476 -> 30224 bytes 05-build_abe-stage1/console.log.xz | Bin 72644 -> 72424 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 9232 -> 8496 bytes 08-build_abe-glibc/console.log.xz | Bin 239580 -> 238840 bytes 09-build_abe-stage2/console.log.xz | Bin 205040 -> 202728 bytes 10-build_abe-gdb/console.log.xz | Bin 38592 -> 37408 bytes 11-build_abe-qemu/console.log.xz | Bin 32060 -> 31448 bytes 12-check_regression/console.log.xz | Bin 3388 -> 4960 bytes 13-update_baseline/console.log | 70 +++++++++++++++++------------------ 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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 47 +++++++++++------------ 23 files changed, 69 insertions(+), 68 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (217dac3a8 -> 18383cd10)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-aarch64 in repository toolchain/ci/base-artifacts. discards 217dac3a8 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits discards 18755de75 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits discards 74a23574f 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards 83eca6692 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards 28a8707a6 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards f97cdde5e 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards 1ccbe6d0b 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards 524117012 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards d1eda8b0e 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards 1a101ce8f 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards 5667df185 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards 06242d2d6 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards a2af680ba 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards 80c6f7b15 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards 477ce32dd 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards d98b9acf7 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards 51eec10fe 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards b565732e1 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards a8384ddd3 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-270 [...] discards 593e54e6c 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards a633fd7e3 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards 414e1bded 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards cc7c8f693 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards 25677a2af 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards 9fa6b71af 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-2393 [...] discards 36bfeb887 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-2392 [...] discards ef0e36df6 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards 2005848a7 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-2390 [...] discards 9b7aa9055 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards 794934e25 91: onsuccess: 1: Success after gcc: Daily bump. discards 7bffdff35 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards 7c0a88eab 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards 603b8c33a 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards 2a8638fda 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards 91f4e463e 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards cddaed7cf 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards 7623a5bce 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards beac73124 83: onsuccess: 1: Success after gcc: 8 commits discards 87bd5597a 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards 67f9ccb1e 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards 26523390b 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards 521218882 79: onsuccess: 1: Successful build after gcc: Daily bump. discards 4341a2155 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards d5410a67c 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards d9caf3180 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards b35cf15cb 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards f3ca473ce 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards e1c21dded 73: onsuccess: 1: Successful build after binutils: PR29494 Tr [...] discards 78c29cf9a 72: onsuccess: 1: Successful build after gcc: 2 commits discards 33decad4d 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 319c0e78a 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards 4b9ca0cfd 69: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards e0f959c43 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards a5b08fb80 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards c7c2e0014 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 216451883 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards b70be8128 64: onsuccess: 1: Successful build after gcc: 5 commits discards 5cdf06a67 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards c0cd87e2d 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards ff588c2ac 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits discards 90be285ad 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 373d38ff8 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits discards 9dbcf77e0 58: onsuccess: 1: Successful build after binutils: 2 commits discards 42df3b085 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards 61528c970 56: onsuccess: 1: Successful build after gcc: Daily bump. discards ca981856c 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 923add715 54: onsuccess: 1: Successful build after gcc: 7 commits discards c7978839c 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 241e63fbd 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 3dfebe7ee 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 9c0098f04 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 089555cce 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 0041f80cd 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 1e7e5769f 47: onsuccess: 1: Successful build after binutils: 2 commits discards 2dadef198 46: onsuccess: 1: Successful build after gcc: Daily bump. discards c88653b66 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards b6a7b0daa 44: onsuccess: 1: Successful build after gcc: 2 commits discards e0828a877 43: onsuccess: 1: Successful build after gcc: Daily bump. discards 4f378f04c 42: onsuccess: 1: Successful build after binutils: Automatic [...] discards 540eceb69 41: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 93a0b3518 40: onsuccess: 1: Successful build after gcc: 2 commits discards 3fd39916b 39: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards c152f73f0 38: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards ff0abddb3 37: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards 8334e2cb8 36: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards e83f0c309 35: onsuccess: 1: Successful build after gcc: 4 commits discards 29a090344 34: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards a845e0b5b 33: onsuccess: 1: Successful build after gcc: 10 commits discards 124e07dac 32: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards f056ed934 31: onsuccess: 1: Successful build after gcc: 2 commits discards e07c238dd 30: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards e812ab9bb 29: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 9b399f08c 28: onsuccess: 1: Successful build after binutils/gcc: 22 commits discards 567f97883 27: onsuccess: binutils-gcc: 1 discards 6af0003e2 26: onsuccess: binutils-gcc: 1 discards 9c309c014 25: onsuccess: binutils-gcc: 1 discards 082af1671 24: onsuccess: binutils-gcc: 1 discards 3f91c0e87 23: onsuccess: binutils-gcc: 1 discards df3717190 22: onsuccess: binutils-gcc: 1 discards c0b578f25 21: onsuccess: binutils-gcc: 1 discards a75b4bd0e 20: onsuccess: binutils-gcc: 1 new d9874bdf0 20: onsuccess: binutils-gcc: 1 new 9f98c0a3e 21: onsuccess: binutils-gcc: 1 new fd9fb066d 22: onsuccess: binutils-gcc: 1 new 1a34f90aa 23: onsuccess: binutils-gcc: 1 new e1221e144 24: onsuccess: binutils-gcc: 1 new cec736f87 25: onsuccess: binutils-gcc: 1 new 11a0f2d93 26: onsuccess: binutils-gcc: 1 new a45fb9c96 27: onsuccess: binutils-gcc: 1 new ffd0a63cf 28: onsuccess: 1: Successful build after binutils/gcc: 22 commits new 81b4b91ad 29: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 8c36c2d6d 30: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 46d03cad6 31: onsuccess: 1: Successful build after gcc: 2 commits new 3abfe22e6 32: onsuccess: 1: Successful build after binutils/gcc: 9 commits new a3433a36e 33: onsuccess: 1: Successful build after gcc: 10 commits new b3e2df55b 34: onsuccess: 1: Successful build after binutils/gcc: 5 commits new a932a8640 35: onsuccess: 1: Successful build after gcc: 4 commits new 186cc6b69 36: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 0b64974ce 37: onsuccess: 1: Successful build after binutils/gcc: 12 commits new d57099008 38: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 913ff2c60 39: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 3ec48b28a 40: onsuccess: 1: Successful build after gcc: 2 commits new 58cbc9faf 41: onsuccess: 1: Successful build after binutils/gcc: 6 commits new fecf1f8f0 42: onsuccess: 1: Successful build after binutils: Automatic [...] new 292c260f8 43: onsuccess: 1: Successful build after gcc: Daily bump. new 582765da7 44: onsuccess: 1: Successful build after gcc: 2 commits new 252ec0447 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits new db0e64fcd 46: onsuccess: 1: Successful build after gcc: Daily bump. new b21ec33fb 47: onsuccess: 1: Successful build after binutils: 2 commits new cf74abcfa 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits new f6853fa2d 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 29bb96163 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 74612f743 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits new d71d8593a 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 3fceef3d4 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new d06dc5d59 54: onsuccess: 1: Successful build after gcc: 7 commits new ce6187266 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 5735c3282 56: onsuccess: 1: Successful build after gcc: Daily bump. new 3677b01c3 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits new 73adf2a16 58: onsuccess: 1: Successful build after binutils: 2 commits new d10052bad 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits new e34a2c788 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 8f51bd456 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits new cc641b8c8 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new ef847cddc 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 828d0b1fa 64: onsuccess: 1: Successful build after gcc: 5 commits new 7e14ab665 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new b73a15da9 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new c35afe77f 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 6f17a9f35 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 31b7f8579 69: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new 16aeb5c50 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new b1c8dd29c 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 640a10479 72: onsuccess: 1: Successful build after gcc: 2 commits new 1796b0428 73: onsuccess: 1: Successful build after binutils: PR29494 Tr [...] new 8506f5864 74: onsuccess: 1: Successful build after binutils: Automatic [...] new 86b10593c 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 2f79e93ec 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 72e04ef2a 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new e7b6a4751 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 0469abd9b 79: onsuccess: 1: Successful build after gcc: Daily bump. new 27aa1ce24 80: onsuccess: 1: Success after binutils/gcc: 14 commits new 2573a2acb 81: onsuccess: 1: Success after binutils/gcc: 27 commits new 2070c072a 82: onsuccess: 1: Success after binutils/gcc: 10 commits new 4b45f6980 83: onsuccess: 1: Success after gcc: 8 commits new 4e6170c43 84: onsuccess: 1: Success after binutils/gcc: 9 commits new 80251ac76 85: onsuccess: 1: Success after binutils/gcc: 9 commits new cb421d7e9 86: onsuccess: 1: Success after binutils/gcc: 13 commits new 576874efe 87: onsuccess: 1: Success after binutils/gcc: 4 commits new b1eb87c17 88: onsuccess: 1: Success after binutils/gcc: 16 commits new 4b78df343 89: onsuccess: 1: Success after binutils/gcc: 9 commits new 814bc5d1c 90: onsuccess: 1: Success after binutils/gcc: 6 commits new e92e3d15e 91: onsuccess: 1: Success after gcc: Daily bump. new 139cf0e9b 92: onsuccess: #1965: 1: Success after gcc: 2 commits new f31a07c25 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-2390 [...] new af7834a8a 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new 8e0729a7f 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-2392 [...] new 39a03af20 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-2393 [...] new 3892b5961 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new 7a82946b6 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new 0d955da72 99: onsuccess: #1974: 1: Success after gcc: 14 commits new 435bf7970 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new 0ebba837d 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new 7c7a88a0a 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-270 [...] new 66a5b2022 103: onsuccess: #2020: 1: Success after gcc: 2 commits new 91d211c94 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new a9d12c2fc 105: onsuccess: #2022: 1: Success after gcc: 4 commits new c3034820b 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new 7bb5389b4 107: onsuccess: #2024: 1: Success after gcc: 3 commits new 3026072dd 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new 86636f301 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new 67e81a575 110: onsuccess: #2027: 1: Success after gcc: 5 commits new bed9f5cdf 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new 382072106 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new ea7a39058 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new 8433275b0 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new b261cd6f4 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new f51751cb7 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new ec8d2be94 117: onsuccess: #2034: 1: Success after binutils: 2 commits new 212319cc8 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new 66eece6ec 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits new 156486415 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits new 18383cd10 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 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 (217dac3a8) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...] 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 -> 1868 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 39320 -> 37600 bytes 04-build_abe-gcc/console.log.xz | Bin 213524 -> 211652 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3860 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2504 -> 2756 bytes 07-check_regression/console.log.xz | Bin 5292 -> 5964 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 7 + 07-check_regression/mail-body.txt | 130 +- 07-check_regression/results.compare | 40 +- 07-check_regression/results.compare2 | 212 +- 07-check_regression/results.regressions | 41 + 08-update_baseline/console.log | 34 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 132 +- mail/mail-subject.txt | 2 +- manifest.sh | 19 +- results | 41 + sumfiles/g++.log.xz | Bin 3611848 -> 3578604 bytes sumfiles/g++.sum | 147 +- sumfiles/gcc.log.xz | Bin 3089532 -> 3109248 bytes sumfiles/gcc.sum | 4964 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1039192 -> 1035704 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2184 -> 2188 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207272 -> 207448 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2540 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 440168 -> 448620 bytes sumfiles/libstdc++.sum | 10 +- 36 files changed, 2866 insertions(+), 2990 deletions(-) create mode 100644 07-check_regression/extra-bisect-params create mode 100644 07-check_regression/fails.sum create mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022