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.)
29 lines
531 B
Text
29 lines
531 B
Text
|
|
|
|
def g (x : Nat) : Nat :=
|
|
dbgTrace ("g: " ++ toString x) $ fun _ =>
|
|
x + 1
|
|
|
|
def f1 (x : Nat) : Nat :=
|
|
dbgSleep 1000 $ fun _ =>
|
|
dbgTrace ("f1: " ++ toString x) $ fun _ =>
|
|
g (x + 1)
|
|
|
|
def f2 (x : Nat) : Nat :=
|
|
dbgSleep 100 $ fun _ =>
|
|
dbgTrace ("f2: " ++ toString x) $ fun _ =>
|
|
g x
|
|
|
|
def tst (n : Nat) : IO UInt32 :=
|
|
let t1 := Task.spawn fun _ => f1 n;
|
|
let t2 := Task.spawn fun _ => f2 n;
|
|
dbgSleep 1000 $ fun _ =>
|
|
IO.println (toString t1.get ++ " " ++ toString t2.get) *>
|
|
pure 0
|
|
|
|
/--
|
|
info: 12 11
|
|
0
|
|
-/
|
|
#guard_msgs in
|
|
#eval tst 10
|