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.)
32 lines
515 B
Text
32 lines
515 B
Text
import Lean.CoreM
|
|
import Lean.MonadEnv
|
|
|
|
open Lean
|
|
open Lean.Core
|
|
|
|
def f : CoreM Nat := do
|
|
let env ← getEnv;
|
|
let cinfo ← getConstInfo `Nat.add;
|
|
trace[Elab] "trace message";
|
|
IO.println $ toString cinfo.type;
|
|
IO.println "testing...";
|
|
pure 10;
|
|
|
|
/--
|
|
info: ([mdata borrowed:1 Nat]) -> ([mdata borrowed:1 Nat]) -> Nat
|
|
testing...
|
|
10
|
|
-/
|
|
#guard_msgs in
|
|
#eval f
|
|
|
|
set_option trace.Elab true
|
|
|
|
/--
|
|
info: ([mdata borrowed:1 Nat]) -> ([mdata borrowed:1 Nat]) -> Nat
|
|
testing...
|
|
[Elab] trace message
|
|
10
|
|
-/
|
|
#guard_msgs in
|
|
#eval f
|