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 (0f691155d -> a9b79a93f)

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 0f691155d 9: onsuccess: #405: boot: Success after binutils/llvm/linux: [...] new a9b79a93f 10: onsuccess: #406: boot: Success after binutils/llvm/qemu: [...] 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 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 30376 -> 30156 bytes 04-build_kernel_llvm/console.log.xz | Bin 62092 -> 62776 bytes 05-build_abe-qemu/console.log.xz | Bin 31996 -> 31548 bytes 06-build_linux/console.log.xz | Bin 3892 -> 3460 bytes 07-boot_linux/console.log.xz | Bin 5852 -> 5860 bytes 08-check_regression/console.log.xz | Bin 2972 -> 2964 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_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 | 26 +++++++++++++------------- 16 files changed, 20 insertions(+), 20 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-lts-allnoconfig updated (a0790357c -> 530716c3f)

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-allnoconfig in repository toolchain/ci/base-artifacts. from a0790357c 9: onsuccess: #460: boot: Success after binutils/llvm/linux: [...] new 530716c3f 10: onsuccess: #461: boot: Success after binutils/llvm/qemu: [...] 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 2736 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30592 -> 30212 bytes 04-build_kernel_llvm/console.log.xz | Bin 64796 -> 65628 bytes 05-build_abe-qemu/console.log.xz | Bin 32200 -> 31348 bytes 06-build_linux/console.log.xz | Bin 4168 -> 3348 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 2996 -> 2960 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_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 | 26 +++++++++++++------------- 16 files changed, 20 insertions(+), 20 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_debug updated (852f921c6 -> 12d081b15)

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_debug in repository toolchain/ci/base-artifacts. from 852f921c6 12: onsuccess: #135: 2: Success after binutils/gcc: 10 commits new 12d081b15 13: onsuccess: #136: 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 1692 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 37920 -> 37752 bytes 05-build_abe-bootstrap_debug/console.log.xz | Bin 262576 -> 263744 bytes 06-check_regression/console.log.xz | Bin 2144 -> 2044 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_gcc_bootstrap/master-aarch64-bootstrap_lto updated (f6454f7af -> 90ee7d77a)

