intel-mkl-tool-0.3.2: Failed to connect to s3-ap-northeast-1.amazonaws.com

[relf]

For several days now, I get the following error when compiling with linfa 0.7 with intel-mkl backend (see also in CI tests):

> cargo test --all --release --features blas,linfa/intel-mkl-static
   Compiling intel-mkl-src v0.7.0+mkl2020.1
The following warnings were emitted during compilation:

warning: intel-mkl-src@0.7.0+mkl2020.1: "Download Intel MKL archive into D:\rlafage\workspace\egobox\target\release\build\intel-mkl-src-811c06fa5efcefb9\out"

error: failed to run custom build command for `intel-mkl-src v0.7.0+mkl2020.1`

Caused by:
  process didn't exit successfully: `D:\rlafage\workspace\egobox\target\release\build\intel-mkl-src-0a864131c98c1eb7\build-script-build` (exit code: 101)
  --- stdout
  cargo:rerun-if-env-changed=MKL_STATIC_LP64_SEQ_NO_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-pc-windows-msvc
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_pc_windows_msvc
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG
  cargo:rerun-if-env-changed=MKL_STATIC_LP64_SEQ_STATIC
  cargo:rerun-if-env-changed=MKL_STATIC_LP64_SEQ_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-pc-windows-msvc
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_pc_windows_msvc
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-pc-windows-msvc
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_pc_windows_msvc
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-pc-windows-msvc
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_pc_windows_msvc
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=MKL_STATIC_LP64_SEQ_STATIC
  cargo:rerun-if-env-changed=MKL_STATIC_LP64_SEQ_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-pc-windows-msvc
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_pc_windows_msvc
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-pc-windows-msvc
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_pc_windows_msvc
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-pc-windows-msvc
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_pc_windows_msvc
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
  cargo:warning="Download Intel MKL archive into D:\rlafage\workspace\egobox\target\release\build\intel-mkl-src-811c06fa5efcefb9\out"

  --- stderr
  thread 'main' panicked at D:\rlafage\.cargo\registry\src\index.crates.io-6f17d22bba15001f\intel-mkl-tool-0.3.2+mkl2020.1\src\download.rs:38:28:
  called `Result::unwrap()` on an `Err` value: Error { description: "Timeout was reached", code: 28, extra: Some("Failed to connect to s3-ap-northeast-1.amazonaws.com port 443 after 168370 ms: Couldn't connect to server") }
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[relf]

From #76, I understand that download from S3 is obsolete. Downstream crates have to upgrade to intel-mkl-src 0.8. @termoshtt correct?

[termoshtt]

I understand that download from S3 is obsolete. Downstream crates have to upgrade to intel-mkl-src 0.8.

Yes. As reported in https://github.com/rust-math/intel-mkl-src/issues/103#issuecomment-2073195303, it looks terminated accidentally.

[relf]

Ok, thanks!