You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am encountering an issue where the test test_non_matching_dates_add fails with a SIGABRT signal. The test is supposed to panic with the message "Dates must match." when adding SimpleCashflow instances with non-matching dates. However, instead of the expected panic, I am getting a SIGABRT signal, which indicates an abort signal in the process.
RUST_BACKTRACE=1 cargo test test_non_matching_dates_add -- --nocapture
running 1 test
thread 'cashflows::cashflow::test_cashflows::test_non_matching_dates_add' panicked at src/cashflows/cashflow.rs:72:9:
assertion `left == right` failed: Dates must match.
left: 2024-06-25 4:14:44.398515 +00:00:00
right: 2024-06-26 4:14:44.398515 +00:00:00
stack backtrace:
libunwind: stepWithCompactEncoding - invalid compact unwind encoding
error: test failed, to rerun pass `--lib`
Caused by:
process didn't exit successfully: `RustQuant-c0a882e3717c1824 test_non_matching_dates_add --nocapture` (signal: 6, SIGABRT: process abort signal)
Original test
// Test for non-matching dates during addition (should panic).#[test]#[should_panic(expected = "Dates must match.")]fntest_non_matching_dates_add(){let date1 = OffsetDateTime::now_utc();let date2 = date1 + Duration::days(1);let cf1 = SimpleCashflow::new(100.0, date1);let cf2 = SimpleCashflow::new(50.0, date2);let _ = cf1 + cf2;}
I am encountering an issue where the test test_non_matching_dates_add fails with a SIGABRT signal. The test is supposed to panic with the message "Dates must match." when adding SimpleCashflow instances with non-matching dates. However, instead of the expected panic, I am getting a SIGABRT signal, which indicates an abort signal in the process.
RUST_BACKTRACE=1 cargo test test_non_matching_dates_add -- --nocapture
Original test
I added this test that failed as well.
The text was updated successfully, but these errors were encountered: