Ref T5568. As discussed in IRC. This is very rough and not widely useable, but represents a solid first step.
- Group Reviewers
- Maniphest Tasks
- T5568: Support `.arcunit`, similar to `.arclint`
- rARC59698df856dd: Rough version of configuration driven unit test engine
Ran arc unit with a bunch of flags.
|7 ↗||(On Diff #32820)|
Maybe only true if at least one configured engine supports --everything.
|69–72 ↗||(On Diff #32820)|
Could we just do the type check first, and simplify this a bit?
|120 ↗||(On Diff #32820)|
I think we should move away from support for this (and "postponed" linters) -- these models never really made sense, and Harbormaster is on the horizon now. Fine to maintain support if it's "free", but feel free to just drop it if it's non-free, too.
|125 ↗||(On Diff #32820)|
At some point, maybe we should emit a warning here if an engine doesn't support --everything, to reduce surprise when --everything does not really mean --everything.
|128 ↗||(On Diff #32820)|
Consider type checking the results, similar to D13486, to place blame on bad engines more clearly.
|150 ↗||(On Diff #32820)|
(Is this essentially identical to something in the Lint engine?)