The lance-bench FTS index job fails while building Lance at commit .\n\nBenchmark run: https://github.com/lancedb/lance-bench/actions/runs/29415334699\nJob: \nFailed step: \n\nThe benchmark updates its Lance git dependencies to the tested SHA and runs:\n\n\n\nBuild output:\n\nCStringCStringgoosefs-sdk\n\nThe resolver selected while compiling Lance . This blocks the FTS index benchmark before benchmark code runs. The relevant CI environment uses Rust and a freshly generated lockfile ().\n\nReproduction hint: from lance-bench , update the Lance revisions in to , remove/regenerate the benchmark lockfile as CI does, then run in that directory.\n\nLikely remediation is to pin/upgrade/patch the GooseFS dependency or disable the affected feature until an upstream release contains the missing import.\n\nDuplicate checks: searched open and closed Lance issues for , , , and ; no matching build-failure issue was found.
The lance-bench FTS index job fails while building Lance at commit .\n\nBenchmark run: https://github.com/lancedb/lance-bench/actions/runs/29415334699\nJob: \nFailed step: \n\nThe benchmark updates its Lance git dependencies to the tested SHA and runs:\n\n\n\nBuild output:\n\nCStringCStringgoosefs-sdk\n\nThe resolver selected while compiling Lance . This blocks the FTS index benchmark before benchmark code runs. The relevant CI environment uses Rust and a freshly generated lockfile ().\n\nReproduction hint: from lance-bench , update the Lance revisions in to , remove/regenerate the benchmark lockfile as CI does, then run in that directory.\n\nLikely remediation is to pin/upgrade/patch the GooseFS dependency or disable the affected feature until an upstream release contains the missing import.\n\nDuplicate checks: searched open and closed Lance issues for , , , and ; no matching build-failure issue was found.