You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The output from fizzy-spectests is quite large as it reports status of every executed test case. I expect users are mostly interested in failures. Some ideas how to improve it.
Skip PASSED reports by default. Easy to implement.
Repeat status of each file in the end. This will allow at least quickly find the file with failures and repeat the run on the subset of files.
Use "dot notation" per file. Each test result is represented by a single character. E.g.
binary.wast: ......F.....s.....
Line 98: assert_return FAILED Incorrect returned value. Expected: 9219994337134247936 (0x7ff4000000000000) Actual: 0 (0x0)
Line 99: assert_return SKIPPED Unsupported feature: Floating point instruction.
The text was updated successfully, but these errors were encountered:
The output from
fizzy-spectests
is quite large as it reports status of every executed test case. I expect users are mostly interested in failures. Some ideas how to improve it.PASSED
reports by default. Easy to implement.The text was updated successfully, but these errors were encountered: