Stack traces from "coverage" check are missing line numbers #170
Description
Unclear if it also affects other things but only the standard library lines here appear to have line numbers. Are we executing tests for coverage without generating debug information or something to that nature?
Example from https://github.com/microsoft/oxidizer/actions/runs/20592503815/job/59140206566?pr=169:
thread 'system_time_ext::tests::display_ok' (2020) panicked at C:\Users\runneradmin\.cargo\registry\src\index.crates.io-1949cf8c6b5b557f\jiff-0.2.16\src\timestamp.rs:2833:41:
duration too big (negative)
stack backtrace:
0: std::panicking::panic_handler
at /rustc/806c2a35dcc1db7867864fea0a7a65554a5238b7/library\std\src\panicking.rs:689
1: core::panicking::panic_fmt
at /rustc/806c2a35dcc1db7867864fea0a7a65554a5238b7/library\core\src\panicking.rs:80
2: core::panicking::panic_display
at /rustc/806c2a35dcc1db7867864fea0a7a65554a5238b7/library\core\src\panicking.rs:259
3: core::option::expect_failed
at /rustc/806c2a35dcc1db7867864fea0a7a65554a5238b7/library\core\src\option.rs:2208
4: <core::option::Option<std::time::SystemTime>>::expect
5: <std::time::SystemTime as core::convert::From<jiff::timestamp::Timestamp>>::from
6: core::sync::atomic::fence
7: tick::system_time_ext::tests::display_ok::{closure#0}
8: <tick::system_time_ext::tests::display_ok::{closure#0} as core::ops::function::FnOnce<()>>::call_once
9: core::ops::function::FnOnce::call_once
at C:\a\rust\rust\library\core\src\ops\function.rs:250
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.