Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rust error "could not rename downloaded file" #727

Closed
jforissier opened this issue Jan 29, 2024 · 3 comments
Closed

Rust error "could not rename downloaded file" #727

jforissier opened this issue Jan 29, 2024 · 3 comments
Labels

Comments

@jforissier
Copy link
Contributor

jforissier commented Jan 29, 2024

The Rust examples sometimes fail to build with "could not rename downloaded file" errors. Trying a second time "solves" the issue.

$ docker run -it --rm jforissier/optee_os_ci:qemuv8_check2
root@1c43ca64e015:/# cd ~
root@1c43ca64e015:~# ./get_optee_qemuv8.sh
[...]
root@1c43ca64e015:~# cd optee_repo_qemu_v8/build
root@1c43ca64e015:~# make -j128 buildroot SPMC_AT_EL=2 2>&1 | tee build.log
[...]
error: component download failed for cargo-x86_64-unknown-linux-gnu: could not rename downloaded file from '/root/.rustup/downloads/fc0055ac726cf9fe06dce3bfac393b2744e7ff0970766d02414c1c3e28d0eefa.partial' to '/root/.rustup/downloads/fc0055ac726cf9fe06dce3bfac393b2744e7ff0970766d02414c1c3e28d0eefa'

Attaching build.log (first build, with errors) and build2.log (second try immediately after the first one failed and without cleaning anything, OK).

b49020 added a commit to b49020/build that referenced this issue Jan 30, 2024
There has been random CI build failures reported while building Rust
examples. Most of them seems like conflicts with buildroot provided Rust
toolchain. So until those are resolved, disable default Rust examples
build for now to get the CI passing successfully.

Link: OP-TEE#727
Link: OP-TEE#728
Acked-by: Etienne Carriere <etienne.carriere@foss.st.com>
Acked-by: Jerome Forissier <jerome.forissier@linaro.org>
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
jforissier pushed a commit that referenced this issue Jan 30, 2024
There has been random CI build failures reported while building Rust
examples. Most of them seems like conflicts with buildroot provided Rust
toolchain. So until those are resolved, disable default Rust examples
build for now to get the CI passing successfully.

Link: #727
Link: #728
Acked-by: Etienne Carriere <etienne.carriere@foss.st.com>
Acked-by: Jerome Forissier <jerome.forissier@linaro.org>
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
@b49020
Copy link
Contributor

b49020 commented Feb 5, 2024

Should be fixed by: #731

b49020 added a commit to b49020/build that referenced this issue Feb 7, 2024
Buildroot provides its own Rust toolchain for various Linux user-space
components. However, that toolchain doesn't support nightly version of
Rust complier which we need for OP-TEE Rust examples for the time being.

Due to two separate Rust toolchains being used for different buildroot
components, there are conflicts [1] [2] observed leading to CI errors.
In order to fix them enable OP-TEE specific Rust toolchain specifically
to build OP-TEE Rust examples rather than enabling it for the entire
buildroot build.

Fixes: [1] OP-TEE#727
Fixes: [2] OP-TEE#728
Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
b49020 added a commit to b49020/build that referenced this issue Feb 7, 2024
Buildroot provides its own Rust toolchain for various Linux user-space
components. However, that toolchain doesn't support nightly version of
Rust complier which we need for OP-TEE Rust examples for the time being.

Due to two separate Rust toolchains being used for different buildroot
components, there are conflicts [1] [2] observed leading to CI errors.
In order to fix them enable OP-TEE specific Rust toolchain specifically
to build OP-TEE Rust examples rather than enabling it for the entire
buildroot build.

Fixes: [1] OP-TEE#727
Fixes: [2] OP-TEE#728
Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
b49020 added a commit to b49020/build that referenced this issue Feb 8, 2024
Buildroot provides its own Rust toolchain for various Linux user-space
components. However, that toolchain doesn't support nightly version of
Rust complier which we need for OP-TEE Rust examples for the time being.

Due to two separate Rust toolchains being used for different buildroot
components, there are conflicts [1] [2] observed leading to CI errors.
In order to fix them enable OP-TEE specific Rust toolchain specifically
to build OP-TEE Rust examples rather than enabling it for the entire
buildroot build.

Fixes: [1] OP-TEE#727
Fixes: [2] OP-TEE#728
Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
b49020 added a commit to b49020/build that referenced this issue Feb 8, 2024
Buildroot provides its own Rust toolchain for various Linux user-space
components. However, that toolchain doesn't support nightly version of
Rust complier which we need for OP-TEE Rust examples for the time being.

Due to two separate Rust toolchains being used for different buildroot
components, there are conflicts [1] [2] observed leading to CI errors.
In order to fix them enable OP-TEE specific Rust toolchain specifically
to build OP-TEE Rust examples rather than enabling it for the entire
buildroot build.

Fixes: [1] OP-TEE#727
Fixes: [2] OP-TEE#728
Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
@jforissier
Copy link
Contributor Author

rust-lang/rustup#988 might be relevant.

b49020 added a commit to b49020/build that referenced this issue Feb 8, 2024
Buildroot provides its own Rust toolchain for various Linux user-space
components. However, that toolchain doesn't support nightly version of
Rust complier which we need for OP-TEE Rust examples for the time being.

Due to two separate Rust toolchains being used for different buildroot
components, there are conflicts [1] [2] observed leading to CI errors.
In order to fix them enable OP-TEE specific Rust toolchain specifically
to build OP-TEE Rust examples rather than enabling it for the entire
buildroot build.

Fixes: [1] OP-TEE#727
Fixes: [2] OP-TEE#728
Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
b49020 added a commit to b49020/build that referenced this issue Feb 8, 2024
Buildroot provides its own Rust toolchain for various Linux user-space
components. However, that toolchain doesn't support nightly version of
Rust complier which we need for OP-TEE Rust examples for the time being.

Due to two separate Rust toolchains being used for different buildroot
components, there are conflicts [1] [2] observed leading to CI errors.
In order to fix them enable OP-TEE specific Rust toolchain specifically
to build OP-TEE Rust examples rather than enabling it for the entire
buildroot build.

Fixes: [1] OP-TEE#727
Fixes: [2] OP-TEE#728
Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
b49020 added a commit to b49020/build that referenced this issue Feb 9, 2024
Buildroot provides its own Rust toolchain for various Linux user-space
components. However, that toolchain doesn't support nightly version of
Rust complier which we need for OP-TEE Rust examples for the time being.

Due to two separate Rust toolchains being used for different buildroot
components, there are conflicts [1] [2] observed leading to CI errors.
In order to fix them enable OP-TEE specific Rust toolchain specifically
to build OP-TEE Rust examples rather than enabling it for the entire
buildroot build.

Fixes: [1] OP-TEE#727
Fixes: [2] OP-TEE#728
Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
b49020 added a commit to b49020/build that referenced this issue Feb 9, 2024
Buildroot provides its own Rust toolchain for various Linux user-space
components. However, that toolchain doesn't support nightly version of
Rust complier which we need for OP-TEE Rust examples for the time being.

Due to two separate Rust toolchains being used for different buildroot
components, there are conflicts [1] [2] observed leading to CI errors.
In order to fix them enable OP-TEE specific Rust toolchain specifically
to build OP-TEE Rust examples rather than enabling it for the entire
buildroot build.

Fixes: [1] OP-TEE#727
Fixes: [2] OP-TEE#728
Tested-by: Jerome Forissier <jerome.forissier@linaro.org>
Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
b49020 added a commit to b49020/build that referenced this issue Feb 9, 2024
Buildroot provides its own Rust toolchain for various Linux user-space
components. However, that toolchain doesn't support nightly version of
Rust complier which we need for OP-TEE Rust examples for the time being.

Due to two separate Rust toolchains being used for different buildroot
components, there are conflicts [1] [2] observed leading to CI errors.
In order to fix them enable OP-TEE specific Rust toolchain specifically
to build OP-TEE Rust examples rather than enabling it for the entire
buildroot build.

Fixes: [1] OP-TEE#727
Fixes: [2] OP-TEE#728
Acked-by: Jerome Forissier <jerome.forissier@linaro.org>
Tested-by: Jerome Forissier <jerome.forissier@linaro.org>
Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
jforissier pushed a commit that referenced this issue Feb 9, 2024
Buildroot provides its own Rust toolchain for various Linux user-space
components. However, that toolchain doesn't support nightly version of
Rust complier which we need for OP-TEE Rust examples for the time being.

Due to two separate Rust toolchains being used for different buildroot
components, there are conflicts [1] [2] observed leading to CI errors.
In order to fix them enable OP-TEE specific Rust toolchain specifically
to build OP-TEE Rust examples rather than enabling it for the entire
buildroot build.

Fixes: [1] #727
Fixes: [2] #728
Acked-by: Jerome Forissier <jerome.forissier@linaro.org>
Tested-by: Jerome Forissier <jerome.forissier@linaro.org>
Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
Copy link

This issue has been marked as a stale issue because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 5 days. Note, that you can always re-open a closed issue at any time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants