alamb opened a new issue #345: URL: https://github.com/apache/arrow-rs/issues/345
**Describe the bug** Ever since we have enabled MIRI checks on CI in https://github.com/apache/arrow-rs/pull/323 (epic thanks to @roee88 ) we have started to see intermittent failures of the check **To Reproduce** Run CI checks on a PR Here are some example failures https://github.com/apache/arrow-rs/runs/2656075800 https://github.com/apache/arrow-rs/runs/2658362992 An excerpt from https://github.com/alamb/arrow-rs/runs/2659329294?check_suite_focus=true ``` test array::array_primitive::tests::test_time32_millisecond_array_from_vec ... ok test array::array_primitive::tests::test_time32second_fmt_debug ... ok thread 'main' panicked at 'invalid time', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/chrono-0.4.19/src/naive/time.rs:412:67 stack backtrace: 0: 0xa9fa3ef - std::backtrace_rs::backtrace::miri::trace_unsynchronized::<&mut [closure@std::sys_common::backtrace::_print_fmt::{closure#1}]> at /usr/share/rust/.rustup/toolchains/nightly-2021-03-24-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/../../backtrace/src/backtrace/miri.rs:65:18 1: 0xaa266e9 - std::backtrace_rs::backtrace::miri::trace::<&mut [closure@std::sys_common::backtrace::_print_fmt::{closure#1}]> at /usr/share/rust/.rustup/toolchains/nightly-2021-03-24-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/../../backtrace/src/backtrace/miri.rs:51:14 2: 0xa9dc49b - std::backtrace_rs::backtrace::trace_unsynchronized::<[closure@std::sys_common::backtrace::_print_fmt::{closure#1}]> at /usr/share/rust/.rustup/toolchains/nightly-2021-03-24-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5 3: 0x298f21f - std::sys_common::backtrace::_print_fmt at /usr/share/rust/.rustup/toolchains/nightly-2021-03-24-x86_64-unknown-linux-g ``` **Expected behavior** A clear and concise description of what you expected to happen. **Additional context** Add any other context about the problem here. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
