linaro-toolchain October 2024

linaro-toolchain@lists.linaro.org

9 participants
10 discussions

Re: [Linaro-TCWG-CI] gcc-15-4377-gf9bac2388401: Failure on aarch64

by Sam James

This is https://gcc.gnu.org/PR117177 which has a patch posted by Jakub already at https://inbox.sourceware.org/gcc-patches/ZxArjATvc%2FnI6YiO@tucnak/.

1 day, 4 hours

RE: [Linaro-TCWG-CI] llvmorg-20-init-8878-g367c3c968eb8: FAIL: 2 regressions on aarch64

by Jean Perier

Hi there! These are legitimate regressions: the code compiled to bogus BIND(C) ABI that only worked when using with Fortran to Fortran. A TODO is now correctly emitted until the proper ABI is implemented. In Fujitsu-Fortran-0379_0074 ``` function strfunc() bind(C) type,bind(C) :: str integer :: iii end type type(str) :: strfunc end function end interface type,bind(C) :: str integer :: iii end type ```` Previously, the result was passed in as a hidden extra argument, like it is done in normal Fortran ABI. On ARM, the equivalent C code is returned in registered as far as I can see: https://godbolt.org/z/nec6jbhYM 0384_0028.f90 also has BIND(C) function returning such BIND(C) types. So, both tests should not be run on ARM, or should expect a TODO error message until the feature is implemented on ARM. Jean -----Original Message----- From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Sent: Monday, October 14, 2024 11:23 PM To: ohno.yasuyuki(a)fujitsu.com; itou.tetsuya(a)fujitsu.com; t-kawashima(a)fujitsu.com Cc: maxim.kuvyrkov(a)linaro.org; Jean Perier <jperier(a)nvidia.com> Subject: [Linaro-TCWG-CI] llvmorg-20-init-8878-g367c3c968eb8: FAIL: 2 regressions on aarch64 External email: Use caution opening links or attachments Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. We track this report status in https://linaro.atlassian.net/browse/LLVM-1398 , please let us know if you are looking at the problem and/or when you have a fix. In CI config tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld after: | commit llvmorg-20-init-8878-g367c3c968eb8 | Author: jeanPerier <jperier(a)nvidia.com> | Date: Mon Oct 14 09:35:29 2024 +0200 | | [flang] correctly deal with bind(c) derived type result ABI (#111969) | | Derived type results of BIND(C) function should be returned according | the the C ABI for returning the related C struct type. | | ... 15 lines of the commit log omitted. FAIL: 2 regressions The configuration of this build is: * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld * Testsuite : cmake -GNinja -DCMAKE_C_COMPILER="$WORKSPACE/llvm-install/bin/clang" -DCMAKE_CXX_COMPILER="$WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$WORKSPACE/test/test-suite" regressions.sum: | === test-suite tests === | | Running test-suite:Fujitsu/Fortran/0379 ... | NOEXE: test-suite :: Fujitsu/Fortran/0379/Fujitsu-Fortran-0379_0074.test | | Running test-suite:Fujitsu/Fortran/0384 ... | NOEXE: test-suite :: Fujitsu/Fortran/0384/Fujitsu-Fortran-0384_0028.test | | # "NOEXE" means : the test program cannot be compiled You can find the failure logs in *.log.1.xz files in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… Full commit : https://github.com/llvm/llvm-project/commit/367c3c968eb8f29b55fb8019b2464c7…

3 days, 3 hours

[Linaro-TCWG-CI] v9.1.0-759-g07f0d32641e: Failure on aarch64

by ci_notify＠linaro.org

Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. We track this report status in https://linaro.atlassian.net/browse/GNU-1377 , please let us know if you are looking at the problem and/or when you have a fix. In master-aarch64 after: | commit v9.1.0-759-g07f0d32641e | Author: Paolo Bonzini <pbonzini(a)redhat.com> | Date: Thu Oct 3 16:28:43 2024 +0300 | | Require meson version 1.5.0 | | This is needed for Rust support. | | Signed-off-by: Paolo Bonzini <pbonzini(a)redhat.com> | ... 3 lines of the commit log omitted. The configuration of this build is: CI config tcwg_gnu_cross_build master-aarch64 configure and test flags: --target aarch64-linux-gnu Results changed to # reset_artifacts: -10 # true: 0 # build_abe binutils: 1 # build_abe stage1 --: 2 # build_abe linux: 3 # build_abe glibc: 4 # build_abe stage2 --: 5 # build_abe gdb: 6 # build_abe qemu: # FAILED From # reset_artifacts: -10 # true: 0 # build_abe binutils: 1 # build_abe stage1 --: 2 # build_abe linux: 3 # build_abe glibc: 4 # build_abe stage2 --: 5 # build_abe gdb: 6 # build_abe qemu: 7 -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/854/ar… Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/853/ar… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/qemu/s… Full commit : https://gitlab.com/qemu-project/qemu/commit/07f0d32641e04703e6ed9626d061790…

3 days, 8 hours

Re: [Linaro-TCWG-CI] llvmorg-20-init-8119-gd2408c417cfa: Failure on aarch64

by Nathan Chancellor

Thanks for the report, I have opened https://github.com/llvm/llvm-project/issues/111903 for this. On Tue, Oct 08, 2024 at 07:40:22AM +0000, ci_notify(a)linaro.org wrote: > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/LLVM-1390 , please let us know if you are looking at the problem and/or when you have a fix. > > In CI config tcwg_kernel/llvm-master-aarch64-lts-allmodconfig after: > > | commit llvmorg-20-init-8119-gd2408c417cfa > | Author: David Green <david.green(a)arm.com> > | Date: Sun Oct 6 10:44:21 2024 +0100 > | > | [InstCombine] Canonicalize more geps with constant gep bases and constant offsets. (#110033) > | > | This is another small but hopefully not performance negative step to > | canonicalizing towards i8 geps. We looks for geps with a constant offset > | base pointer of the form `gep (gep @glob, C1), x, C2` and expand the gep > | ... 2 lines of the commit log omitted. > > The configuration of this build is: > CI config tcwg_kernel/llvm-master-aarch64-lts-allmodconfig > Results changed to > # reset_artifacts: > -10 > # build_abe binutils: > -9 > # build_kernel_llvm: > -5 > # build_abe qemu: > -2 > # linux_n_obj: > 24511 > > From > # reset_artifacts: > -10 > # build_abe binutils: > -9 > # build_kernel_llvm: > -5 > # build_abe qemu: > -2 > # linux_n_obj: > 33835 > # linux build successful: > all > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-lts-allmodconfig… > Reference build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-lts-allmodconfig… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : https://github.com/llvm/llvm-project/commit/d2408c417cfa71f1786c90978856037…

1 week

[Linaro-TCWG-CI] glibc-2.40.9000-232-gd40ac01cbbc: FAIL: 5 regressions on aarch64

by ci_notify＠linaro.org

Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. We track this report status in https://linaro.atlassian.net/browse/GNU-1372 , please let us know if you are looking at the problem and/or when you have a fix. In master-aarch64 after: | commit glibc-2.40.9000-232-gd40ac01cbbc | Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> | Date: Thu Oct 3 15:41:10 2024 -0300 | | stdlib: Make abort/_Exit AS-safe (BZ 26275) | | The recursive lock used on abort does not synchronize with a new process | creation (either by fork-like interfaces or posix_spawn ones), nor it | is reinitialized after fork(). | ... 60 lines of the commit log omitted. FAIL: 5 regressions The configuration of this build is: CI config tcwg_gnu_native_check_gdb master-aarch64 configure and test flags: --target aarch64-linux-gnu regressions.sum: | === gdb tests === | | Running gdb:gdb.reverse/waitpid-reverse.exp ... | ERROR: GDB process no longer exists | UNRESOLVED: gdb.reverse/waitpid-reverse.exp: check waitpid record | UNRESOLVED: gdb.reverse/waitpid-reverse.exp: continue to breakpoint: marker2 | UNRESOLVED: gdb.reverse/waitpid-reverse.exp: reverse to marker1 | UNRESOLVED: gdb.reverse/waitpid-reverse.exp: set breakpoint at marker1 | You can find the failure logs in *.log.1.xz files in * https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1… -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1… Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=d40ac01cbbc66e6d9dbd…

1 week

Re: [Linaro-TCWG-CI] gcc-15-4016-gc534e37facc: FAIL: 1 regressions on arm

by Jonathan Wakely

On Thu, 10 Oct 2024 at 06:33, <ci_notify(a)linaro.org> wrote: > > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1370 , please let us know if you are looking at the problem and/or when you have a fix. I'm not sure what the problem is here. It looks like the build uses --enable-clocale=gnu and so I would expect the test to PASS on this target, like it does on x86_64-pc-linux-gnu. Maybe it's a newlib vs glibc difference. Looking into it ... > > In arm-eabi v7-a softfp after: > > | commit gcc-15-4016-gc534e37facc > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Tue Sep 24 23:20:56 2024 +0100 > | > | libstdc++: Populate std::time_get::get's %c format for C locale > | > | We were using the empty string "" for D_T_FMT and ERA_D_T_FMT in the C > | locale, instead of "%a %b %e %T %Y" as the C standard requires. Set it > | correctly for each locale implementation that defines time_members.cc. > | ... 18 lines of the commit log omitted. > > FAIL: 1 regressions > The configuration of this build is: > CI config tcwg_gnu_embed_check_gcc arm-eabi -marm -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=softfp > configure and test flags: --target arm-eabi --disable-multilib --with-mode=arm --with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=softfp --target_board=-marm/-march=armv7-a/-mfpu=vfpv3-d16/-mfloat-abi=softfp qemu_cpu=cortex-a9 > > regressions.sum: > | === libstdc++ tests === > | > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: 22_locale/time_get/get/wchar_t/5.cc -std=gnu++17 execution test > | > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e… > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e… > Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://github.com/gcc-mirror/gcc/commit/c534e37faccf481afa9bc28f0605ca0ec3…

1 week, 1 day

[Linaro-TCWG-CI] glibc-2.40.9000-226-g42c810c2cf3: FAIL: 1 regressions on arm

by ci_notify＠linaro.org

Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. We track this report status in https://linaro.atlassian.net/browse/GNU-1365 , please let us know if you are looking at the problem and/or when you have a fix. In glibc_check master-arm after: | commit glibc-2.40.9000-226-g42c810c2cf3 | Author: Joseph Myers <josmyers(a)redhat.com> | Date: Mon Oct 7 19:44:25 2024 +0000 | | Add freopen special-case tests: thread cancellation | | Add tests of freopen adding or removing "c" (non-cancelling I/O) from | the mode string (so completing my planned tests of freopen with | different features used in the mode strings). Note that it's in the | ... 5 lines of the commit log omitted. FAIL: 1 regressions The configuration of this build is: CI config tcwg_glibc_check master-arm configure and test flags: --target arm-linux-gnueabihf regressions.sum: | === glibc tests === | | Running glibc:. ... | FAIL: lint-makefiles | You can find the failure logs in *.log.1.xz files in * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1896/artifact/… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1896/artifact/… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1896/artifact/… -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1896/artifact/… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1894/artifact/… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=42c810c2cf3554afbdd6…

1 week, 3 days

[Linaro-TCWG-CI] llvmorg-20-init-8106-ge36a39346796: Failure on aarch64

by ci_notify＠linaro.org

1 week, 5 days

Re: [Linaro-TCWG-CI] v6.11-rc4-291-g16531118ba63: Failure on aarch64

by Nathan Chancellor

On Fri, Oct 04, 2024 at 07:05:02AM +0000, ci_notify(a)linaro.org wrote: ... > | commit v6.11-rc4-291-g16531118ba63 > | Author: Denis Benato <benato.denis96(a)gmail.com> > | Date: Sat Aug 24 16:11:22 2024 +0200 > | > | iio: bmi323: peripheral in lowest power state on suspend > | > | The bmi323 is mounted on some devices that are powered > | by an internal battery: help in reducing system overall power drain > | while the system is in s2idle or the imu driver is not loaded > | ... 5 lines of the commit log omitted. This should be fixed with https://git.kernel.org/jic23/iio/c/506a1ac4c4464a61e4336e135841067dbc040aaa which is on its way for an -rc release. Cheers, Nathan

1 week, 6 days

Re: [Linaro-TCWG-CI] llvmorg-20-init-7781-g0f973ac783aa: FAIL: 1 regressions on aarch64

by Peter Klausler

The error message for that test is correct. From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Date: Thursday, October 3, 2024 at 06:51 To: ohno.yasuyuki(a)fujitsu.com <ohno.yasuyuki(a)fujitsu.com>, itou.tetsuya(a)fujitsu.com <itou.tetsuya(a)fujitsu.com>, t-kawashima(a)fujitsu.com <t-kawashima(a)fujitsu.com> Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>, Peter Klausler <pklausler(a)nvidia.com> Subject: [Linaro-TCWG-CI] llvmorg-20-init-7781-g0f973ac783aa: FAIL: 1 regressions on aarch64 External email: Use caution opening links or attachments Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. We track this report status in https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinaro.at…<https://linaro.atlassian.net/browse/LLVM-1374> , please let us know if you are looking at the problem and/or when you have a fix. In CI config tcwg_flang_test/main-aarch64-Ofast-sve_vla after: | commit llvmorg-20-init-7781-g0f973ac783aa | Author: Peter Klausler <pklausler(a)nvidia.com> | Date: Wed Oct 2 08:54:49 2024 -0700 | | [flang] Tag warnings with LanguageFeature or UsageWarning (#110304) | | (This is a big patch, but it's nearly an NFC. No test results have | changed and all Fortran tests in the LLVM test suites work as expected.) | | ... 24 lines of the commit log omitted. FAIL: 1 regressions The configuration of this build is: * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld * Testsuite : cmake -GNinja -DCMAKE_C_COMPILER="$WORKSPACE/llvm-install/bin/clang" -DCMAKE_CXX_COMPILER="$WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$WORKSPACE/test/test-suite" regressions.sum: | === test-suite tests === | | Running test-suite:Fujitsu/Fortran/0384 ... | NOEXE: test-suite :: Fujitsu/Fortran/0384/Fujitsu-Fortran-0384_0053.test | | # "NOEXE" means : the test program cannot be compiled You can find the failure logs in *.log.1.xz files in * https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…> The full lists of regressions and improvements as well as configure and make commands are in * https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…> The list of [ignored] baseline and flaky failures are in * https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…> -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…> Reference build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…> Fujitsu testsuite : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…<https://github.com/fujitsu/compiler-test-suite/> Instruction to reproduce the build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit-us.li…<https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…> Full commit : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…<https://github.com/llvm/llvm-project/commit/0f973ac783aa100cfbce1cd2c6e8a3a…>

2 weeks

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain October 2024