Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-defconfig updated (5d2f0228b0 -> 2595f93332)

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-next-defconfig in repository toolchain/ci/base-artifacts. from 5d2f0228b0 44: force: #520: : Failure after v6.2-rc2-5-ga7334dc70496: a [...] new 2595f93332 45: onsuccess: #521: all: Success after linux: 4316 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 1704 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 31976 -> 31932 bytes 04-build_kernel_llvm/console.log.xz | Bin 64420 -> 64672 bytes 05-build_abe-qemu/console.log.xz | Bin 31512 -> 31712 bytes 06-build_linux/console.log.xz | Bin 3080 -> 2996 bytes 07-boot_linux/console.log.xz | Bin 5912 -> 5912 bytes 08-check_regression/console.log.xz | Bin 3728 -> 2804 bytes 08-check_regression/jira-body.txt | 2 +- 08-check_regression/mail-body.txt | 8 +- 08-check_regression/mail-subject.txt | 2 +- 08-check_regression/results.regressions | 2 - 08-check_regression/trigger-bisect | 2 - 08-check_regression/trigger-notify | 0 09-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 146 -------------------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 8 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +-- results | 4 +- 27 files changed, 21 insertions(+), 186 deletions(-) delete mode 100644 08-check_regression/results.regressions delete mode 100644 08-check_regression/trigger-bisect delete mode 100644 08-check_regression/trigger-notify delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-defconfig updated (3d9d5b38b4 -> 5d2f0228b0)

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-next-defconfig in repository toolchain/ci/base-artifacts. from 3d9d5b38b4 43: force: #519: boot: Success after linux: 2 commits new 5d2f0228b0 44: force: #520: : Failure after v6.2-rc2-5-ga7334dc70496: a [...] 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 1748 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 32196 -> 31976 bytes 04-build_kernel_llvm/console.log.xz | Bin 66068 -> 64420 bytes 05-build_abe-qemu/console.log.xz | Bin 31556 -> 31512 bytes 06-build_linux/console.log.xz | Bin 3072 -> 3080 bytes 07-boot_linux/console.log.xz | Bin 6144 -> 5912 bytes 08-check_regression/console.log.xz | Bin 2660 -> 3728 bytes 08-check_regression/jira-body.txt | 2 +- 08-check_regression/mail-body.txt | 7 +- 08-check_regression/mail-subject.txt | 2 +- 08-check_regression/results.regressions | 2 + 08-check_regression/trigger-bisect | 2 + 08-check_regression/trigger-notify | 0 dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 146 ++++++++++++++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 7 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 ++-- results | 4 +- 26 files changed, 181 insertions(+), 24 deletions(-) create mode 100644 08-check_regression/results.regressions create mode 100644 08-check_regression/trigger-bisect create mode 100644 08-check_regression/trigger-notify create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/interesting-commits] branch master updated (43543189 -> 051fb71a)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from 43543189 Add entry a7334dc70496bb0cec7f1d3b1f148855951f41c5 from https [...] new 051fb71a Add entry a7334dc70496bb0cec7f1d3b1f148855951f41c5 from https [...] 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: .../tcwg_kernel/llvm-master-aarch64-next-defconfig/build_url | 2 +- .../last_good | 0 .../summary.txt | 0 .../a7334dc70496bb0cec7f1d3b1f148855951f41c5/tcwg_kernel/status.txt | 3 +++ 4 files changed, 4 insertions(+), 1 deletion(-) copy linux/sha1/{1b19c4c249a196301a2a3a69aeba2c6407dad25d => a7334dc70496bb0cec7f1 [...] copy linux/sha1/a7334dc70496bb0cec7f1d3b1f148855951f41c5/tcwg_kernel/{gnu-master-a [...] copy linux/sha1/a7334dc70496bb0cec7f1d3b1f148855951f41c5/tcwg_kernel/{gnu-master-a [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allyesconfig updated (dbbc12c210 -> 0f6c1d48cb)

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-next-allyesconfig in repository toolchain/ci/base-artifacts. from dbbc12c210 53: onsuccess: #725: 21635: Success after binutils/llvm/linu [...] new 0f6c1d48cb 54: onsuccess: #727: 21635: 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 1772 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32188 -> 32284 bytes 04-build_kernel_llvm/console.log.xz | Bin 64972 -> 65684 bytes 05-build_abe-qemu/console.log.xz | Bin 31520 -> 31796 bytes 06-build_linux/console.log.xz | Bin 4032 -> 4048 bytes 08-check_regression/console.log.xz | Bin 4468 -> 3992 bytes 08-check_regression/mail-body.txt | 2 +- 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 | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 31 +++++++++++++++---------------- 16 files changed, 24 insertions(+), 25 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-aarch64-bootstrap_lto updated (931a46f6ba -> afc028fd58)

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_lto in repository toolchain/ci/base-artifacts. from 931a46f6ba 43: onsuccess: #157: 2: Success after gcc: 5 commits new afc028fd58 44: onsuccess: #158: 2: Success after binutils/gcc: 10 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 1724 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 38076 -> 38104 bytes 05-build_abe-bootstrap_lto/console.log.xz | Bin 271548 -> 266580 bytes 06-check_regression/console.log.xz | Bin 2608 -> 2788 bytes 07-update_baseline/console.log | 9 --------- 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, 16 insertions(+), 25 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-defconfig updated (3374663cfc -> 3d9d5b38b4)

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-next-defconfig in repository toolchain/ci/base-artifacts. from 3374663cfc 42: onsuccess: #517: boot: Success after binutils/llvm/qemu: [...] new 3d9d5b38b4 43: force: #519: boot: Success after linux: 2 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 1752 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 32040 -> 32196 bytes 04-build_kernel_llvm/console.log.xz | Bin 66264 -> 66068 bytes 05-build_abe-qemu/console.log.xz | Bin 31900 -> 31556 bytes 06-build_linux/console.log.xz | Bin 3224 -> 3072 bytes 07-boot_linux/console.log.xz | Bin 6160 -> 6144 bytes 08-check_regression/console.log.xz | Bin 3848 -> 2660 bytes 08-check_regression/mail-body.txt | 2 +- 09-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 22 ++++++++++------------ results | 2 +- 17 files changed, 19 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

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

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 fcf18eb323 34: onsuccess: #435: boot: Success after binutils/llvm/linux [...] new aea6d62bff 35: onsuccess: #436: boot: Success after binutils/llvm/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1772 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 32360 -> 32556 bytes 04-build_kernel_llvm/console.log.xz | Bin 63196 -> 64580 bytes 05-build_abe-qemu/console.log.xz | Bin 31432 -> 31788 bytes 06-build_linux/console.log.xz | Bin 3544 -> 3500 bytes 07-boot_linux/console.log.xz | Bin 5876 -> 5660 bytes 08-check_regression/console.log.xz | Bin 4344 -> 4656 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 ++++++++++++++++---------------- results | 2 +- 20 files changed, 31 insertions(+), 31 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 updated (627e99e7e5 -> 8d8b3aef14)

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_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. discards 627e99e7e5 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards 3d5db1bc0f 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards cc9e327f5e 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards 43b58da191 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards 8cd89a1528 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards dbfe631456 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards 8fdd82b3bd 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards e5d3ed460d 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards 764c7381c7 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards 306ed5e3de 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards 3ae3e649b0 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards 63d4bba45d 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards c1c1259757 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards 0122bbbeaf 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards 7fba665186 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards c3380ba73b 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards 2e5c325952 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards 9db2e11f6c 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards 559298a9e1 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards e909420a85 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 5f58f51f5b 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards c1760776c7 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 0a714afbe1 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards 5a84fd142a 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards 0e560b4062 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 5fcecb7a18 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards 3a1d4b8c96 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 7b50946fc6 122: onsuccess: #909: 1: Success after linux: 2753 commits discards c34ae00436 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 50637038ea 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 2c6aae4c63 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards cb025972d9 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards 3a0407d5b9 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards 040780f0f4 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards bc87c5b63a 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards cfc7e121f7 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards 4a656e3659 113: onsuccess: #898: 1: Success after linux: 3 commits discards bb8ed9aac0 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 4af2cb16cc 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards a260756662 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards d374d8923a 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards 8438746f9f 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 98021a9e4b 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards 12711b62e4 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 7e7726f2de 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards effe0850f9 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards c76d8ddbb2 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards 3f0bb88385 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards e7340df980 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 30fa44c961 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 16e4368bff 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 3a9320ead8 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards d660c92a70 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards b1b180b79c 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 0d3f184373 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 01d9fccd82 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 86d2620f36 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards ffdc05debe 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 26f2bb520f 91: onsuccess: #870: 1: Success after binutils: 5 commits discards d4525c947d 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 847de2701f 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 6a431cdeb1 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards 88874202ee 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 6ae3c67a02 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards 88091d892e 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards 9a2837cc56 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 7309693ef7 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards cccbf1867e 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards edc714fed9 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards 9c63645623 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 45e74e3f48 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards 6d3bee41ae 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards e324765df2 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 458b0449f2 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 76cdcfda75 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards cfe9effdaa 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards c9324a8464 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards cbea667507 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 3b3be3274d 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 522808d437 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards f61c413bff 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards 090d032a9d 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards c3c37b37b9 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards d7188a95fd 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards 93d91bf5d1 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards bd7db32bdd 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 85ba129c92 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 10017896bc 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 472c6c743e 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards c9e58a64de 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards e0806ddd6c 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards a537ac8bbf 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards ebc500e271 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards b98759d839 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 0e81824920 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 89999775a6 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 7657ea4b6c 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 579ebb9ec7 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 03e178be76 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards a009eab05e 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards f694ed202a 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new c5f30095bb 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new b21f600da9 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new 7a8406b8d3 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new cfbb558533 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new c1b663ab10 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 51bf2f465d 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new ce3d381854 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 427ea5aef3 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 40e1c00d8d 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new 6fe42ba108 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new 2136a7c172 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new ed14ff952e 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new d0d6962bab 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new c532abf356 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 6620f9e36c 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new b144e2b175 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new 4f703debe3 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 4782b74595 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new e300390336 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new d671191636 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new 478f6f0f55 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new c683c0f381 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new 1182892be8 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 8d51f899d8 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 740369a317 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new a1d6cf22d8 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 59d38e6258 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 0bfd5ca42a 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new a996be0dcd 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 98175f6a61 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 066ea3aad8 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new 85571452d2 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new e7b9ef657b 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 159e2538d6 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new b65c74703a 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new 12c2257371 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new 79eebc2026 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 1dee7ddc38 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new 6bf8901836 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 96e84e17ef 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 1c03cd46bd 89: onsuccess: #864: 1: Success after binutils: 25 commits new fccfb34112 90: onsuccess: #867: 1: Success after binutils: 4 commits new a7863f14f4 91: onsuccess: #870: 1: Success after binutils: 5 commits new deedf91c96 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 025ecdd28b 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new a033ef078a 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 6538bb181c 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new 1271620258 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 232f613167 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new 8b1fe65449 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 517df4e055 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 741c74e57d 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 7ae35872d0 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 901c4ce3d5 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 5ab60cdee0 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new f9655dbd73 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 661c846a86 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 0b721320fe 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 5a5f719e53 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new 999707545a 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 358d4d6be5 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 0ff1ea9632 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 607a8a1c2b 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new ef1c70dd6b 112: onsuccess: #896: 1: Success after binutils: 24 commits new 53d6409ffb 113: onsuccess: #898: 1: Success after linux: 3 commits new ffc9ad79f7 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new 224d8fe8b9 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new 55e9864642 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new 926f0881fe 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new 698668950c 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 0bc74455ce 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new ec2d56f108 120: onsuccess: #906: 1: Success after binutils: 29 commits new bd360540cf 121: onsuccess: #908: 1: Success after glibc: 2 commits new 81c8538ed5 122: onsuccess: #909: 1: Success after linux: 2753 commits new 93a8d20387 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new fd3e1afbaa 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new e3d39ef58f 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new 65125b1df7 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new c947d06580 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 956ea08bbe 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new f1417541d0 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new abc8b9c363 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new c06fc1c517 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new 6b410c027f 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new 72e79060b8 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new a98bda7cd2 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new 08f600b304 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new fb0628af6c 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new 65936dca38 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new 6858cb20d1 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new d30ed2b9b0 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new c0df688fb7 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new af151395fd 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new 86732818a3 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new 66d16276d3 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 14a7a9f820 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new 07f72acba5 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new 51a22ced15 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new cb6065c990 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new c8ae311f61 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new b21fec841e 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new 8d8b3aef14 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (627e99e7e5) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] 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 1788 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 39572 -> 39832 bytes 04-build_abe-gcc/console.log.xz | Bin 214256 -> 214020 bytes 06-build_abe-linux/console.log.xz | Bin 8536 -> 8524 bytes 07-build_abe-glibc/console.log.xz | Bin 244300 -> 244912 bytes 08-build_abe-gdb/console.log.xz | Bin 39520 -> 39616 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2156 -> 2744 bytes 11-check_regression/console.log.xz | Bin 22700 -> 17648 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 37 +- 11-check_regression/mail-body.txt | 122 +- 11-check_regression/results.compare | 67 +- 11-check_regression/results.compare2 | 2446 +-------------- 11-check_regression/results.regressions | 67 +- 12-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 124 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 67 +- sumfiles/gdb.log.xz | Bin 1944064 -> 1969592 bytes sumfiles/gdb.sum | 4926 ++++++++++++++++++++++++++++++- 30 files changed, 5308 insertions(+), 2664 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/llvm-arm-master-Oz created (now 31c9e75474)

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-code_size-spec2k6/llvm-arm-master-Oz in repository toolchain/ci/base-artifacts. at 31c9e75474 51: onsuccess: #1: 1: [TCWG CI] No change after binutils/gcc [...] This branch includes the following new commits: new 31c9e75474 51: onsuccess: #1: 1: [TCWG CI] No change after binutils/gcc [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch releases/gcc-12 updated (eec3a65ed63 -> c142b30b3a2)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-12 in repository gcc. from eec3a65ed63 Fix problematic interaction between bitfields, unions, SSO and SRA new c142b30b3a2 Daily bump. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/ChangeLog | 15 +++++++++++++++ gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 12 ++++++++++++ 3 files changed, 28 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits January 2023