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-aarch64-lts-defconfig updated (1606415e5 -> 61ef3a954)

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-lts-defconfig in repository toolchain/ci/base-artifacts. from 1606415e5 8: onsuccess: #458: boot: Success after binutils/llvm/linux: [...] new 61ef3a954 9: onsuccess: #459: boot: Success after binutils/llvm/linux/q [...] 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 -> 1916 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30788 -> 30668 bytes 04-build_kernel_llvm/console.log.xz | Bin 65408 -> 65176 bytes 05-build_abe-qemu/console.log.xz | Bin 31792 -> 31820 bytes 06-build_linux/console.log.xz | Bin 3460 -> 3484 bytes 07-boot_linux/console.log.xz | Bin 6052 -> 6076 bytes 08-check_regression/console.log.xz | Bin 3080 -> 3432 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 | 30 +++++++++++++++--------------- 17 files changed, 23 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/master-aarch64-bootstrap_lto updated (90ee7d77a -> cce71fb12)

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_lto in repository toolchain/ci/base-artifacts. from 90ee7d77a 44: onsuccess: #439: 2: Success after binutils/gcc: 9 commits new cce71fb12 45: onsuccess: #440: 2: Success after binutils/gcc: 37 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 1684 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2708 bytes 04-build_abe-binutils/console.log.xz | Bin 37708 -> 37632 bytes 05-build_abe-bootstrap_lto/console.log.xz | Bin 274360 -> 274576 bytes 06-check_regression/console.log.xz | Bin 2208 -> 2336 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 | 18 +++++++++--------- 12 files changed, 15 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_kernel/gnu-master-aarch64-lts-allmodconfig updated (32b9d158c -> cc887e5ec)

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-aarch64-lts-allmodconfig in repository toolchain/ci/base-artifacts. from 32b9d158c 12: onsuccess: #501: 33: Success after binutils/gcc/linux: 22 [...] new cc887e5ec 13: onsuccess: #502: 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 1724 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 30584 -> 30840 bytes 04-build_abe-stage1/console.log.xz | Bin 72180 -> 73164 bytes 05-build_abe-qemu/console.log.xz | Bin 32160 -> 31492 bytes 06-build_linux/console.log.xz | Bin 5028 -> 5664 bytes 08-check_regression/console.log.xz | Bin 3036 -> 3304 bytes 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 | 30 +++++++++++++++--------------- 16 files changed, 23 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 (2653756e0 -> 4069d92ec)

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 2653756e0 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] discards a1cd3b9af 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 4c297500c 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 525d7b214 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards cf393721f 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] discards f48d4cfe0 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] discards 3d17e3ae2 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards 77e8fdd15 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 1a0c35545 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards 71eb9ef68 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards 592b7bdd4 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards f120722ce 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards 0b3be45ea 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards cf7e0c580 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards 3b0f4d27d 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 3fe11dfa7 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards c0b9cf3e1 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards 958f2ab64 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 5339afa9d 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 6471ab73b 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards 077ed06ff 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards a4622ea93 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards fea6ee8e5 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 69004c824 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 7ee029fb8 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards b1277d5b3 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards f7aa3d99f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 65bcd0b4b 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 970ed97a0 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 90fdd4597 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 9e16b74ff 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 6723c7101 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards 860812c62 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards e5d578fcf 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards b789fc4fa 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b648edd8c 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards bb9dd63de 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards dc559bcdb 74: onsuccess: 1: Successful build after linux: 44 commits discards 859eb3bbb 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 0c4767954 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b9fb08a86 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards 3202fe833 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards b4d0cabfe 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 054343523 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 4640c0ed0 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards cb2367d13 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards bdae685c7 65: onsuccess: 1: Successful build after gcc: 4 commits discards 386e69e63 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 37292ca1a 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7c279745e 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards 9f9a4892f 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards b8a0cc473 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards e5b5b8830 59: onsuccess: 1: Successful build after glibc: 2 commits discards d08f05e39 58: onsuccess: 1: Successful build after binutils: 2 commits discards d4292a6d0 57: onsuccess: 1: Successful build after gcc: 7 commits discards 832be2a5a 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 4f354a785 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 17809806a 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 883926b59 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 50e38fd43 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards fa19fe9cf 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards dbba9723e 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c82fbc1a2 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards c0187a331 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards adbf6161d 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards aba66b044 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards ec1cfd378 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 43351edc6 44: onsuccess: 1: Successful build after linux: 34 commits discards dc356c3e2 43: onsuccess: 1: Successful build after gcc: 2 commits discards 12e55a3ca 42: onsuccess: 1: Successful build after baseline build: no n [...] discards 18390adce 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c4df25d9b 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5df8cb334 39: onsuccess: 1: Successful build after gcc: 2 commits discards a960c02bf 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 542ed5b25 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 62e87e515 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7b7a8075e 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 212d95f21 34: onsuccess: 1: Successful build after gcc: 3 commits discards 2721132c9 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a1805f971 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 35c3edb7c 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 117d0323a 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards f27ef5eec 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 83549da4a 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards fd09d07d5 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards b79d229fc 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3f71968a9 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6e6628340 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d620ee714 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 565eda05e 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 80e47128d 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 560bd6340 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9c1073202 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 615f94b07 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards abb28b027 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5485e5fce 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e8345ea70 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 97d32c963 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3f60488da 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d47d06a24 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ecd1499b9 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 692a7b297 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d883ad4cf 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 922514159 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f16288576 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 885e72632 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 95edb6d53 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a88442cb0 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 78e1db6e8 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4484bc27c 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 58486465d 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 66cbf7731 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 568332bf7 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 0d998eb37 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 472a336a6 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6ee985183 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 18395aa3c 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 84a239c2c 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 584f49b16 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 5a9fed3e9 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 78f22a30c 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new e4c3b9b12 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 66650d1f5 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new bedc410cc 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 886c9aa96 34: onsuccess: 1: Successful build after gcc: 3 commits new ffb4d4073 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new b5ce56310 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 8bec2b164 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 5aaa104ec 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 712efaf12 39: onsuccess: 1: Successful build after gcc: 2 commits new 6eedc47b6 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2e012f614 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 51d43a3ce 42: onsuccess: 1: Successful build after baseline build: no n [...] new 633dd4c5f 43: onsuccess: 1: Successful build after gcc: 2 commits new 0978ee3bd 44: onsuccess: 1: Successful build after linux: 34 commits new 2b879b135 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a406f395a 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 529f7b091 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 89bdc7700 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 292eb7d9f 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 7b664538c 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new ac5f806d6 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new fea355f54 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 808650e54 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 26d104765 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new f080fd995 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 0f6c71042 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 1107bfec7 57: onsuccess: 1: Successful build after gcc: 7 commits new 7dbde7b62 58: onsuccess: 1: Successful build after binutils: 2 commits new 8a509c9b5 59: onsuccess: 1: Successful build after glibc: 2 commits new 76c41235f 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 22cd9f145 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 9498daa5a 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new 99f1924dd 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 23e73e0cc 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 72d646050 65: onsuccess: 1: Successful build after gcc: 4 commits new 61ca6ff7c 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new f4b1a6ad1 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e0d9095bc 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 6ddcd3834 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new b6dd5ad4d 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new 95c6d6813 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new 6559f6c78 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7ab7a2bc9 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 4ee69596d 74: onsuccess: 1: Successful build after linux: 44 commits new d4bc53176 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2217cf696 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 215bf6d12 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 768d781a0 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 4d8f3ee3e 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new aab558146 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 49288cf21 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new ea771383e 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 61c010786 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 6b356500d 84: onsuccess: 1: Success after gcc/glibc: 9 commits new f8b37c805 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 14ce53da4 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new b1f1be9dd 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 9ae842e53 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new ea54ee705 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 76f7c292b 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 91b9e2e44 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 7af75383d 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new cd12590ba 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 6ff8d3470 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new 3176ee40b 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new 0cff3bfca 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 3a98e5127 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new b7c9802fc 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new 87026f2c2 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new 5628b8541 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new 13cd70847 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 48465c5eb 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new 13995f1d8 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new 063bb5e24 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 6952cceb6 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new 81fc44ba7 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] new 4203b44f6 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] new 806587768 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 794ad5f87 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new f4ffb5d87 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 9e4967cec 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] new 4069d92ec 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (2653756e0) \ 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 1720 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 29868 -> 30100 bytes 04-build_abe-stage1/console.log.xz | Bin 91072 -> 91476 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8292 -> 8612 bytes 07-build_abe-glibc/console.log.xz | Bin 234412 -> 234372 bytes 08-build_abe-stage2/console.log.xz | Bin 222944 -> 225192 bytes 09-build_abe-gdb/console.log.xz | Bin 37132 -> 37572 bytes 10-build_abe-qemu/console.log.xz | Bin 31280 -> 32200 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2540 -> 2600 bytes 13-check_regression/console.log.xz | Bin 6344 -> 6228 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 52 + 13-check_regression/results.compare | 59 +- 13-check_regression/results.compare2 | 377 +---- 13-check_regression/results.regressions | 52 + 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 | 54 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- results | 52 + sumfiles/g++.log.xz | Bin 2663728 -> 2654192 bytes sumfiles/g++.sum | 173 ++- sumfiles/gcc.log.xz | Bin 2231024 -> 2240440 bytes sumfiles/gcc.sum | 2417 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 879100 -> 886396 bytes sumfiles/gfortran.sum | 56 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201132 -> 201152 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 422400 -> 417076 bytes sumfiles/libstdc++.sum | 20 +- 45 files changed, 1758 insertions(+), 1709 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[binutils-gdb] branch master updated (63b3ec661a0 -> 7f99cbd91fc)

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 63b3ec661a0 Make stdin_event_handler static adds 7f99cbd91fc ppc/svp64: test setvl ms operand No new revisions were added by this update. Summary of changes: gas/testsuite/gas/ppc/setvl.d | 1 + gas/testsuite/gas/ppc/setvl.s | 1 + 2 files changed, 2 insertions(+) -- 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-arm-bootstrap updated (6ccd9b6d8 -> 419933674)

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-arm-bootstrap in repository toolchain/ci/base-artifacts. discards 6ccd9b6d8 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards fa1cf4e7e 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards a17eb9ddf 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards e93e5dd7c 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards ab4030eb9 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 91f3bbad5 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-271 [...] discards 29e7e4b8a 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 0d075c6ee 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-271 [...] discards 94e536e90 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards 09478b8cd 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards edb955a5f 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards fa2369354 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 2388730c7 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards de713fe34 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards 76eb0ea3d 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards 195cefca4 99: onsuccess: #1455: 2: Success after baseline build: no new [...] discards 5c548690b 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-2393 [...] discards e8c242aa4 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 3df3a1a8b 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards ce36f3c21 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-2389 [...] discards aaa200611 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP 5 [...] discards 7942cbf5f 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards 25805a1eb 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards e5c87a0bf 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards 9684f1ec0 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards e6af00dc7 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards dbe77c85a 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards 619ca9165 87: onsuccess: 2: Success after gcc: 4 commits discards d7006707c 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards dea66a65a 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 7347d2f34 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards e772b31be 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 55842c3a4 82: onsuccess: 1: Successful build after gcc: 3 commits discards 819c9e2cc 81: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] discards 8b33ce8ed 80: force: 2: Successful build after gcc: 14 commits discards 7a8f36fb7 79: onsuccess: 2: Successful build after binutils: 5 commits discards 90efe28d7 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards 154c3ea50 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 30f8d4f9f 76: onsuccess: 2: Successful build after gcc: 12 commits discards 100b3c93e 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards fe92866d9 74: onsuccess: 2: Successful build after baseline build: no n [...] discards da71c45f5 73: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] discards f4f7912b6 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards a08af603a 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards d316e5c52 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards e5e586567 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 10ac04345 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards b109102af 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 32b63c44d 66: onsuccess: 2: Successful build after gcc: 9 commits discards 63cf16a5c 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards a555b6dd0 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 79d533fd4 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards e1f7a4ff3 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards fdcc7789a 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards 6b2e83e04 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards b5b593473 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] discards 99c6e7b78 58: force: 2: Successful build after gcc: 6 commits discards ef3b87bef 57: onsuccess: 2: Successful build after binutils: gdb: new ' [...] discards b0520139c 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 8363bf7c9 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 45f0052ee 54: onsuccess: 2: Successful build after gcc: 5 commits discards 648c7a846 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards d8b7d9e31 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 7c2dd83e8 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards e95e68eb9 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 0359e97ca 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards f3f044d3a 48: onsuccess: 2: Successful build after gcc: 4 commits discards 506972cc7 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 295885646 46: onsuccess: 2: Successful build after baseline build: no n [...] discards 6d3a5efb8 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards deb52aaf6 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 7ef585a0f 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] discards fa22591aa 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] discards d2c6a8c1e 41: onsuccess: 2: Successful build after gcc: libcpp: Impleme [...] discards e02f89512 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 1810b1c76 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards b3ec2f96d 38: onsuccess: 2: Successful build after gcc: 2 commits discards 0a3edac3a 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 0e13505a7 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 00e48018d 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards d768a712b 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 8454a561d 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards af42d9942 32: onsuccess: 2: Successful build after gcc: 6 commits discards 6cbef73a9 31: onsuccess: 2: Successful build after gcc: 6 commits discards eea2494f2 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards de6f30fee 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards b7dafdf2d 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards e6d3a34c5 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits discards 4566aef77 26: onsuccess: binutils-gcc: 2 discards 0edf97a7f 25: onsuccess: binutils-gcc: 2 discards 88401e45b 24: onsuccess: binutils-gcc: 2 discards 15ed3a6b0 23: onsuccess: binutils-gcc: 2 discards c98a10127 22: onsuccess: binutils-gcc: 2 discards 024c32def 21: onsuccess: binutils-gcc: 2 discards df9090446 20: onsuccess: binutils-gcc: 2 discards dba128ac3 19: onsuccess: binutils-gcc: 2 discards fc8ad606d 18: onsuccess: binutils-gcc: 2 discards 76daacbcf 17: onsuccess: binutils-gcc: 2 discards a5dd46f8e 16: onsuccess: binutils-gcc: 2 discards 4832c3bf0 15: onsuccess: binutils-gcc: 2 discards 38552f974 14: onsuccess: binutils-gcc: 2 new f430ce624 14: onsuccess: binutils-gcc: 2 new 25b2ba642 15: onsuccess: binutils-gcc: 2 new 4b03ef04b 16: onsuccess: binutils-gcc: 2 new 6dee958cb 17: onsuccess: binutils-gcc: 2 new 7fcea13a2 18: onsuccess: binutils-gcc: 2 new 838d5dd06 19: onsuccess: binutils-gcc: 2 new b1731ec8b 20: onsuccess: binutils-gcc: 2 new 541f523fd 21: onsuccess: binutils-gcc: 2 new 13964b5f2 22: onsuccess: binutils-gcc: 2 new dc804ed7e 23: onsuccess: binutils-gcc: 2 new b96449d26 24: onsuccess: binutils-gcc: 2 new ff2b0d489 25: onsuccess: binutils-gcc: 2 new 4e94f73db 26: onsuccess: binutils-gcc: 2 new 9c5b4574a 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits new bf4b770ce 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 44b151fe7 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 39d10254e 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits new da1d7726a 31: onsuccess: 2: Successful build after gcc: 6 commits new d8b2abf98 32: onsuccess: 2: Successful build after gcc: 6 commits new 76a450619 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 5b1494543 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 654230c8c 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 58060fcb1 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 96d1e015a 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 55a08a24a 38: onsuccess: 2: Successful build after gcc: 2 commits new 5c3b10156 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 3538efc91 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 0478a90bf 41: onsuccess: 2: Successful build after gcc: libcpp: Impleme [...] new be1c2f8cb 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] new 25d139408 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] new 562f7925c 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 7fedba960 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 53330e680 46: onsuccess: 2: Successful build after baseline build: no n [...] new 6a7a6e22a 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 7dd84b1f8 48: onsuccess: 2: Successful build after gcc: 4 commits new 5980a0c08 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new d691edd58 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new a865b9878 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 7a31e4b88 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 2a88e979a 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 4d9a67f35 54: onsuccess: 2: Successful build after gcc: 5 commits new 209c1861d 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new e5664b023 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new cb23a2866 57: onsuccess: 2: Successful build after binutils: gdb: new ' [...] new 1749ab746 58: force: 2: Successful build after gcc: 6 commits new b1950f843 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] new 0d58ec21c 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 003b3d12f 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new db76c0085 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new dde2b4352 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new c78083e62 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 4856cc7b2 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new c49158034 66: onsuccess: 2: Successful build after gcc: 9 commits new 914313fc4 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new e86e9b0ab 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 085086899 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 0e5b836aa 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 28580cd73 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 506d60238 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 06e594bcf 73: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] new e328888fe 74: onsuccess: 2: Successful build after baseline build: no n [...] new 3851d1fd1 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 0cf368d9a 76: onsuccess: 2: Successful build after gcc: 12 commits new 9be32ef67 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 4192b7282 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new 0b0e23216 79: onsuccess: 2: Successful build after binutils: 5 commits new bd75260b9 80: force: 2: Successful build after gcc: 14 commits new c2538c117 81: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] new a88041e5e 82: onsuccess: 1: Successful build after gcc: 3 commits new 8a52070be 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new 08be8f1fe 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 9356c453d 85: onsuccess: 2: Success after binutils/gcc: 25 commits new 3ba54117e 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 11515d9e4 87: onsuccess: 2: Success after gcc: 4 commits new 1e84375c0 88: onsuccess: 2: Success after binutils/gcc: 25 commits new 61c2e45d2 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 03610ffd1 90: onsuccess: 2: Success after binutils/gcc: 16 commits new de5ed5893 91: onsuccess: 2: Success after binutils/gcc: 7 commits new e54374110 92: onsuccess: 2: Success after binutils/gcc: 9 commits new e22b30860 93: onsuccess: 2: Success after binutils/gcc: 3 commits new 4612f4728 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP 5 [...] new e811011ea 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-2389 [...] new be844f40c 96: onsuccess: #1452: 2: Success after gcc: 2 commits new b9837cd54 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new acc25ab2d 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-2393 [...] new d33dba3ca 99: onsuccess: #1455: 2: Success after baseline build: no new [...] new 7c72fbadf 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 1d959db18 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new f6b712bc9 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new 41380c40d 103: onsuccess: #1504: 2: Success after gcc: 2 commits new a72406231 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new f4f067e83 105: onsuccess: #1506: 2: Success after gcc: 2 commits new f96ef030e 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 3f8ce83eb 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-271 [...] new f5b107f6c 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 112ff5909 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-271 [...] new e2058e3cc 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new f87f4aa6b 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new 7621c4384 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new 061937252 113: onsuccess: #1514: 2: Success after gcc: 5 commits new d61b66196 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new 419933674 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 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 (6ccd9b6d8) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] 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 1664 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 51288 -> 50196 bytes 05-build_abe-bootstrap/console.log.xz | Bin 463956 -> 463248 bytes 06-check_regression/console.log.xz | Bin 2412 -> 2216 bytes 07-update_baseline/console.log | 58 +++++++++++++++++----------------- 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, 44 insertions(+), 44 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[binutils-gdb] branch upstream created (now 7f99cbd91fc)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch upstream in repository binutils-gdb. at 7f99cbd91fc ppc/svp64: test setvl ms operand This branch includes the following new commits: new 7f99cbd91fc ppc/svp64: test setvl ms operand 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. -- 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/gnu-release-aarch64-next-defconfig updated (b60625012 -> a1769a975)

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-release-aarch64-next-defconfig in repository toolchain/ci/base-artifacts. from b60625012 7: onsuccess: #531: boot: Success after binutils/gcc/linux: 1 [...] new a1769a975 8: onsuccess: #533: boot: Success after binutils/gcc/linux/qe [...] 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 1696 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30148 -> 30292 bytes 04-build_abe-stage1/console.log.xz | Bin 68604 -> 68436 bytes 05-build_abe-qemu/console.log.xz | Bin 31784 -> 31520 bytes 06-build_linux/console.log.xz | Bin 3052 -> 3088 bytes 07-boot_linux/console.log.xz | Bin 6092 -> 504 bytes 08-check_regression/console.log.xz | Bin 2728 -> 3216 bytes 08-check_regression/mail-body.txt | 4 ++-- dashboard/dashboard-generate.sh | 2 +- dashboard/squad/dashboard-push-squad.sh | 18 ------------------ dashboard/squad/results-functional.json | 1 + dashboard/squad/summary-annotation.txt | 0 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 | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- results | 2 +- 22 files changed, 29 insertions(+), 46 deletions(-) delete mode 100755 dashboard/squad/dashboard-push-squad.sh create mode 100644 dashboard/squad/results-functional.json delete mode 100644 dashboard/squad/summary-annotation.txt -- 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 (ec3178779 -> 38d528b20)

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 ec3178779 12: onsuccess: #121: 2: Success after binutils/gcc: 10 commits new 38d528b20 13: onsuccess: #122: 2: Success after binutils/gcc: 8 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 1696 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2712 bytes 04-build_abe-binutils/console.log.xz | Bin 37420 -> 37700 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 507140 -> 509172 bytes 06-check_regression/console.log.xz | Bin 2144 -> 2040 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 | 18 +++++++++--------- 12 files changed, 15 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[gcc] branch master updated (5976fbf9d5d -> 59f6dea963b)

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 5976fbf9d5d Fortran: error recovery on invalid ARRAY argument to FINDLO [...] new 59f6dea963b Fortran: F2018 type(*),dimension(*) with scalars [PR104143] 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: gcc/fortran/interface.cc | 11 ++++++++++- gcc/testsuite/gfortran.dg/assumed_type_16.f90 | 14 ++++++++++++++ gcc/testsuite/gfortran.dg/assumed_type_17.f90 | 18 ++++++++++++++++++ gcc/testsuite/gfortran.dg/c-interop/c407b-2.f90 | 2 +- 4 files changed, 43 insertions(+), 2 deletions(-) create mode 100644 gcc/testsuite/gfortran.dg/assumed_type_16.f90 create mode 100644 gcc/testsuite/gfortran.dg/assumed_type_17.f90 -- 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