turso
turso copied to clipboard
test_combined_modifiers fails when ran from tarpaulin
failures:
---- vdbe::datetime::tests::test_combined_modifiers stdout ----
thread 'vdbe::datetime::tests::test_combined_modifiers' panicked at core/vdbe/datetime.rs:1534:9:
Expected: 2025-01-12 01:37:09.591333350, Actual: 2025-01-12 01:37:09.605
stack backtrace:
0: rust_begin_unwind
at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/panicking.rs:665:5
1: core::panicking::panic_fmt
at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/core/src/panicking.rs:74:14
2: limbo_core::vdbe::datetime::tests::test_combined_modifiers
at ./vdbe/datetime.rs:1534:9
3: limbo_core::vdbe::datetime::tests::test_combined_modifiers::{{closure}}
at ./vdbe/datetime.rs:1513:33
4: core::ops::function::FnOnce::call_once
at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/core/src/ops/function.rs:250:5
5: core::ops::function::FnOnce::call_once
at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
failures:
vdbe::datetime::tests::test_combined_modifiers
test result: FAILED. 223 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.63s
on ubuntu 20 using gnu libc with cargo 1.83.0 (5ffbef321 2024-10-29)
the faliure apears to only happen when testing with tarpaulin and messing with the code a bit It would pass if the tolerance is increased. I am not sure what is happening but I am willing to run whatever steps to debug this you need me to do.