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.)
21 lines
481 B
Text
21 lines
481 B
Text
--
|
|
|
|
def run1 (i : Nat) (n : Nat) (xs : List Nat) : Nat :=
|
|
n.repeat (fun r =>
|
|
dbg_trace ">> [{i}] {r}";
|
|
xs.foldl (fun a b => a + b) r)
|
|
0
|
|
|
|
def tst (n : Nat) : IO UInt32 :=
|
|
let ys := (List.replicate n 1);
|
|
let ts : List (Task Nat) := (List.iota 10).map (fun i => Task.spawn fun _ => run1 (i+1) n ys);
|
|
let ns : List Nat := ts.map Task.get;
|
|
IO.println (">> " ++ toString ns) *>
|
|
pure 0
|
|
|
|
/--
|
|
info: >> [100, 100, 100, 100, 100, 100, 100, 100, 100, 100]
|
|
0
|
|
-/
|
|
#guard_msgs in
|
|
#eval tst 10
|