Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-stable-defconfig updated (a9b79a93f1 -> 20d22014d2)

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/llvm-master-arm-stable-defconfig in repository toolchain/ci/base-artifacts. from a9b79a93f1 10: onsuccess: #406: boot: Success after binutils/llvm/qemu: [...] new 20d22014d2 11: onsuccess: #407: boot: Success after binutils/llvm/linux [...] 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 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30156 -> 29992 bytes 04-build_kernel_llvm/console.log.xz | Bin 62776 -> 61696 bytes 05-build_abe-qemu/console.log.xz | Bin 31548 -> 30824 bytes 06-build_linux/console.log.xz | Bin 3460 -> 3924 bytes 07-boot_linux/console.log.xz | Bin 5860 -> 5820 bytes 08-check_regression/console.log.xz | Bin 2964 -> 4364 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_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, 24 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_gcc_bootstrap/release-aarch64-bootstrap_profiled_lto updated (38d528b201 -> 729ced879b)

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/release-aarch64-bootstrap_profiled_lto in repository toolchain/ci/base-artifacts. from 38d528b201 13: onsuccess: #122: 2: Success after binutils/gcc: 8 commits new 729ced879b 14: onsuccess: #123: 2: Success after binutils/gcc: 14 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 1708 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2712 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 37700 -> 37336 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 509172 -> 507756 bytes 06-check_regression/console.log.xz | Bin 2040 -> 3080 bytes 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 ++++++++++--------- 12 files changed, 16 insertions(+), 15 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 (5d6475c55f -> 1e6634ec1d)

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 5d6475c55f 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 95ee0fc2b2 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards f78c47a01b 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 71ec2b256a 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 26e4ef8aac 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards d1494b368b 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 9a52f4d367 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards a8a5c7b274 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 58177afed8 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards a3b1e74257 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 36c48241d6 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards eac536b4f4 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 6586f883b0 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 26e0bcbb28 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards f5b06f8877 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 9ed26614d5 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 344492181a 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards cb0843bb75 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 5cfd242dfd 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards c30657b383 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards ffc26f858b 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards e58ddd0aaa 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards d248acae62 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards ac3c1521f3 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards a2173b3685 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 429a1b3acc 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 1e349ba238 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 2a58e55a10 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards e158ba75d5 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards c70aeb9fa3 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 83d6addc9c 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 3b5f0e7710 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards dc149f046a 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1d979bd027 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards c72faf8b42 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards e0a7643bb4 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 2aba92347f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards aad082b030 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 5a6adaa3ce 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 0cd1e8b652 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 93387a15eb 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 3197963920 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 980a418e0a 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 9c9ef65e5e 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 051cb33928 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 10a8a1d168 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards fc30297416 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1e7add6298 74: onsuccess: 1: Successful build after linux: 44 commits discards 1524c123d5 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 46b674f4f2 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 37fd8a2758 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 5a23d1837c 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 66a33e7cfd 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 3de7e02883 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards caf38f49ff 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cf31c7f78b 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d06e2643fe 65: onsuccess: 1: Successful build after gcc: 4 commits discards 31f45b1297 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8851ea5153 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 72d95dbbe4 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards eb6e1ad31b 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 48d089131e 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 380ddf4dd0 59: onsuccess: 1: Successful build after glibc: 2 commits discards 116b5b8354 58: onsuccess: 1: Successful build after binutils: 2 commits discards bcc6b43c68 57: onsuccess: 1: Successful build after gcc: 7 commits discards 7f6b0630ed 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 77916ccf3d 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ff9f5748ae 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards d57bbd87d5 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 8d90c5a361 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 4fbd438766 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 64a876f04c 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 811969b231 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 48e9c64a9c 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards c7b6ef3efa 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e86dd47a7e 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards c5f0a48026 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d6ea50e69a 44: onsuccess: 1: Successful build after linux: 34 commits discards 60f5e63d05 43: onsuccess: 1: Successful build after gcc: 2 commits discards d194034f4f 42: onsuccess: 1: Successful build after baseline build: no [...] discards 21feff93c8 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 87fdbeb9c5 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2457adf8ea 39: onsuccess: 1: Successful build after gcc: 2 commits discards 89e91bbb89 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2e4944952a 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3c74e9b921 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f104ba6333 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 1ff6426099 34: onsuccess: 1: Successful build after gcc: 3 commits discards 571978ee12 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0ff8671492 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards c833845c65 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d8c4354ab9 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards ecac602032 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5f7ea2341a 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 4c133ed4ce 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 124cdba344 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d5d0928409 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4a53f58c12 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3ab0a9609d 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 41cb28991c 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5ef61bd60c 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d95779d92c 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c196afd92c 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b1781df772 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 453e34e250 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9672090d24 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 20bac3262e 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 22d252f562 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4aaf013d2d 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 695bc0b80f 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6bae8b85ca 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 3f73260332 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 63f75c6eca 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 52e2e9dc22 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ff8ca7b2cf 34: onsuccess: 1: Successful build after gcc: 3 commits new f21730a09f 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 95352be294 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a64dfebcc4 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2c0d84ce3a 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 723b5d9d9c 39: onsuccess: 1: Successful build after gcc: 2 commits new 1a50ec5672 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 260c9806e8 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new aff9593b68 42: onsuccess: 1: Successful build after baseline build: no [...] new d3bf6e864f 43: onsuccess: 1: Successful build after gcc: 2 commits new 7e72073f57 44: onsuccess: 1: Successful build after linux: 34 commits new 2a7438e418 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 214a5b950b 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new c767289c4a 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8c32b0bccd 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new f65f2e4354 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3f4d848fda 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 86903039de 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3c7abe5321 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 567080e40f 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new a8a65e0c01 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 162281bbc7 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0c940ed976 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e458109a19 57: onsuccess: 1: Successful build after gcc: 7 commits new 57265a09e2 58: onsuccess: 1: Successful build after binutils: 2 commits new 453be4d9e3 59: onsuccess: 1: Successful build after glibc: 2 commits new 9d1dbd2b85 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new fd777f81f7 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new b52b9d1609 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 4bee82a486 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 10bc9b9b88 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ce22f2cedc 65: onsuccess: 1: Successful build after gcc: 4 commits new 505a4316b7 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 059eccacd9 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4d7608b2a3 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 675f095bc7 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 9046432133 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new ce708713e0 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 4e5939d70a 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6ee25a807c 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 49195f235f 74: onsuccess: 1: Successful build after linux: 44 commits new 3dfc5764a0 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 57a21573d5 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 7289a41f92 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5c4a3275d6 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1c7fb87f70 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 90abb185a1 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new a62de56b0d 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 0073238a62 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 1b76dc1d0e 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new feac2fc637 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 2c1eeafee5 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 32bc3d8b45 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new fa2606fcc7 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 338916d5c3 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new ea8a0d0465 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new d60f2d2a2b 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 3e2def9a16 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new b64df19169 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new bc0a676274 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 037f72ed6b 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 8fe73609cc 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 6030347cec 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 1e75a4b03e 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 599a1a9a98 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new a2dcf7bec0 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 9e9019db48 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 330f824c27 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 0d243243c5 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new a09d99b551 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new f5c6f25cc0 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 1ab24f2e4e 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 1cb097d98b 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 7708cfb095 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 9f2f64a29c 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 2e6c8aea73 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new a5d202fd80 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 3a103bfd88 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 1ba3d6caaf 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 5eafc60014 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 9df9d0c34e 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 1e24a6418f 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new f68e9fec51 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 778ef6c1f7 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 8f44f84653 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new d77b2157da 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new a75796f09e 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new b0a20b9d19 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 1e6634ec1d 122: onsuccess: #1717: 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 (5d6475c55f) \ 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 1740 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30104 -> 29996 bytes 04-build_abe-stage1/console.log.xz | Bin 91000 -> 90832 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8572 -> 8952 bytes 07-build_abe-glibc/console.log.xz | Bin 233576 -> 233688 bytes 08-build_abe-stage2/console.log.xz | Bin 223740 -> 224692 bytes 09-build_abe-gdb/console.log.xz | Bin 37248 -> 37204 bytes 10-build_abe-qemu/console.log.xz | Bin 31108 -> 31224 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2780 -> 2752 bytes 13-check_regression/console.log.xz | Bin 6736 -> 7292 bytes 13-check_regression/results.compare | 56 +- 13-check_regression/results.compare2 | 149 +- 14-update_baseline/console.log | 42 +- 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 | 42 +- sumfiles/g++.log.xz | Bin 2677476 -> 2663288 bytes sumfiles/g++.sum | 146 +- sumfiles/gcc.log.xz | Bin 2212280 -> 2227740 bytes sumfiles/gcc.sum | 2697 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 881336 -> 882820 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201184 -> 201120 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 422648 -> 426244 bytes sumfiles/libstdc++.sum | 10 +- 40 files changed, 1679 insertions(+), 1549 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_kernel/llvm-master-aarch64-mainline-allyesconfig updated (aa549f8586 -> 7c305bd44f)

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/llvm-master-aarch64-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from aa549f8586 13: onsuccess: #498: all: Success after binutils/llvm/linux/ [...] new 7c305bd44f 14: onsuccess: #499: all: Success after binutils/llvm/linux/ [...] 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 1688 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30156 -> 30544 bytes 04-build_kernel_llvm/console.log.xz | Bin 65352 -> 63276 bytes 05-build_abe-qemu/console.log.xz | Bin 31700 -> 31208 bytes 06-build_linux/console.log.xz | Bin 3104 -> 3072 bytes 07-boot_linux/console.log.xz | Bin 576 -> 576 bytes 08-check_regression/console.log.xz | Bin 3364 -> 4364 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 31 ++++++++++++++++--------------- 18 files changed, 28 insertions(+), 27 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 (67ab8fd787 -> 750ce81709)

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 67ab8fd787 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 41fb894d13 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 2162f752e9 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards dd8974de0b 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards 893b81c7ff 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 43e7f01c23 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards c04b8363a5 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 3a3afcab6e 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards d6b5d66ae2 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 59f04a673f 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 6d7c57dfa6 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards e801290bd9 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 2b5bba3c75 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 6098220ead 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 190d99ca22 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards d0d9a13ca5 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 081bd79ee9 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 7baecdf346 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards 034b51508d 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards 527b8bfa9e 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 4bf4a5db38 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards a7c98ccea9 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards a1315d1bc4 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 0d3de5cc4f 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards 5f576fb802 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 6450cc8187 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards f2bc968ba6 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards b815f7f951 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards ac5a7073ae 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 9f10f6a60a 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 3b6e02ff23 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 9b72c932c1 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 2db56f1d74 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 93cbe76211 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards a25fe33f9b 88: onsuccess: 1: Success after gcc: 20 commits discards 39d27dfb3d 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards 8285bd1bb3 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards 9c51a46a0f 85: onsuccess: 2: Success after binutils: 4 commits discards ac36f5b5a5 84: onsuccess: 2: Success after gcc: 9 commits discards a5a03b4dcc 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 7108effabd 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards f746842b43 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards c1c0322e48 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 5f888bef32 79: onsuccess: 1: Successful build after gcc: 3 commits discards e5acbd0e2d 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards e2410ccacc 77: force: 2: Successful build after gcc: 32 commits discards bd421466d8 76: onsuccess: 2: Successful build after binutils: 10 commits discards 8e0525a229 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards ecbffb2550 74: onsuccess: 2: Successful build after gcc: 13 commits discards 9c56908791 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 43df6b9207 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 0f04607f1e 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 7ad023d37d 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 9ea677a3f4 69: onsuccess: 2: Successful build after baseline build: no [...] discards 2438817e44 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards e3be527595 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 20360c356e 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards b6a3ab8d37 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 93381ebab6 64: onsuccess: 2: Successful build after gcc: 7 commits discards 58d988d91f 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 9bf36a5f29 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 60e778f187 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards e172930347 60: onsuccess: 1: Successful build after gcc: 15 commits discards 6167c727d6 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards d495ab056c 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 77fe35047d 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 04b26f0f7b 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 23066c9da4 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 7f91eb55eb 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 2c4bc77d88 53: onsuccess: 2: Successful build after gcc: 5 commits discards 50f4e186cc 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards dba43c3243 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards bd0e3bf484 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards f7fd24435d 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards d189e63711 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards a71cfb7e6e 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 5d01cec363 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards dba31544ee 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards f74cb85d26 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 53c21f849e 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards 878a350986 42: onsuccess: 2: Successful build after gcc: 2 commits discards 86657901b0 41: onsuccess: 2: Successful build after baseline build: no [...] discards c8dd0ec39c 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 49ce0ba78c 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards c1d9e354d3 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 532a8e4839 37: onsuccess: 2: Successful build after gcc: 2 commits discards 4421f31394 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards b7df55c6bc 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 92d1b83ca1 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards eed8b760e2 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 4550eefe7b 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 60c455035b 31: onsuccess: 2: Successful build after gcc: 8 commits discards b9bd189333 30: onsuccess: 2: Successful build after gcc: 7 commits discards 8769bf5d86 29: onsuccess: 2: Successful build after binutils: 5 commits discards ca130caa8f 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 7b51d63959 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 2317a5daa1 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits discards 1119aa32d6 25: onsuccess: binutils-gcc: 2 discards bc6fa476c4 24: onsuccess: binutils-gcc: 2 discards a228228256 23: onsuccess: binutils-gcc: 2 discards d0b018910a 22: onsuccess: binutils-gcc: 2 new 814a6a6302 22: onsuccess: binutils-gcc: 2 new 2c5948d602 23: onsuccess: binutils-gcc: 2 new ffbd3c7c22 24: onsuccess: binutils-gcc: 2 new 6a958f4e0d 25: onsuccess: binutils-gcc: 2 new 23c23c9de6 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits new 971d13a256 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits new a967c97941 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 48555f2ba7 29: onsuccess: 2: Successful build after binutils: 5 commits new 2eab43c469 30: onsuccess: 2: Successful build after gcc: 7 commits new 3ff5e53fb6 31: onsuccess: 2: Successful build after gcc: 8 commits new 7276031ff3 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 2decbdd3d2 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 4f66bffcdd 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits new ddc7ba6a56 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits new e9f54bdd16 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 81bb236186 37: onsuccess: 2: Successful build after gcc: 2 commits new 8059ec2c72 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 8dfc2a38a2 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new f80b169fd2 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 8497b4876a 41: onsuccess: 2: Successful build after baseline build: no [...] new 3add4198b8 42: onsuccess: 2: Successful build after gcc: 2 commits new a05fbc628d 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new 8031a73248 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 2bc14fc52e 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 980cc8bb60 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 172e394787 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 71e0049924 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 3ec1a47bed 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 63e65f76da 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new ba6a6d0c03 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new c6786402f1 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 42556d8302 53: onsuccess: 2: Successful build after gcc: 5 commits new 98f181c34b 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 711a2c42b5 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 6b959d5d06 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new fb750fe8a2 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 454b2dbf1a 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new 5a239165ba 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 69b716b77a 60: onsuccess: 1: Successful build after gcc: 15 commits new 17ac042400 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 5690ba66c3 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ecf17bbaf8 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 8fa3830244 64: onsuccess: 2: Successful build after gcc: 7 commits new 63787b7d81 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 933c9fbbdc 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 2669af3dea 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 12b6613f0f 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 7690df4f57 69: onsuccess: 2: Successful build after baseline build: no [...] new 9a57eecad2 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 8753e714dc 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 92e4fbf692 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new a20557fb58 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new d01d0ac5e2 74: onsuccess: 2: Successful build after gcc: 13 commits new 132aa0754a 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new ac09a829d4 76: onsuccess: 2: Successful build after binutils: 10 commits new b46db30d50 77: force: 2: Successful build after gcc: 32 commits new f95fe45a0e 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new a49cb1e9c9 79: onsuccess: 1: Successful build after gcc: 3 commits new 24b026d4bb 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 865925a175 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 847145ba80 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 75d5f86c0e 83: onsuccess: 2: Success after binutils/gcc: 7 commits new d3df4f6768 84: onsuccess: 2: Success after gcc: 9 commits new e4d227e1ad 85: onsuccess: 2: Success after binutils: 4 commits new 846b598e95 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new b1dfe21ea9 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new eeb5e24d52 88: onsuccess: 1: Success after gcc: 20 commits new 3d969bdc4b 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 78ec8abd56 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 30c35dd1b2 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 98e141d0f2 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 5f4daa00a8 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new 0c7eb743f3 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new a5f19ab632 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 21ce602eca 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 0103b7bbc4 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 522a07e84b 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new b3f8b5b6c3 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new d81cfeae7b 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new 641023737f 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new d7bb2e8f6f 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 8e6d35689f 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 102d141a60 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 5be84da731 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 3b77e4eadc 106: onsuccess: #1527: 2: Success after gcc: 2 commits new f103e021f4 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 370ac09a0b 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 0f374bb893 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 54ba9f1eda 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 5dd7471f69 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 86f8845a9d 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 4d1bbf88c9 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new 94f1636da0 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 27fc04366d 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new a74c212311 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 8ff9d54137 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new 780a497e45 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 7058814eab 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new ae92426f61 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new f8334be1bf 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new 12807888d6 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 750ce81709 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 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 (67ab8fd787) \ 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 1832 -> 1832 bytes 02-prepare_abe/console.log.xz | Bin 2708 -> 2708 bytes 04-build_abe-binutils/console.log.xz | Bin 37596 -> 37476 bytes 05-build_abe-bootstrap/console.log.xz | Bin 269020 -> 269180 bytes 06-check_regression/console.log.xz | Bin 3072 -> 2872 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 | 18 +++++----- 13 files changed, 47 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 (c539172a8e -> ec15d7ce3e)

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 c539172a8e 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 72909e4519 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards 1dcb846134 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 20f07cc7f2 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards d27e458aba 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 71772d31f1 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards c0502f7ae1 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 6b599d73e2 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 04ad383f7b 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 0c33f1f4c9 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards bde9c8c7e5 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 83faa030e4 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 5510825a6d 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 4d8333fa75 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards e33e0153d2 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards 1ca3e77aca 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 1b22c91d0f 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 68bc42f934 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 5fb526b807 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 8876dbb8f4 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 5814db37c4 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 1e77a03ecd 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 8aebb856e9 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards fc3cda9211 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 25c72bc091 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 5e8d93cfec 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 1f98db844b 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards fe7001135b 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 7490b73b75 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards f06bced537 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 38eea0f0ad 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 858b349a50 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 8eca406a8c 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards d23ea360c0 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards e364d050fd 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards ab563607a3 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 78ea07b436 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards af68c2a276 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 56e2fb8697 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 318f76a181 85: onsuccess: 7: Success after gcc: 9 commits discards ebbbcbf6aa 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 8050512e04 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 9add2c407d 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 13c573e8fd 81: onsuccess: 7: Successful build after gcc: 2 commits discards 68afb6e76c 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 7aea726ab0 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards fe5ee61690 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8e7ec6d469 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 59b459cd09 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards eaedfb3c27 75: onsuccess: 7: Successful build after linux: 44 commits discards 9d0a807c65 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 4792568a0a 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 58b3a593b1 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 2040636b56 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 9977d3477f 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards f166797777 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 9d866b558b 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards edffeb57d1 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 858e9d3d9e 66: onsuccess: 7: Successful build after gcc: 3 commits discards 2168ddf655 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards db3cce83d0 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d36c029235 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 54adaefcb5 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards f2913947dd 61: onsuccess: 4: Successful build after gcc: 15 commits discards 22f8073939 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 3721e88d02 59: force: 7: Successful build after gcc: 2 commits discards 9cd0be5683 58: onsuccess: 7: Successful build after glibc: 2 commits discards dc554057be 57: onsuccess: 7: Successful build after gcc: 7 commits discards 2faaf470d6 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b8dd1f271d 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 4e744d6bd2 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 47a4359355 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards c67abe0ab3 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 65195c7366 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 35b31ca705 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 353376f062 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 90c0fd5bf7 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 736fd722b0 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c9937c3eef 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards ca754dcb8a 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 616ba9bb8c 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards 56ea630b2b 43: onsuccess: 7: Successful build after gcc: 2 commits discards a6b8f3d566 42: onsuccess: 7: Successful build after baseline build: no [...] discards 2038eab107 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a478951f3e 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 961a7c5b77 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] discards 03db427320 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards 174c1d5b0b 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards f45e37563b 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 03e4735005 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 30a4322f55 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 73663c26ff 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f6338891a6 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 0a0d487ff9 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 337d20bab3 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards d9231b56b0 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 46f17039de 28: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3fb29f3a8e 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards c4f6366a23 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 67488eda63 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 8c3e41e4f7 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 94c681df10 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new aaaa04202a 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 578ab27a09 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d6ba6e0155 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new d84b2e8a9f 28: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a969fa3dd4 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new e7a8e43d08 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 8e1243618b 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new e029ac4254 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 12e7f2567c 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 30f7899bad 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 2b2bd40c3c 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 974aa292fa 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new bf737b3354 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new d589ee9ac4 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new a5721fc743 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] new 20efe4eb02 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8de44498e1 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 39d42f9da4 42: onsuccess: 7: Successful build after baseline build: no [...] new 5cedf5379e 43: onsuccess: 7: Successful build after gcc: 2 commits new d97f3454f6 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new fa2acb472b 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b7c62d3e46 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 3a6572a818 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 82dfea0a26 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new c30bedd8c4 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new bf7e96d22d 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new bfa211621b 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new bbaf858b89 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 628eb3e577 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new ce64e0fa85 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 1ff290f79d 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d243e00597 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 28a6706416 57: onsuccess: 7: Successful build after gcc: 7 commits new 793fa94149 58: onsuccess: 7: Successful build after glibc: 2 commits new 63c82c7885 59: force: 7: Successful build after gcc: 2 commits new 2b8d2e1b43 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new f11f43c4ba 61: onsuccess: 4: Successful build after gcc: 15 commits new d4b0176986 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 3b6ab28ddb 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 148cd0da0f 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 1805173ec5 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a9633f37b0 66: onsuccess: 7: Successful build after gcc: 3 commits new fd759ab052 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 13335d0df1 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 0579d1fb2f 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new f37e9c1737 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 2d222e0d90 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new b8e0f42769 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 2076a75d71 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 76967bcf4f 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new ef3ab9ff7c 75: onsuccess: 7: Successful build after linux: 44 commits new a7e5c8cf82 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5bb946dc30 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new cc1103a7c8 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a9790948d4 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new dc0cd88ace 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new a7ca6760ec 81: onsuccess: 7: Successful build after gcc: 2 commits new 31df0dc31b 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new ef71ae1724 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new b5315defe1 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 638b21744f 85: onsuccess: 7: Success after gcc: 9 commits new 4177a9321e 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 44d865b904 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 4242e37dd1 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 466b92f852 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 6fbd362bbc 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 7b84b9ba6f 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 0d8a118b9d 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new d95bfb8b0a 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 3aae6ec38a 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new d2cbbc936d 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 515f2bbcf3 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new ad00b3f3bf 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new f7de913e8c 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new b99452d161 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 831d34c18d 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new b66a199bcd 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 7224887086 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 47c84df0c6 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new c9f1554546 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new e6b306e752 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 4f20c5f6e9 106: onsuccess: #1617: 7: Success after gcc: 2 commits new b92359ceef 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 287f440597 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new 184279da38 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new d1fbb4df82 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 1ca9f20f40 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new e93fe8b410 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 19dffb75d8 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 8b82387ce2 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 0730e4c6ff 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 60da414b30 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new ca92a6d9cd 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 4c47aa2016 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 1f9649fd8b 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 661ce898a0 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new c14365a534 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new f10ccd973e 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 12777dced4 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new bc6fc7e163 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new ec15d7ce3e 125: onsuccess: #1638: 7: 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 (c539172a8e) \ 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 1884 -> 1640 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 30148 -> 30132 bytes 05-build_abe-stage1/console.log.xz | Bin 91300 -> 91184 bytes 07-build_abe-linux/console.log.xz | Bin 8564 -> 9164 bytes 08-build_abe-glibc/console.log.xz | Bin 234648 -> 236156 bytes 09-build_abe-stage2/console.log.xz | Bin 223416 -> 228568 bytes 10-build_abe-gdb/console.log.xz | Bin 37592 -> 37292 bytes 11-build_abe-qemu/console.log.xz | Bin 31236 -> 31100 bytes 12-check_regression/console.log.xz | Bin 4812 -> 4468 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 | 42 +++++++++++++++++------------------ 21 files changed, 50 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_kernel/llvm-release-arm-lts-allnoconfig updated (ded0edc38f -> b641ab2940)

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/llvm-release-arm-lts-allnoconfig in repository toolchain/ci/base-artifacts. from ded0edc38f 10: onsuccess: #232: all: Success after binutils/llvm/qemu: [...] new b641ab2940 11: onsuccess: #233: all: Success after binutils/llvm/linux/ [...] 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 1700 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30032 -> 29876 bytes 04-build_kernel_llvm/console.log.xz | Bin 64676 -> 64488 bytes 05-build_abe-qemu/console.log.xz | Bin 31464 -> 31068 bytes 06-build_linux/console.log.xz | Bin 3400 -> 3408 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 2804 -> 4456 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 31 ++++++++++++++++--------------- 18 files changed, 28 insertions(+), 27 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_kernel/llvm-release-arm-next-defconfig updated (027030c0a4 -> 055154d001)

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/llvm-release-arm-next-defconfig in repository toolchain/ci/base-artifacts. from 027030c0a4 10: onsuccess: #317: boot: Success after binutils/llvm/linux [...] new 055154d001 11: onsuccess: #318: boot: Success after binutils/llvm/linux [...] 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 1680 -> 1880 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 29800 -> 30072 bytes 04-build_kernel_llvm/console.log.xz | Bin 62488 -> 63592 bytes 05-build_abe-qemu/console.log.xz | Bin 30984 -> 31128 bytes 06-build_linux/console.log.xz | Bin 4308 -> 4240 bytes 07-boot_linux/console.log.xz | Bin 5640 -> 5652 bytes 08-check_regression/console.log.xz | Bin 3188 -> 4596 bytes 08-check_regression/mail-body.txt | 4 ++-- 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 31 ++++++++++++++++--------------- results | 2 +- 20 files changed, 33 insertions(+), 32 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_kernel/llvm-release-arm-mainline-defconfig updated (11b3033cfc -> 2fa7c9c52e)

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/llvm-release-arm-mainline-defconfig in repository toolchain/ci/base-artifacts. from 11b3033cfc 11: onsuccess: #400: boot: Success after binutils/llvm/linux [...] new 2fa7c9c52e 12: onsuccess: #401: boot: Success after binutils/llvm/linux [...] 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 1684 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 29976 -> 30024 bytes 04-build_kernel_llvm/console.log.xz | Bin 64384 -> 64784 bytes 05-build_abe-qemu/console.log.xz | Bin 31556 -> 31084 bytes 06-build_linux/console.log.xz | Bin 3160 -> 3188 bytes 07-boot_linux/console.log.xz | Bin 5848 -> 5868 bytes 08-check_regression/console.log.xz | Bin 3184 -> 4400 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_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, 24 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_bmk_gnu_apm/gnu-release-arm-spec2k6-Os_LTO updated (2429a1e18a -> 55d1f91700)

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_apm/gnu-release-arm-spec2k6-Os_LTO in repository toolchain/ci/base-artifacts. from 2429a1e18a 8: onsuccess: #64: 1: [TCWG CI] No change after binutils/gcc [...] new 55d1f91700 9: onsuccess: #65: 1: [TCWG CI] No change after binutils/gcc [...] 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 1728 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30704 -> 30232 bytes 04-build_abe-stage1/console.log.xz | Bin 88808 -> 87540 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-linux/console.log.xz | Bin 8628 -> 7844 bytes 07-build_abe-glibc/console.log.xz | Bin 231740 -> 231488 bytes 08-build_abe-stage2/console.log.xz | Bin 212700 -> 208600 bytes 09-benchmark/benchmark-build.log | 100 +- 09-benchmark/benchmark.log | 98 +- 09-benchmark/console.log.xz | Bin 3720 -> 3724 bytes 10-check_regression/console.log.xz | Bin 6544 -> 7748 bytes 10-check_regression/csv-results-0/md5sum.csv | 28603 - 10-check_regression/csv-results-0/perf.csv | 248 +- 10-check_regression/csv-results-0/results.csv | 704901 +++++++++-------- 10-check_regression/csv-results-0/size.csv | 704535 ++++++++--------- 10-check_regression/csv-results-0/vect.csv | 36 +- 10-check_regression/csv-results-1/md5sum.csv | 28603 - 10-check_regression/csv-results-1/perf.csv | 262 +- 10-check_regression/csv-results-1/results.csv | 705081 +++++++++--------- 10-check_regression/csv-results-1/size.csv | 704710 ++++++++--------- 10-check_regression/csv-results-1/vect.csv | 46 +- 10-check_regression/results-brief.csv | 60 +- 10-check_regression/results-full.csv | 278 +- 10-check_regression/results-internal.csv | 82 +- 10-check_regression/results.csv | 82 +- 10-check_regression/results.log | 1520 +- dashboard/dashboard-generate.sh | 2 +- .../squad/400.perlbench/results-metadata.json | 16 +- dashboard/squad/400.perlbench/results-metrics.json | 2 +- dashboard/squad/401.bzip2/results-metadata.json | 16 +- dashboard/squad/401.bzip2/results-metrics.json | 2 +- dashboard/squad/403.gcc/results-metadata.json | 16 +- dashboard/squad/403.gcc/results-metrics.json | 2 +- dashboard/squad/410.bwaves/results-metadata.json | 16 +- dashboard/squad/410.bwaves/results-metrics.json | 2 +- dashboard/squad/416.gamess/results-metadata.json | 16 +- dashboard/squad/416.gamess/results-metrics.json | 2 +- dashboard/squad/429.mcf/results-metadata.json | 16 +- dashboard/squad/429.mcf/results-metrics.json | 2 +- dashboard/squad/433.milc/results-metadata.json | 16 +- dashboard/squad/433.milc/results-metrics.json | 2 +- dashboard/squad/434.zeusmp/results-metadata.json | 16 +- dashboard/squad/434.zeusmp/results-metrics.json | 2 +- dashboard/squad/435.gromacs/results-metadata.json | 16 +- dashboard/squad/435.gromacs/results-metrics.json | 2 +- .../squad/436.cactusADM/results-metadata.json | 16 +- dashboard/squad/436.cactusADM/results-metrics.json | 2 +- dashboard/squad/437.leslie3d/results-metadata.json | 16 +- dashboard/squad/437.leslie3d/results-metrics.json | 2 +- dashboard/squad/444.namd/results-metadata.json | 16 +- dashboard/squad/444.namd/results-metrics.json | 2 +- dashboard/squad/445.gobmk/results-metadata.json | 16 +- dashboard/squad/445.gobmk/results-metrics.json | 2 +- dashboard/squad/447.dealII/results-metadata.json | 16 +- dashboard/squad/447.dealII/results-metrics.json | 2 +- dashboard/squad/450.soplex/results-metadata.json | 16 +- dashboard/squad/450.soplex/results-metrics.json | 2 +- dashboard/squad/453.povray/results-metadata.json | 16 +- dashboard/squad/453.povray/results-metrics.json | 2 +- dashboard/squad/454.calculix/results-metadata.json | 16 +- dashboard/squad/454.calculix/results-metrics.json | 2 +- dashboard/squad/456.hmmer/results-metadata.json | 16 +- dashboard/squad/456.hmmer/results-metrics.json | 2 +- dashboard/squad/458.sjeng/results-metadata.json | 16 +- dashboard/squad/458.sjeng/results-metrics.json | 2 +- dashboard/squad/459.GemsFDTD/results-metadata.json | 16 +- dashboard/squad/459.GemsFDTD/results-metrics.json | 2 +- .../squad/462.libquantum/results-metadata.json | 16 +- .../squad/462.libquantum/results-metrics.json | 2 +- dashboard/squad/464.h264ref/results-metadata.json | 16 +- dashboard/squad/464.h264ref/results-metrics.json | 2 +- dashboard/squad/465.tonto/results-metadata.json | 16 +- dashboard/squad/465.tonto/results-metrics.json | 2 +- dashboard/squad/470.lbm/results-metadata.json | 16 +- dashboard/squad/470.lbm/results-metrics.json | 2 +- dashboard/squad/471.omnetpp/results-metadata.json | 16 +- dashboard/squad/471.omnetpp/results-metrics.json | 2 +- dashboard/squad/473.astar/results-metadata.json | 16 +- dashboard/squad/473.astar/results-metrics.json | 2 +- dashboard/squad/481.wrf/results-metadata.json | 16 +- dashboard/squad/481.wrf/results-metrics.json | 2 +- dashboard/squad/482.sphinx3/results-metadata.json | 16 +- dashboard/squad/482.sphinx3/results-metrics.json | 2 +- .../squad/483.xalancbmk/results-metadata.json | 16 +- dashboard/squad/483.xalancbmk/results-metrics.json | 2 +- dashboard/squad/Mean/results-metadata.json | 16 +- dashboard/squad/Mean/results-metrics.json | 2 +- dashboard/squad/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 47 +- mail/mail-body.txt | 47 +- mail/mail-subject.txt | 2 +- manifest.sh | 35 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 6960588 -> 6960900 bytes save-temps/401.bzip2.tar.xz | Bin 425632 -> 425412 bytes save-temps/403.gcc.tar.xz | Bin 19775896 -> 19775940 bytes save-temps/410.bwaves.tar.xz | Bin 79540 -> 79556 bytes save-temps/416.gamess.tar.xz | Bin 28721792 -> 28721864 bytes save-temps/429.mcf.tar.xz | Bin 135164 -> 135212 bytes save-temps/433.milc.tar.xz | Bin 850076 -> 850136 bytes save-temps/434.zeusmp.tar.xz | Bin 1165108 -> 1164884 bytes save-temps/435.gromacs.tar.xz | Bin 5454168 -> 5453936 bytes save-temps/436.cactusADM.tar.xz | Bin 4263968 -> 4263736 bytes save-temps/437.leslie3d.tar.xz | Bin 293756 -> 293760 bytes save-temps/444.namd.tar.xz | Bin 1303816 -> 1303588 bytes save-temps/445.gobmk.tar.xz | Bin 8740440 -> 8739232 bytes save-temps/447.dealII.tar.xz | Bin 29190792 -> 29190872 bytes save-temps/450.soplex.tar.xz | Bin 4635588 -> 4635688 bytes save-temps/453.povray.tar.xz | Bin 6993140 -> 7049296 bytes save-temps/454.calculix.tar.xz | Bin 8745520 -> 8743696 bytes save-temps/456.hmmer.tar.xz | Bin 1912184 -> 1911664 bytes save-temps/458.sjeng.tar.xz | Bin 674628 -> 675216 bytes save-temps/459.GemsFDTD.tar.xz | Bin 1281796 -> 1282584 bytes save-temps/462.libquantum.tar.xz | Bin 244772 -> 245464 bytes save-temps/464.h264ref.tar.xz | Bin 3063372 -> 3059228 bytes save-temps/465.tonto.tar.xz | Bin 16388528 -> 16380272 bytes save-temps/470.lbm.tar.xz | Bin 82712 -> 82940 bytes save-temps/471.omnetpp.tar.xz | Bin 6023488 -> 5966584 bytes save-temps/473.astar.tar.xz | Bin 365024 -> 364764 bytes save-temps/481.wrf.tar.xz | Bin 13136280 -> 13252480 bytes save-temps/482.sphinx3.tar.xz | Bin 1340344 -> 1336108 bytes save-temps/483.xalancbmk.tar.xz | Bin 52696664 -> 53108440 bytes 127 files changed, 1411334 insertions(+), 1468716 deletions(-) -- 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