You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The debian build is having a timeout problem building CI tests for xtensor 0.24.7 on arm64.
I don't think it's an actual bug, but I'd like to hear your recommendations for handling it.
The integer at the front of the line is timing in seconds. So compilation of test_xblockwise_reducer.cpp.o starts at 48s and is killas at 748s. Evidently the test environment has a gcc timeout of 700s. I note also the previous step before killing was launching compilation of test_xoperation.cpp.o at 92s, so many of the compilation processes are taking a long time on arm64.
For comparison, the same test on amd64 starts at 26s and reaches linking at 87s.
Are there any known issues with compilation time on arm64?
What would you recommend for managing this problem?
Some options that come to mind,
build with -O2 instead of -O3 (but that ought not to be necessary on arm64)
explicit parallel build with make -j <n> (not certain it would help. Evidently parallel compilation is already implicitly in place otherwise why would test_xblockwise_reducer.cpp.o fail after other processes were run? Could it be test_xoptional_assembly.cpp that's timing out?)
I'll be happy to test your recommendations.
The text was updated successfully, but these errors were encountered:
The debian build is having a timeout problem building CI tests for xtensor 0.24.7 on arm64.
I don't think it's an actual bug, but I'd like to hear your recommendations for handling it.
The failing test log is https://ci.debian.net/data/autopkgtest/testing/arm64/x/xtensor/41963554/log.gz
The relevant excerpt is
The integer at the front of the line is timing in seconds. So compilation of test_xblockwise_reducer.cpp.o starts at 48s and is killas at 748s. Evidently the test environment has a gcc timeout of 700s. I note also the previous step before killing was launching compilation of test_xoperation.cpp.o at 92s, so many of the compilation processes are taking a long time on arm64.
For comparison, the same test on amd64 starts at 26s and reaches linking at 87s.
Are there any known issues with compilation time on arm64?
What would you recommend for managing this problem?
Some options that come to mind,
-O2
instead of-O3
(but that ought not to be necessary on arm64)make -j <n>
(not certain it would help. Evidently parallel compilation is already implicitly in place otherwise why would test_xblockwise_reducer.cpp.o fail after other processes were run? Could it be test_xoptional_assembly.cpp that's timing out?)I'll be happy to test your recommendations.
The text was updated successfully, but these errors were encountered: