-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Closed
Description
Android CI is still unstable due to random errors of Text file busy.
Example attachted.
The crate beeing affected seems to be rather random each time.
As I think this is an issue with the build system itself, I don't know how to easily fix this.
From my experience "Text file busy" means that an other process is blocking the file such that it can't be accessed.
Maybe this is a race-condition that happens when the creation of the file is not yet fully finished and its already accessed for execution?
Anyway I suggest to implement a workaround that just retries the build 3 times before stopping.
I can implement this.
[2024-02-20 17:00:18] Compiling libc v0.2.153
[2024-02-20 17:00:18] Compiling cfg-if v1.0.0
[2024-02-20 17:00:18] Compiling typenum v1.15.0
[2024-02-20 17:00:18] Compiling version_check v0.9.4
[2024-02-20 17:00:18] Compiling bitflags v1.3.2
[2024-02-20 17:00:18] Compiling io-lifetimes v1.0.11
[2024-02-20 17:00:18] Compiling proc-macro2 v1.0.63
[2024-02-20 17:00:18] error: failed to run custom build command for `libc v0.2.153`
[2024-02-20 17:00:18]
[2024-02-20 17:00:18] Caused by:
[2024-02-20 17:00:18] could not execute process `/data/data/com.termux/files/home/coreutils/target/debug/build/libc-db86c7903a93619b/build-script-build` (never executed)
[2024-02-20 17:00:18]
[2024-02-20 17:00:18] Caused by:
[2024-02-20 17:00:18] Text file busy (os error 26)
[2024-02-20 17:00:18] warning: build failed, waiting for other jobs to finish...
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels