rust/tests/run-make/libtest-padding/tests.rs

#![feature(test)]
extern crate test;

#[test]
fn short_test_name() {}

#[test]
fn this_is_a_really_long_test_name() {}

#[bench]
fn short_bench_name(b: &mut test::Bencher) {}

#[bench]
fn this_is_a_really_long_bench_name(b: &mut test::Bencher) {}
libtest: Add regression tests for padding As you can see the padding is wrong when running benches as tests. This will be fixed in the next commit. (Benches should only be padded when run as benches to make it easy to compare the benchmark numbers.) 2023-12-02 12:15:55 -06:00			`#![feature(test)]`
			`extern crate test;`

			`#[test]`
			`fn short_test_name() {}`

			`#[test]`
			`fn this_is_a_really_long_test_name() {}`

			`#[bench]`
Stabilize the runtime of libtest-padding The body of these benchmarks is close to empty but not literally empty. This was making the runtime of the benchmarks (which are compiled without optimizations!) flicker between 9 ns and 10 ns runtime, which changes the padding and breaks the test. Recent changes to the standard library have pushed the runtime closer to 10 ns when unoptimized, which is why we haven't seen such failures before in CI. Contributors can also induce such failures before this PR by running the run-make tests while the system is under heavy load. 2024-05-24 20:23:12 -05:00			`fn short_bench_name(b: &mut test::Bencher) {}`
libtest: Add regression tests for padding As you can see the padding is wrong when running benches as tests. This will be fixed in the next commit. (Benches should only be padded when run as benches to make it easy to compare the benchmark numbers.) 2023-12-02 12:15:55 -06:00
			`#[bench]`
Stabilize the runtime of libtest-padding The body of these benchmarks is close to empty but not literally empty. This was making the runtime of the benchmarks (which are compiled without optimizations!) flicker between 9 ns and 10 ns runtime, which changes the padding and breaks the test. Recent changes to the standard library have pushed the runtime closer to 10 ns when unoptimized, which is why we haven't seen such failures before in CI. Contributors can also induce such failures before this PR by running the run-make tests while the system is under heavy load. 2024-05-24 20:23:12 -05:00			`fn this_is_a_really_long_bench_name(b: &mut test::Bencher) {}`