sccache exits with error when passed .s files

After updating sccache to version 0.15.0, we get build errors for .s assembly files

make[1]: Entering directory 'foo'
[arm64-v8a] Compile        : libname <= file.s
sccache: encountered fatal error
sccache: error: failed to zip up compiler outputs
sccache: caused by: failed to zip up compiler outputs
sccache: caused by: failed to open file `"foo/build/androidndk_90_ARM64_compile_test//local/arm64-v8a/objs/libname/src/arm64/file.o.d"`
sccache: caused by: failed to open file `foo/build/androidndk_90_ARM64_compile_test//local/arm64-v8a/objs/libname/src/arm64/file.o.d`: No such file or directory (os error 2)
make[1]: *** [/opt/android/ndk/27.2.12479018/build/core/build-binary.mk:421: build/androidndk_90_ARM64_compile_test//local/arm64-v8a/objs/libname/src/arm64/file.o] Error 254

In our build system there is not way to avoid passing the .s to sccache. Is it possible to let sccache ignore them? Or perhaps just continue when it cannot find the .0.d files? Thanks.

Start by reproducing the failure with an Android NDK build that passes a .s assembly file through sccache, using the missing .o.d path shown in the report. Trace how sccache handles compiler outputs for this input; done means the assembly build no longer exits fatally when that dependency file is absent.