Problem matchers: Matches of test failures by WillAbides · Pull Request #422 · actions/setup-go
Description:
Currently test failures do not get annotated because the problem matcher requires that a column number be present, but go's test output does not include a column for test failures.
An example line that gets missed by the current matcher is:
/path/to/main_test.go:13: expected true but got false
The updated matcher makes the column number optional and matches the line above.
Check list:
- Mark if documentation changes are required.
- Mark if tests were added or updated to cover the changes.