-
Notifications
You must be signed in to change notification settings - Fork 279
Closed
Description
I'm getting the following test failures when running cargo test --release:
failures:
asm::x86::mc::test::test_rav1e_prep_8tap_regular_bd_8_avx2
asm::x86::mc::test::test_rav1e_prep_8tap_regular_bd_8_ssse3
asm::x86::mc::test::test_rav1e_prep_8tap_regular_sharp_bd_8_avx2
asm::x86::mc::test::test_rav1e_prep_8tap_regular_sharp_bd_8_ssse3
asm::x86::mc::test::test_rav1e_prep_8tap_regular_smooth_bd_8_avx2
asm::x86::mc::test::test_rav1e_prep_8tap_regular_smooth_bd_8_ssse3
asm::x86::mc::test::test_rav1e_prep_8tap_sharp_bd_8_avx2
asm::x86::mc::test::test_rav1e_prep_8tap_sharp_bd_8_ssse3
asm::x86::mc::test::test_rav1e_prep_8tap_sharp_regular_bd_8_avx2
asm::x86::mc::test::test_rav1e_prep_8tap_sharp_regular_bd_8_ssse3
asm::x86::mc::test::test_rav1e_prep_8tap_sharp_smooth_bd_8_avx2
asm::x86::mc::test::test_rav1e_prep_8tap_sharp_smooth_bd_8_ssse3
asm::x86::mc::test::test_rav1e_prep_8tap_smooth_bd_8_avx2
asm::x86::mc::test::test_rav1e_prep_8tap_smooth_bd_8_ssse3
asm::x86::mc::test::test_rav1e_prep_8tap_smooth_regular_bd_8_avx2
asm::x86::mc::test::test_rav1e_prep_8tap_smooth_regular_bd_8_ssse3
asm::x86::mc::test::test_rav1e_prep_8tap_smooth_sharp_bd_8_avx2
asm::x86::mc::test::test_rav1e_prep_8tap_smooth_sharp_bd_8_ssse3
asm::x86::mc::test::test_rav1e_prep_bilin_bd_8_avx2
asm::x86::mc::test::test_rav1e_prep_bilin_bd_8_ssse3
test result: FAILED. 352 passed; 20 failed; 0 ignored; 0 measured; 0 filtered out
This happens only when using the --release option. When running cargo test without --release, the tests runs fine.
Exporting/setting RUSTFLAGS='-C target-cpu=native' does not modify the result.
The last good commit that works for me is 4dfda58. A git bisect shows that this is caused by commit 8fa818b.
System Information:
- OS: Arch Linux x86_64
- rav1e: git master
- rust: 1.42.0 (also happened with 1.41.0)
- NASM: 2.14.02