Closed edwin0cheng closed 4 years ago
:weary: that means I probably did something wrong with the Binders refactoring that wasn't caught by the tests, and I forgot to run analysis-stats...
I just knew that in the log of my ra-stats projects 😭
cargo run --release -p rust-analyzer -- analysis-stats .
Does it make sense to run this in CI?
@JoshMcguigan good question. The problem is that will double our CI times...
I guess we can run this during our nightly release?
Added analysis-stats to CI. I guess I should probably bite the bullet and write the code that promotes release artifacts from nightly to stable...
In 2603a9e628d304c8cb8fd08979e2f9c9afeac69e by running:
Stack track
``` Finished release [optimized] target(s) in 0.25s Running `target\release\rust-analyzer.exe analysis-stats .` thread 'main' panicked at 'index out of bounds: the len is 0 but the index is 0', C:\Users\Edwin\.cargo\git\checkouts\chalk-7b02fa8caa2cec94\039fc90\chalk-ir\src\lib.rs:1613:10 stack backtrace: 0: backtrace::backtrace::trace_unsynchronized at C:\Users\VssAdministrator\.cargo\registry\src\github.com-1ecc6299db9ec823\backtrace-0.3.40\src\backtrace\mod.rs:66 1: std::sys_common::backtrace::_print_fmt at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\/src\libstd\sys_common\backtrace.rs:77 2: std::sys_common::backtrace::_print::{{impl}}::fmt at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\/src\libstd\sys_common\backtrace.rs:59 3: core::fmt::write at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\/src\libcore\fmt\mod.rs:1052 4: std::io::Write::write_fmtcc @flodiebold