Hi,
The HTML links in your mail aren’t usable in my locked-down corporate e-mail environment. If you could just send me a list of the names of the 83 failing Fujitsu tests, I’ll look at them immediately. (The initial ones that are quoted in the mail are working now with llvm-project/main, but I’d like to check the others.)
Thank you for paying attention.
Failing tests are followings.
Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0001.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0002.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0006.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0008.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0009.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0010.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0011.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0012.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0013.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0014.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0015.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0020.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0021.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0022.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0023.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0024.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0025.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0026.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0027.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0113.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0114.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0115.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0116.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0117.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0118.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0119.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0124.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0125.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0126.test Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0136.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0000.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0001.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0002.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0003.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0004.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0005.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0006.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0007.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0008.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0021.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0024.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0025.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0026.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0027.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0028.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0029.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0030.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0031.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0032.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0036.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0037.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0038.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0039.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0043.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0044.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0045.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0046.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0050.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0051.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0052.test Fujitsu/Fortran/1010/Fujitsu-Fortran-1010_0053.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0000.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0002.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0003.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0004.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0005.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0006.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0007.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0008.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0009.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0010.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0011.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0012.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0013.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0014.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0015.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0016.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0017.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0018.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0019.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0020.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0021.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0022.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0051.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0052.test Fujitsu/Fortran/1058/Fujitsu-Fortran-1058_0053.test
Even if HTML links are not usable from the CI system, you can find corresponding Jira issues from https://linaro.atlassian.net/issues/?filter=10629
https: // linaro.atlassian.net/issues/ ?filter=10629
(please concatenate)
The HTML links in your mail aren’t usable in my locked-down corporate e-mail environment. If you could just send me a list of the names of the 83 failing Fujitsu tests, I’ll look at them immediately. (The initial ones that are quoted in the mail are working now with llvm-project/main, but I’d like to check the others.)
From: ci_notify@linaro.org ci_notify@linaro.org Date: Monday, April 14, 2025 at 20:36 To: ohno.yasuyuki@fujitsu.com ohno.yasuyuki@fujitsu.com, itou.tetsuya@fujitsu.com itou.tetsuya@fujitsu.com, t-kawashima@fujitsu.com t-kawashima@fujitsu.com Cc: maxim.kuvyrkov@linaro.org maxim.kuvyrkov@linaro.org, Peter Klausler pklausler@nvidia.com Subject: [Linaro-TCWG-CI] llvmorg-21-init-8019-g0ae9bb96d5af: 86 regressions 14 fixes 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.
In tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after: | commit llvmorg-21-init-8019-g0ae9bb96d5af | Author: Peter Klausler pklausler@nvidia.com | Date: Wed Apr 9 12:30:33 2025 -0700 | | [flang][OpenMP] Fix regression in !$\ continuation (#134756) | | A recent patch that obviated the need to use -fopenmp when using the | compiler to preprocess in -E mode broke a case of Fortran line | continuation when using OpenMP conditional compilation lines (!$) when | ... 1 lines of the commit log omitted.
Produces 86 regressions 14 fixes: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/1008 ... | NOEXE: test-suite :: Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0001.test | NOEXE: test-suite :: Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0002.test | NOEXE: test-suite :: Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0006.test | NOEXE: test-suite :: Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0008.test | ... and 84 more | # "NOEXE" means : the test program cannot be compiled | | fixes.sum: | Running test-suite:Fujitsu/Fortran/0213 ... | NOEXE: test-suite :: Fujitsu/Fortran/0213/Fujitsu-Fortran-0213_0029.test | NOEXE: test-suite :: Fujitsu/Fortran/0213/Fujitsu-Fortran-0213_0023.test | NOEXE: test-suite :: Fujitsu/Fortran/0213/Fujitsu-Fortran-0213_0018.test | NOEXE: test-suite :: Fujitsu/Fortran/0213/Fujitsu-Fortran-0213_0024.test | ... and 10 more | # "NOEXE" means : the test program cannot be compiled
Used configuration :
- 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 : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu${LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
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 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-1665https://linaro.atlassian.net/browse/LLVM-1665. Please let us know if you have a fix.
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
- https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_v...https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays-build/737/artifact/artifacts/00-sumfiles/
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-O3-neoverse_v1-sve_v...https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays-build/737/artifact/artifacts/notify/
The list of [ignored] baseline and flaky failures are in
- https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_v...https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays-build/737/artifact/artifacts/sumfiles/xfails.xfail
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/https://github.com/fujitsu/compiler-test-suite/
Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_v...https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays-build/737/artifact/artifacts Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_v...https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays-build/730/artifact/artifacts
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/sh...https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/sha1/0ae9bb96d5af47a2426596dbd0c35e3ff0cdddcc/tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays/reproduction_instructions.txt
Full commit : https://github.com/llvm/llvm-project/commit/0ae9bb96d5af47a2426596dbd0c35e3f...https://github.com/llvm/llvm-project/commit/0ae9bb96d5af47a2426596dbd0c35e3ff0cdddcc