On Wed, Feb 12, 2025 at 1:17 PM ci_notify@linaro.org wrote:
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
Which version of GCC is your IC using? My patch raises the minimum GCC version to 12.1.
In glibc_build master-aarch64, after: | glibc patch https://patchwork.sourceware.org/patch/106352 | Author: H.J. Lu hjl.tools@gmail.com | Date: Wed Feb 12 12:53:09 2025 +0800 | | [PATCH] Raise the minimum GCC version to 12.1 [BZ #32539] | | For all Linux distros with glibc 2.40 which I can find, GCC 14.2 is used | to compile glibc 2.40: | | ... 52 lines of the commit log omitted. | ... applied on top of baseline commit: | 392261a2b6 hurd: Replace char foo[1024] with string_t
Produces Failure: | Results changed to | # reset_artifacts: | -10 | # init_abe_sysroot: | 0 | # build_abe glibc -- --disable install: | # FAILED | | From | # reset_artifacts: | -10 | # init_abe_sysroot: | 0 | # build_abe glibc -- --disable install: | 1
Used configuration : *CI config* tcwg_glibc_build master-aarch64 *configure and test flags:* --target aarch64-linux-gnu
If you have any questions regarding this report, please ask on linaro-toolchain@lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
The full lists of regressions and improvements as well as configure and make commands are in
The list of [ignored] baseline and flaky failures are in
Current build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-precommit/3634/ar... Reference build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2468/artifa...
Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files.
Hi H.J.,
This particular CI pipeline builds glibc using system compiler in Ubuntu 22.04 environment. So GCC version is GCC 11.4 .
-- Maxim Kuvyrkov https://www.linaro.org
On Feb 12, 2025, at 18:27, H.J. Lu hjl.tools@gmail.com wrote:
On Wed, Feb 12, 2025 at 1:17 PM ci_notify@linaro.org wrote:
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
Which version of GCC is your IC using? My patch raises the minimum GCC version to 12.1.
In glibc_build master-aarch64, after: | glibc patch https://patchwork.sourceware.org/patch/106352 | Author: H.J. Lu hjl.tools@gmail.com | Date: Wed Feb 12 12:53:09 2025 +0800 | | [PATCH] Raise the minimum GCC version to 12.1 [BZ #32539] | | For all Linux distros with glibc 2.40 which I can find, GCC 14.2 is used | to compile glibc 2.40: | | ... 52 lines of the commit log omitted. | ... applied on top of baseline commit: | 392261a2b6 hurd: Replace char foo[1024] with string_t
Produces Failure: | Results changed to | # reset_artifacts: | -10 | # init_abe_sysroot: | 0 | # build_abe glibc -- --disable install: | # FAILED | | From | # reset_artifacts: | -10 | # init_abe_sysroot: | 0 | # build_abe glibc -- --disable install: | 1
Used configuration : *CI config* tcwg_glibc_build master-aarch64 *configure and test flags:* --target aarch64-linux-gnu
If you have any questions regarding this report, please ask on linaro-toolchain@lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
The full lists of regressions and improvements as well as configure and make commands are in
The list of [ignored] baseline and flaky failures are in
Current build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-precommit/3634/ar... Reference build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2468/artifa...
Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files.
-- H.J. _______________________________________________ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-leave@lists.linaro.org
On Wed, Feb 12, 2025 at 1:48 PM Maxim Kuvyrkov maxim.kuvyrkov@linaro.org wrote:
Hi H.J.,
This particular CI pipeline builds glibc using system compiler in Ubuntu 22.04 environment. So GCC version is GCC 11.4 .
If my patch is accepted, you need to update GCC in your CI.
-- Maxim Kuvyrkov https://www.linaro.org
On Feb 12, 2025, at 18:27, H.J. Lu hjl.tools@gmail.com wrote:
On Wed, Feb 12, 2025 at 1:17 PM ci_notify@linaro.org wrote:
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
Which version of GCC is your IC using? My patch raises the minimum GCC version to 12.1.
In glibc_build master-aarch64, after: | glibc patch https://patchwork.sourceware.org/patch/106352 | Author: H.J. Lu hjl.tools@gmail.com | Date: Wed Feb 12 12:53:09 2025 +0800 | | [PATCH] Raise the minimum GCC version to 12.1 [BZ #32539] | | For all Linux distros with glibc 2.40 which I can find, GCC 14.2 is used | to compile glibc 2.40: | | ... 52 lines of the commit log omitted. | ... applied on top of baseline commit: | 392261a2b6 hurd: Replace char foo[1024] with string_t
Produces Failure: | Results changed to | # reset_artifacts: | -10 | # init_abe_sysroot: | 0 | # build_abe glibc -- --disable install: | # FAILED | | From | # reset_artifacts: | -10 | # init_abe_sysroot: | 0 | # build_abe glibc -- --disable install: | 1
Used configuration : *CI config* tcwg_glibc_build master-aarch64 *configure and test flags:* --target aarch64-linux-gnu
If you have any questions regarding this report, please ask on linaro-toolchain@lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
The full lists of regressions and improvements as well as configure and make commands are in
The list of [ignored] baseline and flaky failures are in
Current build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-precommit/3634/ar... Reference build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2468/artifa...
Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files.
-- H.J. _______________________________________________ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-leave@lists.linaro.org
On Feb 12, 2025, at 18:54, H.J. Lu hjl.tools@gmail.com wrote:
On Wed, Feb 12, 2025 at 1:48 PM Maxim Kuvyrkov maxim.kuvyrkov@linaro.org wrote:
Hi H.J.,
This particular CI pipeline builds glibc using system compiler in Ubuntu 22.04 environment. So GCC version is GCC 11.4 .
If my patch is accepted, you need to update GCC in your CI.
Yes, this is not a problem; we will switch to Ubuntu 24.04 soon.
-- Maxim Kuvyrkov https://www.linaro.org
-- Maxim Kuvyrkov https://www.linaro.org
On Feb 12, 2025, at 18:27, H.J. Lu hjl.tools@gmail.com wrote:
On Wed, Feb 12, 2025 at 1:17 PM ci_notify@linaro.org wrote:
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
Which version of GCC is your IC using? My patch raises the minimum GCC version to 12.1.
In glibc_build master-aarch64, after: | glibc patch https://patchwork.sourceware.org/patch/106352 | Author: H.J. Lu hjl.tools@gmail.com | Date: Wed Feb 12 12:53:09 2025 +0800 | | [PATCH] Raise the minimum GCC version to 12.1 [BZ #32539] | | For all Linux distros with glibc 2.40 which I can find, GCC 14.2 is used | to compile glibc 2.40: | | ... 52 lines of the commit log omitted. | ... applied on top of baseline commit: | 392261a2b6 hurd: Replace char foo[1024] with string_t
Produces Failure: | Results changed to | # reset_artifacts: | -10 | # init_abe_sysroot: | 0 | # build_abe glibc -- --disable install: | # FAILED | | From | # reset_artifacts: | -10 | # init_abe_sysroot: | 0 | # build_abe glibc -- --disable install: | 1
Used configuration : *CI config* tcwg_glibc_build master-aarch64 *configure and test flags:* --target aarch64-linux-gnu
If you have any questions regarding this report, please ask on linaro-toolchain@lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
The full lists of regressions and improvements as well as configure and make commands are in
The list of [ignored] baseline and flaky failures are in
Current build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-precommit/3634/ar... Reference build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2468/artifa...
Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files.
-- H.J. _______________________________________________ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-leave@lists.linaro.org
-- H.J.
linaro-toolchain@lists.linaro.org
-
H.J. Lu -
Maxim Kuvyrkov