Harden runner log showing warnings instead of normal logs

I noticed here that normal logs are being shown as warnings: https://github.com/miguelnietoa/stellar_sdk/runs/7881603461?check_suite_focus=true#step:20:4

This does not happen typically and I cannot find it for other runs. Here is a typical run: https://github.com/harden-runner-canary/dassana/runs/7880455490?check_suite_focus=true#step:12:4

@miguelnietoa thanks for using harden-runner! Do you have a configuration in your workflow that treats some kind of logs as warnings? I am trying to investigate why normal harden-runner logs are showing as warnings for your workflow run. If not, I will investigate further. Thanks!

[miguelnietoa]

Hi @miguelnietoa,

I forgot to update you on the original issue. The reason the harden-runner logs were showing as warnings is because erlef/setup-beam (erlef/setup-elixir has been renamed I believe to erlef/setup-beam) GitHub Action adds problem_matchers. These are regular expressions and they were matching the timestamp added to harden-runner logs.

@h0x0er had also created an issue to discuss it.

There is nothing much we can do about this. If you do not need the warnings from erlef/setup-beam Action, you can set disable_problem_matchers to true. That will solve the problem.

Please let me know if you have any follow up questions…

I have no further questions and leave it to your consideration whether this issue should be closed as it is outside the scope of harden-runner action.

Thanks for the research on this and bringing me up to speed! @varunsh-coder @h0x0er 😄 💯

[varunsh-coder]

Hi @miguelnietoa,

I forgot to update you on the original issue. The reason the harden-runner logs were showing as warnings is because erlef/setup-beam (erlef/setup-elixir has been renamed I believe to erlef/setup-beam) GitHub Action adds problem_matchers. These are regular expressions and they were matching the timestamp added to harden-runner logs.

@h0x0er had also created an issue to discuss it.

There is nothing much we can do about this. If you do not need the warnings from erlef/setup-beam Action, you can set disable_problem_matchers to true. That will solve the problem.

Please let me know if you have any follow up questions…