mirror of
https://github.com/rust-lang/rust-analyzer
synced 2024-12-28 05:53:45 +00:00
Auto merge of #15267 - lowr:patch/exceeding-exec-limit-is-slow, r=lnicola
Mark test for MIR execution limit as slow test The test for MIR execution limit accounts for ~2/3 of total execution time of non-slow hir-ty tests. It significantly slows down edit-and-run-test type of workflow. Can we mark it as a slow test?
This commit is contained in:
commit
642420fb60
1 changed files with 5 additions and 0 deletions
|
@ -1,6 +1,7 @@
|
|||
use base_db::{fixture::WithFixture, FileId};
|
||||
use chalk_ir::Substitution;
|
||||
use hir_def::db::DefDatabase;
|
||||
use test_utils::skip_slow_tests;
|
||||
|
||||
use crate::{
|
||||
consteval::try_const_usize, db::HirDatabase, mir::pad16, test_db::TestDB, Const, ConstScalar,
|
||||
|
@ -2458,6 +2459,10 @@ fn const_trait_assoc() {
|
|||
|
||||
#[test]
|
||||
fn exec_limits() {
|
||||
if skip_slow_tests() {
|
||||
return;
|
||||
}
|
||||
|
||||
check_fail(
|
||||
r#"
|
||||
const GOAL: usize = loop {};
|
||||
|
|
Loading…
Reference in a new issue