mirror of
https://github.com/rust-lang/rust.git
synced 2025-12-01 00:28:02 +00:00
e106d63516
When there is a panic in an extensive test, tracing down where it came from can be difficult since no information is provides (messeges are e.g. "attempted to subtract with overflow"). Resolve this by calling the functions within `panic::catch_unwind`, printing the input, and continuing.
39 lines
1.1 KiB
Rust
39 lines
1.1 KiB
Rust
//! Test cases that have both an input and an output, so do not require a basis.
|
|
|
|
use libm_test::gen::case_list;
|
|
use libm_test::{CheckBasis, CheckCtx, CheckOutput, GeneratorKind, MathOp, TupleCall};
|
|
|
|
const BASIS: CheckBasis = CheckBasis::None;
|
|
|
|
fn standalone_runner<Op: MathOp>(
|
|
ctx: &CheckCtx,
|
|
cases: impl Iterator<Item = (Op::RustArgs, Op::RustRet)>,
|
|
) {
|
|
for (input, expected) in cases {
|
|
let crate_res = input.call_intercept_panics(Op::ROUTINE);
|
|
crate_res.validate(expected, input, ctx).unwrap();
|
|
}
|
|
}
|
|
|
|
macro_rules! mp_tests {
|
|
(
|
|
fn_name: $fn_name:ident,
|
|
attrs: [$($attr:meta),*],
|
|
) => {
|
|
paste::paste! {
|
|
#[test]
|
|
$(#[$attr])*
|
|
fn [< standalone_ $fn_name >]() {
|
|
type Op = libm_test::op::$fn_name::Routine;
|
|
let ctx = CheckCtx::new(Op::IDENTIFIER, BASIS, GeneratorKind::List);
|
|
let cases = case_list::get_test_cases_standalone::<Op>(&ctx);
|
|
standalone_runner::<Op>(&ctx, cases);
|
|
}
|
|
}
|
|
};
|
|
}
|
|
|
|
libm_macros::for_each_function! {
|
|
callback: mp_tests,
|
|
}
|