shellcheck q: We're seeing occasional "Text file b...
# general
m
shellcheck q: We're seeing occasional "Text file busy" errors when running shellcheck as a part of
pants test
(full stacktrace in thread).. Any idea why this may occur? Or what'd be useful for debugging?
Copy code
IntrinsicError: Failed to execute: Process {
    argv: [
        "./shellcheck",
        "--format=json",
        "build-support/scripts/assume-role-in-pipeline.sh",
    ],
    env: {},
    working_directory: None,
    input_digests: InputDigests {
        complete: DirectoryDigest {
            digest: Digest {
                hash: Fingerprint<d4ff85a6e4fb07c61f3c867c18f3362645f53784889da77cd7ce43e60e5aedfa>,
                size_bytes: 348,
            },
            tree: "Some(..)",
        },
        nailgun: DirectoryDigest {
            digest: Digest {
                hash: Fingerprint<e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855>,
                size_bytes: 0,
            },
            tree: "Some(..)",
        },
        inputs: DirectoryDigest {
            digest: Digest {
                hash: Fingerprint<d4ff85a6e4fb07c61f3c867c18f3362645f53784889da77cd7ce43e60e5aedfa>,
                size_bytes: 348,
            },
            tree: "Some(..)",
        },
        immutable_inputs: {},
        use_nailgun: {},
    },
    output_files: {},
    output_directories: {},
    timeout: None,
    execution_slot_variable: None,
    concurrency_available: 0,
    description: "Detect Shell imports for build-support/scripts/assume-role-in-pipeline.sh",
    level: Debug,
    append_only_caches: {},
    jdk_home: None,
    cache_scope: Always,
    execution_environment: ProcessExecutionEnvironment {
        name: None,
        platform: Linux_x86_64,
        strategy: Local,
    },
    remote_cache_speculation_delay: 0ns,
}
Error launching process: Os { code: 26, kind: ExecutableFileBusy, message: "Text file busy" }
I'm just going to disable shellcheck on this file for now, since it's not critical, but curious if folks have ideas as to what may be happening
We execute this script in our CI pipeline before we run
pants test
, so perhaps something (?) was holding onto the script even though it completed successfully?
The plot thickens (somewhat): we don't even have the shellcheck backend enabled?
c