-
Notifications
You must be signed in to change notification settings - Fork 3k
Description
Is your feature request related to a problem? Please describe.
I am defining problem matchers for Erlang (see additional context) and noticed that Eunit prints the file name where the error occurred but Common Test does not. Having the file name enables GitHub to pinpoint errors directly on the PR as a line comment.
Describe the solution you'd like
I am thinking of adding the file name to the formatting for these clauses: https://github.com/erlang/otp/blob/master/lib/common_test/src/ct_framework.erl#L1013-L1034
Describe alternatives you've considered
A CT hook printing raw matcher info.
Additional context
erlef/setup-beam#390
Problem matchers add annotations to CI runs (on the summary page and on individual job pages) and to PRs (on the line/number and if available column the error/warning happened). In short they allow knowing what error occurred without having to go through the CI logs.
I started one that does erlc, dialyzer, ct, eunit. Tested it on my projects for now but plan is to have them for RabbitMQ as well.