Closed kentfredric closed 4 years ago
Humm, that's odd, the test runs fine on the CI on the latest commits .
Ah wait, it probably fails because the test data is excluded from the release package to reduce the package size. Is there a need to have that working on the packaged library?
Ideally, if a given test can't be imagined to work on the published crate, that test should be excluded from the published crate.
This could be achieved by moving the handful of tests that require the test data to their own test, then you can exclude both those tests and the test data.
I've excluded the tests directory from the published crate. Does that fix it?
That should fix it. Ideally, you should split the tests into ones that can be expected to work when published, and ones that aren't, and then exclude only the ones that aren't.
That way you have at least some tests.
There are still some tests, it's just the ones in test.rs that are excluded.
Full output with
``` --- roundtrip_lvl_0 stdout ---- thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/libcore/result.rs:1165:5 stack backtrace: 0: 0x55c5d8263be4 - backtrace::backtrace::libunwind::trace::h93069dd45e563114 at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88 1: 0x55c5d8263be4 - backtrace::backtrace::trace_unsynchronized::ha81d63fb01c61f43 at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66 2: 0x55c5d8263be4 - std::sys_common::backtrace::_print_fmt::h5800670bd4856d97 at src/libstd/sys_common/backtrace.rs:77 3: 0x55c5d8263be4 -RUST_BACKTRACE=full