by git＠git.linaro.org

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_eabi_stm32/gnu_eabi-master-arm_eabi-coremark-O3_LTO updated (e346e1fd8 -> 28457abbd)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_gnu_eabi_stm32/gnu_eabi-master-arm_eabi-coremark-O3_LTO in repository toolchain/ci/base-artifacts. from e346e1fd8 10: onsuccess: #305: 1: [TCWG CI] No change after binutils/gc [...] new 28457abbd 11: onsuccess: #308: 1: [TCWG CI] No change after gcc: 21 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 1712 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 29884 -> 30124 bytes 04-build_abe-stage1/console.log.xz | Bin 88956 -> 88784 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-newlib/console.log.xz | Bin 16436 -> 16624 bytes 07-build_abe-stage2/console.log.xz | Bin 160728 -> 160348 bytes 08-benchmark/benchmark-build.log | 100 ++++++++++++------------- 08-benchmark/benchmark.log | 98 ++++++++++++------------ 08-benchmark/console.log.xz | Bin 3760 -> 3788 bytes 09-check_regression/console.log.xz | Bin 3736 -> 3168 bytes 09-check_regression/results.log | 78 +++++++++---------- 10-update_baseline/console.log | 8 +- dashboard/dashboard-generate.sh | 2 +- dashboard/squad/Mean/results-metadata.json | 10 +-- dashboard/squad/coremark/results-metadata.json | 10 +-- dashboard/squad/dashboard-push-squad.sh | 10 +-- git/gcc_rev | 2 +- mail/jira-body.txt | 20 ++--- mail/mail-body.txt | 20 ++--- mail/mail-subject.txt | 2 +- manifest.sh | 24 +++--- results_id | 2 +- 23 files changed, 186 insertions(+), 200 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-arm-bootstrap updated (ab36b0cad -> a9f164bd0)

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 ab36b0cad 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 988f08558 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-271 [...] discards f71c8159c 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 20deb853a 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-271 [...] discards 130a949d2 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards 832ba1b66 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards d619a0972 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards bbdfb7f40 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards b0c2bf3c8 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 43d8b5d6e 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards e1e1c3707 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards ecab5de36 99: onsuccess: #1455: 2: Success after baseline build: no new [...] discards 87287c364 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-2393 [...] discards 85d16925c 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 91cb905be 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 580b67fb8 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-2389 [...] discards 23ef84c47 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP 5 [...] discards 6f94f31b2 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards e0babab80 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards dd3ead0b2 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards d5751639d 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards f6fc52597 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards a3954bb70 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards dfc144e5c 87: onsuccess: 2: Success after gcc: 4 commits discards 9937af82e 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards 858a94998 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 7c2fd729c 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 27b034d06 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 4fa47ba9d 82: onsuccess: 1: Successful build after gcc: 3 commits discards e5499d1c9 81: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] discards 55cbd4969 80: force: 2: Successful build after gcc: 14 commits discards d9ef5a549 79: onsuccess: 2: Successful build after binutils: 5 commits discards 54a2e2e53 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards 62c336569 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 744b46b96 76: onsuccess: 2: Successful build after gcc: 12 commits discards 2e2b73678 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 321aba584 74: onsuccess: 2: Successful build after baseline build: no n [...] discards 7a2a3cc70 73: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] discards d997a82e2 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards e37267238 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 71d3b59cb 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 09118ee55 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards b190560ca 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 9a9510a0b 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 632ea0807 66: onsuccess: 2: Successful build after gcc: 9 commits discards ac3ab2caf 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 3bb47f854 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards fcf24bca4 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 4a68b6437 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 712aeb2b8 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards 9cf848c9d 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards 193ee8ac9 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] discards 5e43b2f92 58: force: 2: Successful build after gcc: 6 commits discards 6b9b74927 57: onsuccess: 2: Successful build after binutils: gdb: new ' [...] discards 1e46cac80 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards b2e43c219 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 988871b3e 54: onsuccess: 2: Successful build after gcc: 5 commits discards 1d361e139 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 7add1e434 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 96ba00465 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards b6791b9c3 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 8c8b3ada2 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 9c724b831 48: onsuccess: 2: Successful build after gcc: 4 commits discards 4d03a259b 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards e9f30a16d 46: onsuccess: 2: Successful build after baseline build: no n [...] discards a892e3e53 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards a19c3f458 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d0ceb93ff 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] discards 5ddb7c18d 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] discards e022ae7b4 41: onsuccess: 2: Successful build after gcc: libcpp: Impleme [...] discards 3b0e752fd 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 6ec357ce2 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards b0bb3fbd2 38: onsuccess: 2: Successful build after gcc: 2 commits discards ce3f7723e 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 7fd4e3401 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 69b1ad1f1 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards b8d59f42a 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 05a27f17b 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 2d0370042 32: onsuccess: 2: Successful build after gcc: 6 commits discards e4c8502bc 31: onsuccess: 2: Successful build after gcc: 6 commits discards 86fdc04e4 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards e2d9d0d5a 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 099147e4c 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 4940ff966 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits discards 17e060d5a 26: onsuccess: binutils-gcc: 2 discards 49abaf7c3 25: onsuccess: binutils-gcc: 2 discards 1d595e73f 24: onsuccess: binutils-gcc: 2 discards 27046cede 23: onsuccess: binutils-gcc: 2 discards 999430bd4 22: onsuccess: binutils-gcc: 2 discards ee0082290 21: onsuccess: binutils-gcc: 2 discards 40e08149d 20: onsuccess: binutils-gcc: 2 discards 2e75f9106 19: onsuccess: binutils-gcc: 2 discards 9bbcc670e 18: onsuccess: binutils-gcc: 2 discards bf64b1338 17: onsuccess: binutils-gcc: 2 discards 8fc3e3d0c 16: onsuccess: binutils-gcc: 2 discards a70202584 15: onsuccess: binutils-gcc: 2 discards 48ed1e0fd 14: onsuccess: binutils-gcc: 2 discards 726a262f6 13: onsuccess: binutils-gcc: 2 discards 1ca4f9b33 12: onsuccess: binutils-gcc: 2 discards 7fc699b9c 11: onsuccess: binutils-gcc: 2 discards 45a965cb3 10: onsuccess: binutils-gcc: 2 new 97c52f3cd 10: onsuccess: binutils-gcc: 2 new ebb6444e1 11: onsuccess: binutils-gcc: 2 new e1a1d594f 12: onsuccess: binutils-gcc: 2 new a209cd7d7 13: onsuccess: binutils-gcc: 2 new 3e5371298 14: onsuccess: binutils-gcc: 2 new f75c3e584 15: onsuccess: binutils-gcc: 2 new a37ec228f 16: onsuccess: binutils-gcc: 2 new c49d488f1 17: onsuccess: binutils-gcc: 2 new afb888227 18: onsuccess: binutils-gcc: 2 new 8b34901ae 19: onsuccess: binutils-gcc: 2 new 129bf5a88 20: onsuccess: binutils-gcc: 2 new 2128ace84 21: onsuccess: binutils-gcc: 2 new 7f0de1212 22: onsuccess: binutils-gcc: 2 new d154eb599 23: onsuccess: binutils-gcc: 2 new 6c9ae1160 24: onsuccess: binutils-gcc: 2 new de76fe1b6 25: onsuccess: binutils-gcc: 2 new 8d03a782d 26: onsuccess: binutils-gcc: 2 new 93e109c4c 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits new 07c5b7ecb 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 5c7d3922b 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 24c2585f0 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 65d3072a3 31: onsuccess: 2: Successful build after gcc: 6 commits new 3796564d3 32: onsuccess: 2: Successful build after gcc: 6 commits new 1a777e1a0 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 9662fff32 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 37b75042e 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 1359bfbe9 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits new d54ebfc80 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits new cf9f492a9 38: onsuccess: 2: Successful build after gcc: 2 commits new 37f67807b 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits new ae5d91b7a 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new eaebbcdbe 41: onsuccess: 2: Successful build after gcc: libcpp: Impleme [...] new 4e0ee620e 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] new 9e93baef4 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] new f36de423d 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new e2c080c82 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 40ab57e4f 46: onsuccess: 2: Successful build after baseline build: no n [...] new 97d436e18 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 2f27ed411 48: onsuccess: 2: Successful build after gcc: 4 commits new b909dd687 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new d2a8bf3cf 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 1d6642869 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 2a94cd07c 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new fcb4cd617 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 06cc403c7 54: onsuccess: 2: Successful build after gcc: 5 commits new e6a0c7fe0 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 7ce3ccc2a 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 3e37f78df 57: onsuccess: 2: Successful build after binutils: gdb: new ' [...] new 78f105c14 58: force: 2: Successful build after gcc: 6 commits new 49f4c9446 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] new 994c2c715 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new cbdb11b02 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new 14a2229af 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new db409ec20 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new e70a64507 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 5660ac769 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 0020f5fce 66: onsuccess: 2: Successful build after gcc: 9 commits new 56a6d9232 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new bd7aa4357 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new b69517e11 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 32b4a9514 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new f093b84dc 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 9e1e2534c 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new bb2e81156 73: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] new 239607e8b 74: onsuccess: 2: Successful build after baseline build: no n [...] new 4c09a83ac 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new cc2e523cd 76: onsuccess: 2: Successful build after gcc: 12 commits new 2ef3e1344 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 2e0da144a 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new 3d76be0a2 79: onsuccess: 2: Successful build after binutils: 5 commits new 6c713281d 80: force: 2: Successful build after gcc: 14 commits new 59dd78d77 81: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] new 2bad7465b 82: onsuccess: 1: Successful build after gcc: 3 commits new bafb2ba5f 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new be9bba1cd 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 59ab6ceb0 85: onsuccess: 2: Success after binutils/gcc: 25 commits new 6b1346789 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 805fcb015 87: onsuccess: 2: Success after gcc: 4 commits new 26af12a9c 88: onsuccess: 2: Success after binutils/gcc: 25 commits new e55590d3b 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 27667de50 90: onsuccess: 2: Success after binutils/gcc: 16 commits new 01bd4d143 91: onsuccess: 2: Success after binutils/gcc: 7 commits new e0b1903fa 92: onsuccess: 2: Success after binutils/gcc: 9 commits new 9865384b7 93: onsuccess: 2: Success after binutils/gcc: 3 commits new 5b2eedae6 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP 5 [...] new 307f96b28 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-2389 [...] new 82e077ee3 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 89dcace7e 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 61e8611a0 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-2393 [...] new b3666ca2b 99: onsuccess: #1455: 2: Success after baseline build: no new [...] new 798e95b7f 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 1c3d22721 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new 955b8e0f2 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new d65aee7e9 103: onsuccess: #1504: 2: Success after gcc: 2 commits new 2663484af 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new acdc9c0a4 105: onsuccess: #1506: 2: Success after gcc: 2 commits new b0543d660 106: onsuccess: #1507: 2: Success after gcc: 2 commits new f2d1d6180 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-271 [...] new acf671eca 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new e3a1c40a7 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-271 [...] new 20082502e 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new a9f164bd0 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 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 (ab36b0cad) \ 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 1732 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 50960 -> 50596 bytes 05-build_abe-bootstrap/console.log.xz | Bin 462500 -> 462388 bytes 06-check_regression/console.log.xz | Bin 1940 -> 1812 bytes 07-update_baseline/console.log | 40 +++++++++++++++++----------------- 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, 35 insertions(+), 35 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 (2adfa206a -> 9ca7a17df)

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 2adfa206a 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] discards a8da0c901 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] discards 7a8a678c1 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards 8b05a72c8 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 4563482b0 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards fd293db8b 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards ceb17611a 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards d80f5dee8 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards 4715bb62c 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards 85665bc36 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards d39daa612 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards b7f5b3044 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 676f2a7a1 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards e29c782e2 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 8c371a4d3 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards b340758fd 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards 3d9feecf2 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards b525ff7e8 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards e43e423aa 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards f585e0e31 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards a059c3597 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards df2e3926f 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 5ac125375 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 9c0bb3f15 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 75acce622 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 429aa3bd2 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 7c4ea452c 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 20902eae2 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards bb799d06e 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards faea5e214 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 1e8b24dcc 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9744764c1 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards 9bc994461 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 244549c5b 74: onsuccess: 1: Successful build after linux: 44 commits discards ecd220042 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 7618648ec 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 48ff41a31 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards 5699e31d1 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards 37db33b53 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 263abe492 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 78526e194 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 459661493 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 93883b81c 65: onsuccess: 1: Successful build after gcc: 4 commits discards 7235f5ef8 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c7365b387 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 569d986a4 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards ad49bd104 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards cab83a459 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 62365ffb8 59: onsuccess: 1: Successful build after glibc: 2 commits discards 97434561f 58: onsuccess: 1: Successful build after binutils: 2 commits discards cb4c9a5b7 57: onsuccess: 1: Successful build after gcc: 7 commits discards 7ec77e4d2 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b9fb0cce6 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards dbde0bb9b 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards b3db204ec 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards ac86fdf74 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 47d5a0ee8 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 18a202fd0 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e8539ce43 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 74347fdca 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 478444844 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d6f00e76f 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards faac3f953 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 8b9abcf74 44: onsuccess: 1: Successful build after linux: 34 commits discards 02e416a11 43: onsuccess: 1: Successful build after gcc: 2 commits discards 20c8452a5 42: onsuccess: 1: Successful build after baseline build: no n [...] discards 46dc21173 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f50318db8 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e6752971a 39: onsuccess: 1: Successful build after gcc: 2 commits discards 5ce2c9115 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 287623755 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 5469dc6e4 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 83ef60dad 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 4f1ca5579 34: onsuccess: 1: Successful build after gcc: 3 commits discards b6a2cd5d2 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 27a609e36 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 0490e0850 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 18bb267bc 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards b6197d919 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9ebbafc1a 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 21872ed29 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards f89509425 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 895f20ff6 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e53bbc4bd 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7e1a6ca3c 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2ac055f48 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e6016ee31 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards aef029d99 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2ba30c93f 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards dc516e545 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 30d0fc169 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b6b86948d 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards df214d17c 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a78ba5748 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 194de195c 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b9e70264c 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2ca5c67d6 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 17c1bd196 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7f3ea2cef 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8949ac312 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7ee3c50fb 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4e8d68c31 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b1bd5ec93 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 754cf1d35 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new df29d6e62 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 017711462 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2702f6e24 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 39e98d668 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 13b5ca9e9 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d0c32dab6 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 47e9b5d48 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c3185d909 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c77ce441e 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bffba1f36 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bf53d6289 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8990865bc 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new fe76aa679 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4b1a46ad7 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f80d69371 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 78ef25771 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 278c6429d 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 93066e3a5 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 3d5cfdc0b 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new b46a09a3f 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d6dd9aa5f 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 7423ee347 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 0386b44fb 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 20a83cabe 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 98173f86a 34: onsuccess: 1: Successful build after gcc: 3 commits new c47939347 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new c4a99a002 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new af5e81efd 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 4d2a67f9d 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 0926811f2 39: onsuccess: 1: Successful build after gcc: 2 commits new a8a476f23 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 13fd4b7d4 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cca7ddfcf 42: onsuccess: 1: Successful build after baseline build: no n [...] new fbdc37a08 43: onsuccess: 1: Successful build after gcc: 2 commits new ce1fd4a5b 44: onsuccess: 1: Successful build after linux: 34 commits new 783fc2af4 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new aa1edf1b7 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new cb273f2b1 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 44bb62e32 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 5a0bdda25 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 1fc83f040 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new aad476cad 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new f522c665a 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 178c6f9bc 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 45b033754 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 17f2e9332 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d9303275a 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 162262f7f 57: onsuccess: 1: Successful build after gcc: 7 commits new 5a13a4b0f 58: onsuccess: 1: Successful build after binutils: 2 commits new 9ca75f407 59: onsuccess: 1: Successful build after glibc: 2 commits new 0978232ba 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new efcbd7246 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 334b65668 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new fcbaf31e1 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 593983137 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 46c1ee477 65: onsuccess: 1: Successful build after gcc: 4 commits new 46d590cc3 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new fad236719 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new ce3b44949 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new fb055d37c 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new 796697cd0 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new 5c8d78ff5 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new d7046defd 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 797000d97 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 06beb469f 74: onsuccess: 1: Successful build after linux: 44 commits new 07c02e126 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c07372315 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 5f5311c5f 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cda3d90c5 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 05a42dbcc 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 26448a2df 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new a942f4209 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 6201e12fa 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 26cb0e50f 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new de56301f2 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 81a311ba2 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new a5b605286 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 4c16895ba 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new f231886ab 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new b1f2dc2d6 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 28898d677 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new f18290ada 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 32f5e7f15 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new 9f02947a2 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new c50b0b2d2 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new b4e32d403 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new 48a721482 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new cbc16678f 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new a4ef74894 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new 19a2cb2fb 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new ce19d36ce 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new c91c579b6 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 0343da214 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new 981dad3c3 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new 632c818f9 104: onsuccess: #1697: 1: Success after gcc: 4 commits new e94b7c45d 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new 23cef4324 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] new 0c4a2a177 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] new 9ca7a17df 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 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 (2adfa206a) \ 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 1768 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30180 -> 30020 bytes 04-build_abe-stage1/console.log.xz | Bin 90908 -> 90960 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8296 -> 8288 bytes 07-build_abe-glibc/console.log.xz | Bin 233668 -> 234264 bytes 08-build_abe-stage2/console.log.xz | Bin 223788 -> 223336 bytes 09-build_abe-gdb/console.log.xz | Bin 37344 -> 37304 bytes 10-build_abe-qemu/console.log.xz | Bin 31304 -> 31392 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2792 -> 2644 bytes 13-check_regression/console.log.xz | Bin 5404 -> 4500 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 17 - 13-check_regression/mail-body.txt | 68 +- 13-check_regression/results.compare | 58 +- 13-check_regression/results.compare2 | 82 +- 13-check_regression/results.regressions | 51 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 70 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 51 - sumfiles/g++.log.xz | Bin 2658708 -> 2647860 bytes sumfiles/g++.sum | 150 +- sumfiles/gcc.log.xz | Bin 2209524 -> 2205712 bytes sumfiles/gcc.sum | 2512 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 879452 -> 884456 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201008 -> 201116 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2660 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 424208 -> 427144 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 1510 insertions(+), 1736 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete 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

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-lts-allnoconfig updated (96fbbdea1 -> ded0edc38)

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 96fbbdea1 9: onsuccess: #231: all: Success after binutils/llvm/linux: 1 [...] new ded0edc38 10: onsuccess: #232: all: Success after binutils/llvm/qemu: 5 [...] 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 1692 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30004 -> 30032 bytes 04-build_kernel_llvm/console.log.xz | Bin 64288 -> 64676 bytes 05-build_abe-qemu/console.log.xz | Bin 31640 -> 31464 bytes 06-build_linux/console.log.xz | Bin 3888 -> 3400 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 2908 -> 2804 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_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 | 26 +++++++++++++------------- 16 files changed, 20 insertions(+), 20 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 (208bb7c4b -> 443aa9851)

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 208bb7c4b 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 94722d323 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-271 [...] discards b0ff8073c 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 83999cb0a 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 081cbfa1c 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards 2033e0b2f 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards e5f275b5b 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 4e880f0f9 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 0a8caa56a 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards ba537ba30 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards e66eb0c4e 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards b03c61f75 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 04aeddfaa 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 6318d63e9 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards ca396ccf0 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 72d382118 94: onsuccess: #1476: 2: Success after baseline build: no new [...] discards e90af6ce0 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-2393 [...] discards 66fd21edc 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 9d58c5b07 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards d9a77f575 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 8c0604c43 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 4d744a6b9 88: onsuccess: 1: Success after gcc: 20 commits discards 9f04f1d2a 87: force: 1: Failure after gcc: Fix up dump_printf_loc forma [...] discards 7e0ea5ca3 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 w [...] discards d04fb3957 85: onsuccess: 2: Success after binutils: 4 commits discards 73a017a19 84: onsuccess: 2: Success after gcc: 9 commits discards aa3769b83 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 3d523e726 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards de867070c 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 0a4f5e993 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 02df05937 79: onsuccess: 1: Successful build after gcc: 3 commits discards 6a2f086b6 78: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] discards da1210479 77: force: 2: Successful build after gcc: 32 commits discards 6031ace44 76: onsuccess: 2: Successful build after binutils: 10 commits discards 066f5d962 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 8b3a60869 74: onsuccess: 2: Successful build after gcc: 13 commits discards f13015b75 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 7ef0feacd 72: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] discards 62d86c05b 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 990518f91 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 2b13b79ed 69: onsuccess: 2: Successful build after baseline build: no n [...] discards 9d4ed5428 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 6c32ac2ee 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 860d8d4f5 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards ff2f4d5f0 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 53d39f3dd 64: onsuccess: 2: Successful build after gcc: 7 commits discards f6ba541da 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 73baa6961 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards ce63f1e78 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards d431f50b5 60: onsuccess: 1: Successful build after gcc: 15 commits discards 8de4029ad 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] discards 2e682bc34 58: force: 2: Successful build after gcc: tree.cc: Fix optimi [...] discards d6fbd02d2 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards c8e05218e 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 74a965d92 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 76c7ec749 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards cef5c4244 53: onsuccess: 2: Successful build after gcc: 5 commits discards 4d33e291c 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards cd59d05d7 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 75eb0cec5 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 399508d3b 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards ccfb29059 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 6603ae1e7 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 8873dd597 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 5eb69a213 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards a5f3f5b2b 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 16b8e360f 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] discards 6e4ad1f53 42: onsuccess: 2: Successful build after gcc: 2 commits discards 4e3c5f897 41: onsuccess: 2: Successful build after baseline build: no n [...] discards 88f9f91c7 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 880d69279 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 38443b49b 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 2b592f536 37: onsuccess: 2: Successful build after gcc: 2 commits discards 8222311dd 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards fee1af4bb 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards e09734200 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 89cef886a 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 0404e3c49 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 0822ecd20 31: onsuccess: 2: Successful build after gcc: 8 commits discards c157a5133 30: onsuccess: 2: Successful build after gcc: 7 commits discards c08b18b4f 29: onsuccess: 2: Successful build after binutils: 5 commits discards d9a26526d 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards e30b1e3d9 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 46cbe228a 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits discards ea1186019 25: onsuccess: binutils-gcc: 2 discards 6d89f22dd 24: onsuccess: binutils-gcc: 2 discards cab0bd166 23: onsuccess: binutils-gcc: 2 discards efa90b8cc 22: onsuccess: binutils-gcc: 2 discards e0d7f4a33 21: onsuccess: binutils-gcc: 2 discards ae4e1b20e 20: onsuccess: binutils-gcc: 2 discards 9543fafaf 19: onsuccess: binutils-gcc: 2 discards b6e549fa7 18: onsuccess: binutils-gcc: 2 discards f744fb4ed 17: onsuccess: binutils-gcc: 2 discards cd6209d28 16: onsuccess: binutils-gcc: 2 discards 3e902d222 15: onsuccess: binutils-gcc: 2 discards 6d817b6c2 14: onsuccess: binutils-gcc: 2 discards 4ec931d44 13: onsuccess: binutils-gcc: 2 discards 59c2382a1 12: onsuccess: binutils-gcc: 2 discards 13dac8e29 11: onsuccess: binutils-gcc: 2 discards 1ab8cbf39 10: onsuccess: binutils-gcc: 2 discards 19cb1b0f9 9: onsuccess: binutils-gcc: 2 new 34f5f53fc 9: onsuccess: binutils-gcc: 2 new 7c86fbef9 10: onsuccess: binutils-gcc: 2 new 7bc1725c3 11: onsuccess: binutils-gcc: 2 new 483c41383 12: onsuccess: binutils-gcc: 2 new f6362fd9c 13: onsuccess: binutils-gcc: 2 new fc14f3609 14: onsuccess: binutils-gcc: 2 new ef9460cba 15: onsuccess: binutils-gcc: 2 new 92cb3eaf9 16: onsuccess: binutils-gcc: 2 new 462b99d84 17: onsuccess: binutils-gcc: 2 new 5af008d5a 18: onsuccess: binutils-gcc: 2 new e58db8804 19: onsuccess: binutils-gcc: 2 new a789dd34a 20: onsuccess: binutils-gcc: 2 new 8e641856a 21: onsuccess: binutils-gcc: 2 new 813adc128 22: onsuccess: binutils-gcc: 2 new 3bf9c7cac 23: onsuccess: binutils-gcc: 2 new 0de14a84a 24: onsuccess: binutils-gcc: 2 new d259682ff 25: onsuccess: binutils-gcc: 2 new fdec07a67 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits new 536647224 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 4a62f8ee0 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 94dfe2183 29: onsuccess: 2: Successful build after binutils: 5 commits new 57e28985b 30: onsuccess: 2: Successful build after gcc: 7 commits new 292d800f4 31: onsuccess: 2: Successful build after gcc: 8 commits new 2ba09c1ee 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 0b3b63e4b 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits new be4b43483 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 24c3bba6a 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 2dbeb07f3 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 2c1c0c87f 37: onsuccess: 2: Successful build after gcc: 2 commits new 51633d89a 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits new c3859c0dc 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 947294bb4 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new c815109a0 41: onsuccess: 2: Successful build after baseline build: no n [...] new c9bee3ba2 42: onsuccess: 2: Successful build after gcc: 2 commits new 84113b19d 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] new 4c7ed9331 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 58be9d976 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new cbf895407 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new f735bdb6e 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 1bee38ab8 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 9948f6fc5 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 34f964606 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new a1a5400c3 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 1b17a8f3a 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 4b0b7b2ec 53: onsuccess: 2: Successful build after gcc: 5 commits new fd329354a 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new fc8fc3af7 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new f167745d7 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 4b2fd1988 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 542441607 58: force: 2: Successful build after gcc: tree.cc: Fix optimi [...] new fd424762d 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] new 9d7874986 60: onsuccess: 1: Successful build after gcc: 15 commits new 627e88a68 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 462ee3ab3 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 326ffd0cd 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 8a43b21ff 64: onsuccess: 2: Successful build after gcc: 7 commits new f12424d8d 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 534100a92 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 41c00c4eb 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new bd4fa5e47 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new d0e9c8045 69: onsuccess: 2: Successful build after baseline build: no n [...] new 6c5852a2b 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 0663d2458 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 5aa4c5166 72: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] new 39f9cb0ce 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new cf3e153d4 74: onsuccess: 2: Successful build after gcc: 13 commits new b1ff5c800 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new bfffd10a6 76: onsuccess: 2: Successful build after binutils: 10 commits new 33cff510b 77: force: 2: Successful build after gcc: 32 commits new 58351a8be 78: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] new 2218c73df 79: onsuccess: 1: Successful build after gcc: 3 commits new 6c38ed2c7 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new b9ff95dd4 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 07c40c0c6 82: onsuccess: 2: Success after binutils/gcc: 26 commits new fc8696562 83: onsuccess: 2: Success after binutils/gcc: 7 commits new f2a420a1c 84: onsuccess: 2: Success after gcc: 9 commits new febbf31b1 85: onsuccess: 2: Success after binutils: 4 commits new 094ad53b6 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 w [...] new 5ce15b623 87: force: 1: Failure after gcc: Fix up dump_printf_loc forma [...] new 438a8100c 88: onsuccess: 1: Success after gcc: 20 commits new 17bb7d231 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 0ce8c374d 90: onsuccess: #1472: 2: Success after gcc: 2 commits new eaf21e84b 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 6aab1beec 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 4d1196e83 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-2393 [...] new f14638c60 94: onsuccess: #1476: 2: Success after baseline build: no new [...] new 40c6d2b83 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new f4a1b75ed 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new e72a5c897 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 92abedba3 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 558c3e40b 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 0c13ed39d 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new 0b6401473 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new a34723e4f 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 2351f07b9 103: onsuccess: #1524: 2: Success after gcc: 2 commits new d8e84debc 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 92f2bc178 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 03e437fc8 106: onsuccess: #1527: 2: Success after gcc: 2 commits new f085f255a 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 62af0261b 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-271 [...] new 984ed18ee 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 443aa9851 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 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 (208bb7c4b) \ 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 1756 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 37660 -> 37792 bytes 05-build_abe-bootstrap/console.log.xz | Bin 270736 -> 267524 bytes 06-check_regression/console.log.xz | Bin 1928 -> 1816 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 (7188413ff -> 5b1d4e777)

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 7188413ff 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/gd [...] discards 417500e15 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...] discards 1c5c05d4d 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] discards fd42eac8e 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards cdfe277e6 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards c4d4ec1ce 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] discards 2a6d182ed 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 821279c40 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] discards d41d0125d 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] discards 1b68590f6 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards d25afb705 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] discards 93942c1bf 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] discards a9495eb7e 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 584db62d3 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] discards ac3c28b67 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] discards f232efbca 95: onsuccess: #1529: 7: Success after baseline build: no new [...] discards 982b1150e 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 8ce688d90 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] discards c75486ca2 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards fa93f7352 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards c2fde2634 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2b5d739fd 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 7aa2a35ce 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards cda37812b 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards f025ce448 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 7db50040b 85: onsuccess: 7: Success after gcc: 9 commits discards ca5d1f2d4 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards f65dea1e5 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 7302bee70 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 297e1cf04 81: onsuccess: 7: Successful build after gcc: 2 commits discards 903f3cd15 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards 5a6fdb29f 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 3717cc0f0 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards b5e99dfa8 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards a7e3a6e08 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards d0c152775 75: onsuccess: 7: Successful build after linux: 44 commits discards b99cb1212 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 0236b1863 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 82cd4d6b8 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 5dd20c0ee 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards a68a512de 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 261865bb2 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 28333c1a3 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 7af80d88b 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 4e43b6ce8 66: onsuccess: 7: Successful build after gcc: 3 commits discards 7bf946650 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards d9563e16b 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards a6787642a 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards 5a454856e 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards dc890bbf5 61: onsuccess: 4: Successful build after gcc: 15 commits discards b63d1a926 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards 36a8940d5 59: force: 7: Successful build after gcc: 2 commits discards 3de990cd0 58: onsuccess: 7: Successful build after glibc: 2 commits discards 1c0e9be12 57: onsuccess: 7: Successful build after gcc: 7 commits discards 76a2285f5 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 24c4d21a1 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 687cd2472 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 271b9b289 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] discards 936e4316f 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards a4bd75a8e 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards b39dd7a77 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards cc332a705 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 2a4a386cd 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards c2d73951c 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 22434522c 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 85908e790 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards acf93d684 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards 9fa0a3f52 43: onsuccess: 7: Successful build after gcc: 2 commits discards 5d0f06376 42: onsuccess: 7: Successful build after baseline build: no n [...] discards 8a6e62a6b 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards ea2631d7f 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 17af35687 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits discards 3eab0f107 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards 84e3cad05 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards ed5a06c12 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards e6f05f43b 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards bb37ef83f 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards c0a8642ef 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 6d5a80fca 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 9fe063e46 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 993b60017 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 5daa69de2 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards fca4a2f22 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards bdd560454 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 8194144da 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards cd6fd675b 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 0169b68e3 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 87d17978a 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 847ef8434 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards a02cc254a 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6c63635af 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 570a03155 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 62ca1d3a0 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 84ab4b046 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 7ef6e6baa 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 991a72936 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 85d2a92b4 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e7dab826e 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 939eed6e9 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards f996a6f47 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 5174d44d2 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new ea8860d47 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3fcf45c5c 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5dbedf611 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2fbef8f50 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 493dd1f64 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1f292e147 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 4cd8cae77 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2a1ba475a 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new fb108b8cb 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3cbdc2b98 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2b11550e7 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 095a05a91 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 0bc0c3df1 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9b8bcdb91 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 56656b490 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 6eceb0b94 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new b8719ac4b 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 70b156f6e 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 4fc0ded2c 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 0414922e1 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 48009ff30 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new be651cfa4 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 06b3da2f9 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new c6ed39774 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new c71d8579b 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 563370f5c 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 919585153 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new c8b243a53 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 1e403532b 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new a32b20206 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits new 21af8a80b 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new e874b7223 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7f1c4520d 42: onsuccess: 7: Successful build after baseline build: no n [...] new b6d883c72 43: onsuccess: 7: Successful build after gcc: 2 commits new c0ab736ab 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new d48468def 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 242dce0fc 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new b72e68739 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7fd719919 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new c569ad6da 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 31f2e4146 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 4b3e343bf 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 0ca6253cd 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new f2f634eec 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] new 183a10ce8 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 83a971766 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new dcd8651b1 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 8d4af6db3 57: onsuccess: 7: Successful build after gcc: 7 commits new c7638f5ec 58: onsuccess: 7: Successful build after glibc: 2 commits new 7ef1d4857 59: force: 7: Successful build after gcc: 2 commits new 0ddb42f0b 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new 9b1ef1487 61: onsuccess: 4: Successful build after gcc: 15 commits new 9a4c3d16f 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 1ccca755c 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new aa83fe4fc 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7b0d28576 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 746e21fa9 66: onsuccess: 7: Successful build after gcc: 3 commits new ddb423cc5 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 09c42babf 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new f2f1ab16a 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 57ffde001 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 5ee5c33c1 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new fe67c0511 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new bca4feaf8 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a49b60f67 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 03ed33e73 75: onsuccess: 7: Successful build after linux: 44 commits new b0d91fa47 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 400f55652 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new 74bfe585f 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 5a16a55ef 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new b1b2b1d23 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new cbc0594f3 81: onsuccess: 7: Successful build after gcc: 2 commits new 911424d83 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 602d106d3 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new f82a8f355 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 60a6ae383 85: onsuccess: 7: Success after gcc: 9 commits new c0f044c4d 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 1dc15b9c6 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 7f1ea066c 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 9c778f6d0 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new dff0d5ccb 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 24a657ce0 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 5b3b0c1e0 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 306fdc7bb 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] new e480c8be9 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new eab4f5841 95: onsuccess: #1529: 7: Success after baseline build: no new [...] new a34e0816d 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] new 48d2d3fdb 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] new 706b99e8f 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 8aad793d2 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] new 8850c1d97 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] new 298cb9b7f 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 95d246d35 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] new d35110f78 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] new d09ea1d25 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new ea0b0b988 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] new c1f33b0e4 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 4403d1410 107: onsuccess: #1618: 7: Success after gcc: 2 commits new a50c58803 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] new 29122c678 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...] new 86bb4b2f6 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/gd [...] new 5b1d4e777 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 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 (7188413ff) \ 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 1628 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 29928 -> 30188 bytes 05-build_abe-stage1/console.log.xz | Bin 90788 -> 91120 bytes 07-build_abe-linux/console.log.xz | Bin 8296 -> 8296 bytes 08-build_abe-glibc/console.log.xz | Bin 232900 -> 234168 bytes 09-build_abe-stage2/console.log.xz | Bin 223152 -> 224652 bytes 10-build_abe-gdb/console.log.xz | Bin 37332 -> 37412 bytes 11-build_abe-qemu/console.log.xz | Bin 31632 -> 31444 bytes 12-check_regression/console.log.xz | Bin 2580 -> 2380 bytes 13-update_baseline/console.log | 62 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +++++++++--------- 19 files changed, 54 insertions(+), 54 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