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.)
40 lines
945 B
Text
40 lines
945 B
Text
import Lean.Util.SCC
|
|
|
|
open Lean.SCC
|
|
|
|
def checkSCC (expected : List (List Nat)) (vertices : List Nat) (successorsOf : Nat → List Nat) : IO Unit := do
|
|
let r := scc vertices successorsOf
|
|
IO.println r
|
|
unless expected == r do
|
|
throw $ IO.userError ("expected result " ++ toString expected)
|
|
|
|
/-- info: [[2], [1, 3], [4]] -/
|
|
#guard_msgs in
|
|
#eval checkSCC [[2], [1, 3], [4]] [1, 2, 3, 4] fun x => match x with
|
|
| 1 => [2, 3]
|
|
| 3 => [1]
|
|
| 4 => [1, 2]
|
|
| _ => []
|
|
|
|
/-- info: [[1], [2], [3], [4]] -/
|
|
#guard_msgs in
|
|
#eval checkSCC [[1], [2], [3], [4]] [1, 2, 3, 4] fun x => match x with
|
|
| _ => []
|
|
|
|
/-- info: [[1, 2, 3, 4]] -/
|
|
#guard_msgs in
|
|
#eval checkSCC [[1, 2, 3, 4]] [1, 2, 3, 4] fun x => match x with
|
|
| 1 => [2]
|
|
| 2 => [3]
|
|
| 3 => [4]
|
|
| 4 => [1]
|
|
| _ => []
|
|
|
|
/-- info: [[1, 2, 4], [3]] -/
|
|
#guard_msgs in
|
|
#eval checkSCC [[1, 2, 4], [3]] [1, 2, 3, 4] fun x => match x with
|
|
| 1 => [2]
|
|
| 2 => [4]
|
|
| 3 => [4]
|
|
| 4 => [1]
|
|
| _ => []
|