3a457e6ad6
Many of our tests in `tests/lean/run/` produce output from `#eval` (or `#check`) statements, that is then ignored. This PR tries to capture all the useful output using `#guard_msgs`. I've only done a cursory check that the output is still sane --- there is a chance that some "unchecked" tests have already accumulated regressions and this just cements them! In the other direction, I did identify two rotten tests: * a minor one in `setStructInstNotation.lean`, where a comment says `Set Nat`, but `#check` actually prints `?_`. Weird? * `CompilerProbe.lean` is generating empty output, apparently indicating that something is broken, but I don't know the signficance of this file. In any case, I'll ask about these elsewhere. (This started by noticing that a recent `grind` test file had an untested `trace_state`, and then got carried away.)
50 lines
443 B
Text
50 lines
443 B
Text
def test2 : IO Unit := do
|
|
let mut i := 0
|
|
repeat
|
|
println! "{i}"
|
|
i := i + 1
|
|
until i >= 10
|
|
println! "test2 done {i}"
|
|
|
|
/--
|
|
info: 0
|
|
1
|
|
2
|
|
3
|
|
4
|
|
5
|
|
6
|
|
7
|
|
8
|
|
9
|
|
test2 done 10
|
|
-/
|
|
#guard_msgs in
|
|
#eval test2
|
|
|
|
def test3 : IO Unit := do
|
|
let mut i := 0
|
|
repeat
|
|
println! "{i}"
|
|
if i > 10 && i % 3 == 0 then break
|
|
i := i + 1
|
|
println! "test3 done {i}"
|
|
|
|
/--
|
|
info: 0
|
|
1
|
|
2
|
|
3
|
|
4
|
|
5
|
|
6
|
|
7
|
|
8
|
|
9
|
|
10
|
|
11
|
|
12
|
|
test3 done 12
|
|
-/
|
|
#guard_msgs in
|
|
#eval test3
|