Better solution for #334 and #348. (FYI @cwfitzgerald @weiznich)
Open the zstd file, parse the nextest metadata, and if that does not work (I assume it is a format that not stable between breaking releases), follow what is passed in the arguments.
This eliminates the need in most cases to pass the flags passed to cargo llvm-cov nextest-archive to cargo llvm-cov nextest --archive-file again.
Better solution for #334 and #348. (FYI @cwfitzgerald @weiznich)
Open the zstd file, parse the nextest metadata, and if that does not work (I assume it is a format that not stable between breaking releases), follow what is passed in the arguments.
This eliminates the need in most cases to pass the flags passed to
cargo llvm-cov nextest-archive
tocargo llvm-cov nextest --archive-file
again.Before:
https://github.com/taiki-e/cargo-llvm-cov/blob/959921c2f9da5c01f6be595321998633c4bcf9d9/.github/workflows/ci.yml#L90-L91
https://github.com/taiki-e/cargo-llvm-cov/blob/959921c2f9da5c01f6be595321998633c4bcf9d9/.github/workflows/ci.yml#L99-L100
After:
https://github.com/taiki-e/cargo-llvm-cov/blob/3bc61cbd28d787a5bbfa3761d36c76cb7c061db9/.github/workflows/ci.yml#L90-L91
https://github.com/taiki-e/cargo-llvm-cov/blob/3bc61cbd28d787a5bbfa3761d36c76cb7c061db9/.github/workflows/ci.yml#L99-L100