Tcwg-commits November 2022

tcwg-commits@lists.linaro.org

5 participants
4683 discussions

[binutils-gdb] branch master updated (3238a750752 -> dc95ee260cc)

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 3238a750752 gas/sframe: avoid "shadowing" of glibc function name new dc95ee260cc gdb/testsuite: remove gcc restriction from gdb.dwarf2/clang [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gdb/testsuite/gdb.dwarf2/clang-cli-macro.exp | 3 --- 1 file changed, 3 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[gcc] branch master updated (09b7993ab6d -> 0f9659e7703)

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 09b7993ab6d tree-optimization/107672 - avoid vector mode type_for_mode call new 0f9659e7703 libstdc++: Fix pool resource build errors for H8 [PR107801] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: libstdc++-v3/src/c++17/memory_resource.cc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_lto updated (790261769c -> 7ff7ae96ab)

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-arm-bootstrap_lto in repository toolchain/ci/base-artifacts. from 790261769c 34: onsuccess: #152: 2: Success after binutils/gcc: 9 commits new 7ff7ae96ab 35: onsuccess: #153: 2: Success after binutils/gcc: 11 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 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 52136 -> 51928 bytes 05-build_abe-bootstrap_lto/console.log.xz | Bin 469116 -> 471040 bytes 06-check_regression/console.log.xz | Bin 2872 -> 2836 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 | 20 ++++++++++---------- 12 files changed, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-next-allnoconfig updated (8d929d2033 -> 4eaebf200d)

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-arm-next-allnoconfig in repository toolchain/ci/base-artifacts. from 8d929d2033 24: onsuccess: #383: all: Success after binutils/gcc/linux/q [...] new 4eaebf200d 25: onsuccess: #384: all: Success after binutils/gcc/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 1772 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30096 -> 29956 bytes 04-build_abe-stage1/console.log.xz | Bin 87404 -> 86644 bytes 05-build_abe-qemu/console.log.xz | Bin 31108 -> 31208 bytes 06-build_linux/console.log.xz | Bin 3168 -> 3172 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4180 -> 4124 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 | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/release-aarch64 updated (44829bebb8 -> 739e2fa216)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/release-aarch64 in repository toolchain/ci/base-artifacts. from 44829bebb8 32: onsuccess: #235: 1: Success after binutils/gcc: 9 commits new 739e2fa216 33: onsuccess: #236: 1: Success after binutils/gcc: 11 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 1668 -> 1652 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 37656 -> 37752 bytes 04-build_abe-gcc/console.log.xz | Bin 208036 -> 206040 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3860 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2340 -> 2336 bytes 07-check_regression/console.log.xz | Bin 5424 -> 5276 bytes 07-check_regression/fails.sum | 2 +- 07-check_regression/mail-body.txt | 54 +- 07-check_regression/results.compare | 23 +- 07-check_regression/results.compare2 | 54 +- 07-check_regression/results.regressions | 23 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 56 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 23 +- sumfiles/g++.log.xz | Bin 3522620 -> 3508928 bytes sumfiles/g++.sum | 118 +- sumfiles/gcc.log.xz | Bin 3003280 -> 3005128 bytes sumfiles/gcc.sum | 4617 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1036824 -> 1035568 bytes sumfiles/gfortran.sum | 92 +- sumfiles/libatomic.log.xz | Bin 2192 -> 2184 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202220 -> 202848 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2548 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 433536 -> 431380 bytes sumfiles/libstdc++.sum | 12 +- 34 files changed, 2555 insertions(+), 2575 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_eabi_stm32/gnu_eabi-master-arm_eabi-coremark-O2 updated (7b26ca0674 -> 4b0a3745e2)

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-O2 in repository toolchain/ci/base-artifacts. from 7b26ca0674 18: onsuccess: #345: 1: [TCWG CI] No change after binutils/g [...] new 4b0a3745e2 19: onsuccess: #346: 1: [TCWG CI] No change after binutils/g [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1700 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 31932 -> 31260 bytes 04-build_abe-stage1/console.log.xz | Bin 89572 -> 89084 bytes 06-build_abe-newlib/console.log.xz | Bin 16800 -> 16720 bytes 07-build_abe-stage2/console.log.xz | Bin 161460 -> 160920 bytes 08-benchmark/benchmark-build.log | 96 ++++++++++----------- 08-benchmark/benchmark.log | 94 ++++++++++---------- 08-benchmark/console.log.xz | Bin 3792 -> 3796 bytes 09-check_regression/console.log.xz | Bin 4688 -> 4884 bytes 09-check_regression/results-vs-first.log | 2 +- 09-check_regression/results-vs-prev.log | 4 +- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/Mean/results-metadata.json | 12 +-- .../squad-vs-first/coremark/results-metadata.json | 12 +-- dashboard/squad-vs-first/dashboard-push-squad.sh | 10 +-- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/newlib_rev | 2 +- mail/jira-body.txt | 28 +++--- mail/mail-body.txt | 28 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++---- results_id | 2 +- 24 files changed, 166 insertions(+), 162 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (d0af5deb57 -> 37bc5dc66e)

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_native_check_binutils/master-arm in repository toolchain/ci/base-artifacts. discards d0af5deb57 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] discards a5c9ca67f6 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] discards b8056990a5 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards f5ce690a54 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] discards 71939dc98a 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] discards be46af1ddd 104: onsuccess: #530: 1: Success after gcc: 7 commits discards 4673605634 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 83c3c31759 102: onsuccess: #527: 1: Success after binutils: 5 commits discards 6e99a01556 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 0769724829 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 8d346792cb 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 1012184d7d 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards 9e008956a0 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 226172bbbf 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 95331711cb 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards ec009382e6 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards fbfa707a15 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards fe1a5c1703 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards 148e4f7e78 91: onsuccess: #511: 1: Success after linux: 27 commits discards 74cd6be632 90: onsuccess: #510: 1: Success after glibc: 5 commits discards fd10c3aea5 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 008df7d471 88: onsuccess: #506: 1: Success after linux: 34 commits discards a01032d3a0 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 7db2e4791c 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 0a3900adb5 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 1bf61e6634 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards df234bb994 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards e894bc99ff 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards 96bd98cc9c 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 875d29db23 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 976d6ed284 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 92e2328345 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards af8602111e 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards 8d3907205a 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards 83edea58d0 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 732b0f0343 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards c53e7d8658 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards 37a80a5487 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards 87da74b40f 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards 7bd02f3eeb 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards 57466b732e 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards e9688ab0ed 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards 1a941cc0f0 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards eb155e4b0a 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards 531b79c34a 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards dbc7b97132 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards b9e1ada0ce 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards 0f79e8bc08 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards 66e1f2c276 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards 60de58428e 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards b62faa5ea8 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards aede2b8a8a 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards ed6cc3d1b8 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards 3c6f8083d4 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards 1d955f99df 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards 779b6f81e1 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards 6773cc4ec4 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards 176f3613cc 52: onsuccess: #467: 1: Success after binutils: 9 commits discards 62c897e8bf 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 82e3d9b317 50: onsuccess: #461: 1: Success after binutils: 12 commits discards c867df8c64 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] discards 22892e9d5f 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] discards 25ed65debf 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 0fb469a26b 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards 11f932f57d 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] discards e7c3612ae6 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] discards 9e3a2e9e8f 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] discards fb0ec9e5a3 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] discards b0e7326c52 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] discards 1f6bcdbef8 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] discards 102b5cbac5 39: onsuccess: #447: 1: Success after binutils: 5 commits discards 833906f841 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] discards 5b24468310 37: onsuccess: #443: 1: Success after binutils: 2 commits discards c2f68f4e60 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] discards 0814d7566f 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] discards c4c91c37a3 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] discards c4a64dceef 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] discards 9f4a2dcced 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] discards b97904859c 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] discards 7bb7f6a6b8 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] discards 75d8da61b6 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] discards 03a6ddfea5 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] discards 01db5635c0 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] discards 57b8b04bdd 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] discards 3d928bdedc 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] discards f44293ef31 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits discards ad2cb73833 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards f188f244b2 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c81758a874 21: onsuccess: 1: Successful build after linux: 79 commits discards b5c8f95f59 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 599b3c005e 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1edb5cdf69 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 77d3431ca2 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ad74332b24 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 03535c8028 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e4491fb113 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2257e45d1e 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fde594219f 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6cb6e3d19b 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7cd391f436 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8bedb56ecf 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 113f757d04 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new fcd760faf4 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f5be402a85 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6dae99d77d 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0642f48c64 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 32d1a43af6 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 580bddb62e 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9248d81b07 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f87634f3ec 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 6ea1b6e2b1 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 43e067debb 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d384945dcb 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7a64117b45 21: onsuccess: 1: Successful build after linux: 79 commits new a03c5cde71 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 8d47c5511e 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 9b20bc7c11 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits new ed8d9c6534 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] new c7a5ef1e2d 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] new fdd87720b5 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] new 65e2842fc8 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] new 713a1beb83 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] new ff953c670c 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] new 89a98f4180 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] new bbacd50232 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] new 76173ae81b 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] new 439b5b2919 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] new d5d96b303d 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] new 833be0e97d 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] new 8fc7748dc8 37: onsuccess: #443: 1: Success after binutils: 2 commits new 98866b0cda 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] new 678a024f72 39: onsuccess: #447: 1: Success after binutils: 5 commits new 25a7e8dd39 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] new 6d1b248cc0 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] new a37b157081 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] new 96419428a7 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new 7f6cb1bacd 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] new 7e7031fd16 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] new 16798529fb 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 5a9a959017 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 70187b7e33 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] new bbd37f04af 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] new 242f6edc73 50: onsuccess: #461: 1: Success after binutils: 12 commits new d6f07cca46 51: onsuccess: #464: 1: Success after binutils: 6 commits new 891db5f263 52: onsuccess: #467: 1: Success after binutils: 9 commits new feeb12e415 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new b7fbb6e4c7 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new ae7b74d944 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new 3bf4ded5d0 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new 533deedda6 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new cbb2e1c8c6 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new c389d5db82 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new 9c371b3ea1 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new 9c57f9edc5 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new 8cf0820d6c 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new 7cbf3c9f85 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new abb2555019 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 542f0c0036 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new 5d0b7a84d5 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new 825b1a844e 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 5eea50c266 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new e2dc25f36b 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new bdd6cbe3a9 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new 93f5a2cdd4 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new 58634318d5 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new 2c7bb17a69 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new 0b41ebdb4f 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new 943ac455ad 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 249ab0fd8b 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new fe6878b509 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new 1ceff7bfe2 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 7a0f04ccc8 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 3801a43188 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new a56dae8f3e 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new e4910cbf54 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new 2edd0dbd35 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new ade150a175 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 5c3c926026 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 1684b7b4f7 86: onsuccess: #503: 1: Success after binutils: 12 commits new 630d27f0df 87: onsuccess: #505: 1: Success after glibc: 7 commits new f33e2b7032 88: onsuccess: #506: 1: Success after linux: 34 commits new c690305bc3 89: onsuccess: #508: 1: Success after binutils: 12 commits new 62625c11b7 90: onsuccess: #510: 1: Success after glibc: 5 commits new 7420d1881b 91: onsuccess: #511: 1: Success after linux: 27 commits new cc57cc19be 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new 850c3dd742 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new d75043b229 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new e5418c9777 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new 7e23e51f76 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 4ef55c11d8 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 274e5aeb4c 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new d18e0df2b5 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 82c8bb0258 100: onsuccess: #521: 1: Success after binutils: 10 commits new 58cdf877d9 101: onsuccess: #524: 1: Success after binutils: 2 commits new d0c64af967 102: onsuccess: #527: 1: Success after binutils: 5 commits new 91ce07dbf8 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new bd46a610d9 104: onsuccess: #530: 1: Success after gcc: 7 commits new ddd2861d2a 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] new 120ecf07b2 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] new 681a6f4af5 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new fa769a2acc 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] new b0914f6421 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] new 37bc5dc66e 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] 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 (d0af5deb57) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] 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 1676 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 52176 -> 52976 bytes 04-build_abe-gcc/console.log.xz | Bin 234268 -> 233716 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8320 -> 8376 bytes 07-build_abe-glibc/console.log.xz | Bin 235268 -> 235516 bytes 08-build_abe-gdb/console.log.xz | Bin 51592 -> 50940 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3820 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2216 -> 2200 bytes 11-check_regression/console.log.xz | Bin 5760 -> 5692 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 34 +-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +-- sumfiles/binutils.log.xz | Bin 62300 -> 61984 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 98144 -> 98056 bytes sumfiles/gas.sum | 270 +++++++++++----------- sumfiles/ld.log.xz | Bin 131520 -> 131532 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 29 files changed, 388 insertions(+), 388 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-next-allnoconfig updated (5e2e9074a9 -> ace8b3a64a)

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-allnoconfig in repository toolchain/ci/base-artifacts. from 5e2e9074a9 23: onsuccess: #413: boot: Success after binutils/gcc/linux/ [...] new ace8b3a64a 24: onsuccess: #415: boot: Success after binutils/gcc/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 -> 1652 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30324 -> 30128 bytes 04-build_abe-stage1/console.log.xz | Bin 68860 -> 68524 bytes 05-build_abe-qemu/console.log.xz | Bin 31324 -> 30332 bytes 06-build_linux/console.log.xz | Bin 3044 -> 3124 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4148 -> 3656 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 31 +++++++++++++++---------------- 16 files changed, 22 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap updated (87015c9d2a -> a39b200bdf)

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 87015c9d2a 347: onsuccess: #1761: 2: Success after binutils/gcc: 13 commits discards 2477293c1d 346: onsuccess: #1760: 2: Success after binutils/gcc: 14 commits discards 346d338db4 345: onsuccess: #1759: 2: Success after binutils/gcc: 23 commits discards e79259276f 344: onsuccess: #1758: 2: Success after gcc: 3 commits discards 9f3b6798f6 343: onsuccess: #1757: 2: Success after binutils/gcc: 5 commits discards 32f1fbd475 342: onsuccess: #1756: 2: Success after gcc: 4 commits discards 2a0b0bc5e1 341: onsuccess: #1755: 2: Success after binutils/gcc: 3 commits discards 36d5f4afbe 340: onsuccess: #1754: 2: Success after binutils/gcc: 3 commits discards 23aaac66d4 339: onsuccess: #1753: 2: Success after binutils/gcc: 7 commits discards c0400315b0 338: onsuccess: #1752: 2: Success after binutils/gcc: 5 commits discards 7a93a81362 337: onsuccess: #1751: 2: Success after binutils/gcc: 2 commits discards 372315f940 336: onsuccess: #1750: 2: Success after binutils/gcc: 5 commits discards 36f2fb2912 335: onsuccess: #1749: 2: Success after binutils/gcc: 22 commits discards 9eb7075370 334: onsuccess: #1748: 2: Success after binutils/gcc: 9 commits discards 0b325349b9 333: onsuccess: #1747: 2: Success after binutils/gcc: 4 commits discards 224b7fc710 332: onsuccess: #1746: 2: Success after binutils/gcc: 6 commits discards 4af804dfa5 331: onsuccess: #1745: 2: Success after binutils/gcc: 14 commits discards c8215aecc1 330: onsuccess: #1744: 2: Success after binutils/gcc: 11 commits discards 115286cb02 329: onsuccess: #1743: 2: Success after binutils/gcc: 7 commits discards 9f4af60dcd 328: onsuccess: #1742: 2: Success after binutils/gcc: 14 commits discards 17d2eedc9d 327: onsuccess: #1741: 2: Success after binutils/gcc: 12 commits discards bedaba092e 326: onsuccess: #1740: 2: Success after binutils/gcc: 19 commits discards 0d1345ed47 325: onsuccess: #1739: 2: Success after gcc: 4 commits discards 3bd5b3c566 324: onsuccess: #1738: 2: Success after binutils/gcc: 18 commits discards 3e8e09712f 323: onsuccess: #1737: 2: Success after binutils/gcc: 84 commits discards 930e4a508c 322: onsuccess: #1736: 2: Success after binutils/gcc: 22 commits discards 560f4c5162 321: onsuccess: #1735: 1: Success after binutils/gcc: 54 commits discards efc99c65da 320: onsuccess: #1734: 1: Success after binutils/gcc: 4 commits discards d738fa1219 319: onsuccess: #1733: 1: Success after binutils/gcc: 8 commits discards b44aecede9 318: onsuccess: #1732: 1: Success after binutils/gcc: 2 commits discards 84e34f43ab 317: onsuccess: #1731: 1: Success after binutils/gcc: 8 commits discards c5b97ffd1f 316: onsuccess: #1730: 1: Success after binutils/gcc: 16 commits discards aaa3b31f87 315: onsuccess: #1729: 1: Success after baseline build: no n [...] discards d13158dc29 314: force: #1728: 1: Failure after basepoints/gcc-13-3918-g [...] discards bf7080f308 313: force: #1727: 2: Success after gcc: 6 commits discards d69cdb6616 312: onsuccess: #1724: 2: Success after gdb-12-branchpoint-2 [...] discards 1e44ff4b68 311: onsuccess: #1722: 2: Success after binutils/gcc: 8 commits discards a168c56ab4 310: onsuccess: #1721: 2: Success after binutils/gcc: 27 commits discards 0b220b62a8 309: onsuccess: #1720: 2: Success after binutils/gcc: 14 commits discards ab4932b1b4 308: onsuccess: #1719: 2: Success after binutils/gcc: 5 commits discards 6c0a8ac5e7 307: onsuccess: #1718: 2: Success after binutils/gcc: 22 commits discards 34227240c8 306: onsuccess: #1717: 2: Success after binutils/gcc: 12 commits discards 84e229d83a 305: onsuccess: #1716: 2: Success after binutils/gcc: 10 commits discards a36ec3a38a 304: onsuccess: #1715: 2: Success after binutils/gcc: 8 commits discards c2bdb741c3 303: onsuccess: #1714: 2: Success after binutils/gcc: 17 commits discards bb52316e12 302: onsuccess: #1713: 2: Success after binutils/gcc: 35 commits discards dab4dead96 301: onsuccess: #1711: 2: Success after gdb-12-branchpoint-2 [...] discards 8d6f5cfbea 300: onsuccess: #1709: 2: Success after binutils/gcc: 9 commits discards 6eccaa6911 299: onsuccess: #1708: 2: Success after binutils/gcc: 16 commits discards 8c94245897 298: onsuccess: #1707: 2: Success after gcc: 32 commits discards 6682cba61c 297: onsuccess: #1706: 2: Success after binutils/gcc: 9 commits discards d3a6327d94 296: onsuccess: #1705: 2: Success after binutils/gcc: 9 commits discards 9cbdfe59b5 295: onsuccess: #1704: 2: Success after binutils/gcc: 17 commits discards fdcd999358 294: onsuccess: #1703: 2: Success after binutils/gcc: 12 commits discards f839f7e056 293: onsuccess: #1702: 2: Success after binutils/gcc: 37 commits discards 611ffb99d9 292: onsuccess: #1701: 2: Success after binutils/gcc: 3 commits discards 554bf5d380 291: onsuccess: #1700: 2: Success after gcc: 4 commits discards 59167294bd 290: onsuccess: #1699: 2: Success after binutils/gcc: 5 commits discards 9ea34d9376 289: onsuccess: #1698: 2: Success after basepoints/gcc-13-37 [...] discards bf0b30039e 288: onsuccess: #1697: 2: Success after binutils/gcc: 4 commits discards df104efdea 287: onsuccess: #1696: 2: Success after gcc: 3 commits discards 65e67da134 286: onsuccess: #1695: 2: Success after binutils/gcc: 10 commits discards d30dca85d9 285: onsuccess: #1694: 2: Success after binutils: 7 commits discards f9d2516bb1 284: onsuccess: #1693: 2: Success after binutils: 2 commits discards 1ec4946c75 283: onsuccess: #1692: 2: Success after binutils/gcc: 8 commits discards 6a7f801510 282: onsuccess: #1691: 2: Success after binutils/gcc: 44 commits discards 956709575f 281: onsuccess: #1690: 2: Success after binutils/gcc: 8 commits discards a91a107bd0 280: onsuccess: #1689: 2: Success after binutils/gcc: 11 commits discards 10de2cf304 279: onsuccess: #1688: 2: Success after binutils/gcc: 23 commits discards 10be831a73 278: onsuccess: #1687: 2: Success after binutils/gcc: 12 commits discards 822327514a 277: onsuccess: #1686: 2: Success after binutils/gcc: 5 commits discards 115be00db1 276: onsuccess: #1685: 2: Success after binutils/gcc: 3 commits discards d399aaae5f 275: onsuccess: #1684: 2: Success after binutils/gcc: 11 commits discards c65eed028d 274: onsuccess: #1683: 2: Success after binutils/gcc: 10 commits discards d80632ab12 273: onsuccess: #1682: 2: Success after binutils: 3 commits discards 51e4edcdae 272: onsuccess: #1681: 2: Success after binutils/gcc: 9 commits discards 1885cf898c 271: onsuccess: #1680: 2: Success after gcc: 4 commits discards 0be641b1a2 270: onsuccess: #1679: 2: Success after binutils/gcc: 13 commits discards e8cb217c61 269: onsuccess: #1678: 2: Success after gcc: 2 commits discards d73df975bc 268: onsuccess: #1677: 2: Success after binutils/gcc: 7 commits discards ac357a521c 267: onsuccess: #1676: 2: Success after binutils/gcc: 15 commits discards 02a6039f33 266: onsuccess: #1675: 2: Success after binutils/gcc: 12 commits discards 0ef20b682e 265: onsuccess: #1674: 2: Success after binutils/gcc: 8 commits discards 237a12c44a 264: onsuccess: #1673: 2: Success after binutils/gcc: 3 commits discards 8dfbfddb1c 263: onsuccess: #1672: 2: Success after gdb-12-branchpoint-2 [...] discards f5a04d3b60 262: onsuccess: #1671: 2: Success after binutils/gcc: 2 commits discards a120e6dc5d 261: onsuccess: #1670: 2: Success after binutils/gcc: 5 commits discards 7faf9e807b 260: onsuccess: #1669: 2: Success after binutils/gcc: 17 commits discards 440b6652d1 259: onsuccess: #1668: 2: Success after binutils/gcc: 7 commits discards db6427d67c 258: onsuccess: #1667: 2: Success after binutils/gcc: 4 commits discards 243bc70d16 257: onsuccess: #1666: 2: Success after binutils/gcc: 9 commits discards f1a8433fff 256: onsuccess: #1665: 2: Success after binutils/gcc: 13 commits discards 877060d422 255: onsuccess: #1664: 2: Success after binutils/gcc: 7 commits discards a29ae7677f 254: onsuccess: #1663: 2: Success after binutils/gcc: 6 commits discards 04d85154b0 253: onsuccess: #1662: 2: Success after binutils/gcc: 6 commits discards 2f7c02af9c 252: onsuccess: #1661: 2: Success after binutils/gcc: 10 commits discards 2f6e5e2dbc 251: onsuccess: #1660: 2: Success after binutils/gcc: 6 commits discards f5047b56ca 250: onsuccess: #1659: 2: Success after binutils/gcc: 6 commits discards 0a4d123300 249: onsuccess: #1658: 2: Success after binutils/gcc: 13 commits discards 4fdb1eaeeb 248: onsuccess: #1657: 2: Success after binutils/gcc: 9 commits discards fb02222543 247: onsuccess: #1656: 2: Success after binutils/gcc: 5 commits new 28c88cb80a 247: onsuccess: #1656: 2: Success after binutils/gcc: 5 commits new 277cbf2506 248: onsuccess: #1657: 2: Success after binutils/gcc: 9 commits new cb7aaa5340 249: onsuccess: #1658: 2: Success after binutils/gcc: 13 commits new 09f14d86c8 250: onsuccess: #1659: 2: Success after binutils/gcc: 6 commits new 7f31490b3e 251: onsuccess: #1660: 2: Success after binutils/gcc: 6 commits new bea2663a95 252: onsuccess: #1661: 2: Success after binutils/gcc: 10 commits new bc90e396cb 253: onsuccess: #1662: 2: Success after binutils/gcc: 6 commits new afad39373c 254: onsuccess: #1663: 2: Success after binutils/gcc: 6 commits new 1530ae9030 255: onsuccess: #1664: 2: Success after binutils/gcc: 7 commits new f738037154 256: onsuccess: #1665: 2: Success after binutils/gcc: 13 commits new 5a3e2dc4e2 257: onsuccess: #1666: 2: Success after binutils/gcc: 9 commits new 66d9509161 258: onsuccess: #1667: 2: Success after binutils/gcc: 4 commits new 03a9757fda 259: onsuccess: #1668: 2: Success after binutils/gcc: 7 commits new d5736987d5 260: onsuccess: #1669: 2: Success after binutils/gcc: 17 commits new c7d5fe7a54 261: onsuccess: #1670: 2: Success after binutils/gcc: 5 commits new a9ede27cc6 262: onsuccess: #1671: 2: Success after binutils/gcc: 2 commits new ac3423b410 263: onsuccess: #1672: 2: Success after gdb-12-branchpoint-2 [...] new 79e737c7d0 264: onsuccess: #1673: 2: Success after binutils/gcc: 3 commits new 3a101cd742 265: onsuccess: #1674: 2: Success after binutils/gcc: 8 commits new 9f0595cb3c 266: onsuccess: #1675: 2: Success after binutils/gcc: 12 commits new 4a154688f6 267: onsuccess: #1676: 2: Success after binutils/gcc: 15 commits new 0894dd5051 268: onsuccess: #1677: 2: Success after binutils/gcc: 7 commits new 6e91da90fb 269: onsuccess: #1678: 2: Success after gcc: 2 commits new b07a82e099 270: onsuccess: #1679: 2: Success after binutils/gcc: 13 commits new f5a77c0a97 271: onsuccess: #1680: 2: Success after gcc: 4 commits new 2e68077e1a 272: onsuccess: #1681: 2: Success after binutils/gcc: 9 commits new 65cad005ee 273: onsuccess: #1682: 2: Success after binutils: 3 commits new feffbe5b9d 274: onsuccess: #1683: 2: Success after binutils/gcc: 10 commits new e90ea41c31 275: onsuccess: #1684: 2: Success after binutils/gcc: 11 commits new 2c34a10060 276: onsuccess: #1685: 2: Success after binutils/gcc: 3 commits new 01058dea1d 277: onsuccess: #1686: 2: Success after binutils/gcc: 5 commits new 1eb21195b9 278: onsuccess: #1687: 2: Success after binutils/gcc: 12 commits new 3f58ef9a43 279: onsuccess: #1688: 2: Success after binutils/gcc: 23 commits new 2c66d0051c 280: onsuccess: #1689: 2: Success after binutils/gcc: 11 commits new 655086e8a5 281: onsuccess: #1690: 2: Success after binutils/gcc: 8 commits new b576060abb 282: onsuccess: #1691: 2: Success after binutils/gcc: 44 commits new 3e4c018f49 283: onsuccess: #1692: 2: Success after binutils/gcc: 8 commits new 5891bace48 284: onsuccess: #1693: 2: Success after binutils: 2 commits new 770d6ea14a 285: onsuccess: #1694: 2: Success after binutils: 7 commits new c49062ae55 286: onsuccess: #1695: 2: Success after binutils/gcc: 10 commits new b1d76da104 287: onsuccess: #1696: 2: Success after gcc: 3 commits new 5c67519943 288: onsuccess: #1697: 2: Success after binutils/gcc: 4 commits new f7ab4bd35f 289: onsuccess: #1698: 2: Success after basepoints/gcc-13-37 [...] new eb11882e40 290: onsuccess: #1699: 2: Success after binutils/gcc: 5 commits new 4372616b8a 291: onsuccess: #1700: 2: Success after gcc: 4 commits new fbd4e4c74a 292: onsuccess: #1701: 2: Success after binutils/gcc: 3 commits new 79e78523a6 293: onsuccess: #1702: 2: Success after binutils/gcc: 37 commits new 412c1f1e4d 294: onsuccess: #1703: 2: Success after binutils/gcc: 12 commits new 8f36ce7172 295: onsuccess: #1704: 2: Success after binutils/gcc: 17 commits new 338f7c7d2a 296: onsuccess: #1705: 2: Success after binutils/gcc: 9 commits new b65833098a 297: onsuccess: #1706: 2: Success after binutils/gcc: 9 commits new 04cf62db69 298: onsuccess: #1707: 2: Success after gcc: 32 commits new a42947d388 299: onsuccess: #1708: 2: Success after binutils/gcc: 16 commits new bf3c4b8517 300: onsuccess: #1709: 2: Success after binutils/gcc: 9 commits new 10a05f7d06 301: onsuccess: #1711: 2: Success after gdb-12-branchpoint-2 [...] new 5da480e6a7 302: onsuccess: #1713: 2: Success after binutils/gcc: 35 commits new 467afa8f9d 303: onsuccess: #1714: 2: Success after binutils/gcc: 17 commits new afcabefddf 304: onsuccess: #1715: 2: Success after binutils/gcc: 8 commits new 1e1424e29c 305: onsuccess: #1716: 2: Success after binutils/gcc: 10 commits new 7e8797e1f5 306: onsuccess: #1717: 2: Success after binutils/gcc: 12 commits new 97fd96fd30 307: onsuccess: #1718: 2: Success after binutils/gcc: 22 commits new b6e0f0eda9 308: onsuccess: #1719: 2: Success after binutils/gcc: 5 commits new d976c728e4 309: onsuccess: #1720: 2: Success after binutils/gcc: 14 commits new d4616354b1 310: onsuccess: #1721: 2: Success after binutils/gcc: 27 commits new 702b10c99a 311: onsuccess: #1722: 2: Success after binutils/gcc: 8 commits new ef93083589 312: onsuccess: #1724: 2: Success after gdb-12-branchpoint-2 [...] new 899f137071 313: force: #1727: 2: Success after gcc: 6 commits new 51ef20589b 314: force: #1728: 1: Failure after basepoints/gcc-13-3918-g [...] new 04061b5b3c 315: onsuccess: #1729: 1: Success after baseline build: no n [...] new 9f1bbce9dc 316: onsuccess: #1730: 1: Success after binutils/gcc: 16 commits new 2fd8cefb00 317: onsuccess: #1731: 1: Success after binutils/gcc: 8 commits new ffaaeb8ca9 318: onsuccess: #1732: 1: Success after binutils/gcc: 2 commits new 3266a91053 319: onsuccess: #1733: 1: Success after binutils/gcc: 8 commits new df03a0da7b 320: onsuccess: #1734: 1: Success after binutils/gcc: 4 commits new 872ae40f67 321: onsuccess: #1735: 1: Success after binutils/gcc: 54 commits new 46d5190616 322: onsuccess: #1736: 2: Success after binutils/gcc: 22 commits new d95463c565 323: onsuccess: #1737: 2: Success after binutils/gcc: 84 commits new 745f79e187 324: onsuccess: #1738: 2: Success after binutils/gcc: 18 commits new 6eb942e682 325: onsuccess: #1739: 2: Success after gcc: 4 commits new 05b7efdb0c 326: onsuccess: #1740: 2: Success after binutils/gcc: 19 commits new dfdd4b82cd 327: onsuccess: #1741: 2: Success after binutils/gcc: 12 commits new 88fbb90663 328: onsuccess: #1742: 2: Success after binutils/gcc: 14 commits new b4dd569147 329: onsuccess: #1743: 2: Success after binutils/gcc: 7 commits new 9106ef7a72 330: onsuccess: #1744: 2: Success after binutils/gcc: 11 commits new 14baa490c6 331: onsuccess: #1745: 2: Success after binutils/gcc: 14 commits new 5518f98923 332: onsuccess: #1746: 2: Success after binutils/gcc: 6 commits new 2edaac024d 333: onsuccess: #1747: 2: Success after binutils/gcc: 4 commits new dd6c3a6713 334: onsuccess: #1748: 2: Success after binutils/gcc: 9 commits new ab55ea1c0f 335: onsuccess: #1749: 2: Success after binutils/gcc: 22 commits new 1e320458ae 336: onsuccess: #1750: 2: Success after binutils/gcc: 5 commits new 5f25192e20 337: onsuccess: #1751: 2: Success after binutils/gcc: 2 commits new d22205c5a8 338: onsuccess: #1752: 2: Success after binutils/gcc: 5 commits new 3aeba42df8 339: onsuccess: #1753: 2: Success after binutils/gcc: 7 commits new 060a2ece3e 340: onsuccess: #1754: 2: Success after binutils/gcc: 3 commits new 8edcb61907 341: onsuccess: #1755: 2: Success after binutils/gcc: 3 commits new caed46cd31 342: onsuccess: #1756: 2: Success after gcc: 4 commits new e8502412cc 343: onsuccess: #1757: 2: Success after binutils/gcc: 5 commits new f146444ad2 344: onsuccess: #1758: 2: Success after gcc: 3 commits new 44433ba2d0 345: onsuccess: #1759: 2: Success after binutils/gcc: 23 commits new 1b1dbe6d67 346: onsuccess: #1760: 2: Success after binutils/gcc: 14 commits new e00d52d990 347: onsuccess: #1761: 2: Success after binutils/gcc: 13 commits new a39b200bdf 348: onsuccess: #1762: 2: Success after binutils/gcc: 4 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 (87015c9d2a) \ 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 1676 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 52032 -> 52324 bytes 05-build_abe-bootstrap/console.log.xz | Bin 470680 -> 467068 bytes 06-check_regression/console.log.xz | Bin 3004 -> 2680 bytes 07-update_baseline/console.log | 34 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 13 files changed, 33 insertions(+), 33 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-mainline-allyesconfig updated (b5f44786db -> 9844a0ba80)

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-aarch64-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from b5f44786db 26: onsuccess: #392: all: Success after binutils/llvm/linux/ [...] new 9844a0ba80 27: onsuccess: #393: all: Success after binutils/llvm/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1728 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30228 -> 30200 bytes 04-build_kernel_llvm/console.log.xz | Bin 64268 -> 64516 bytes 05-build_abe-qemu/console.log.xz | Bin 31816 -> 31160 bytes 06-build_linux/console.log.xz | Bin 3184 -> 3068 bytes 07-boot_linux/console.log.xz | Bin 508 -> 504 bytes 08-check_regression/console.log.xz | Bin 4376 -> 3948 bytes 08-check_regression/mail-body.txt | 2 +- 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 19 files changed, 30 insertions(+), 30 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits November 2022