fix: reduce log level for matching to debug

[mefellows]

The additional noise in the logs at info level is not needed and interferes with standard out (e.g. test output), and is more appropriate for debug level.

[YOU54F]

some other places noted from pact-foundation/pact-js#1114

it’s here

https://github.com/pact-foundation/pact-core-mock-server/blob/febf7974b648aeeefb6af3d69dd988051886243e/pact_mock_server/src/hyper_server.rs#L275

here

https://github.com/pact-foundation/pact-core-mock-server/blob/febf7974b648aeeefb6af3d69dd988051886243e/pact_mock_server/src/hyper_server.rs#L185

The debug values captured for the incoming and outgoing requests are useful and could be captured for sending in case of failure.

and here

pact-reference/rust/pact_matching/src/lib.rs

Line 1665 in efc54d2

info!("comparing to expected {}", expected);

There are other instances of info! statements

• Pact-ref - https://github.com/search?q=repo%3Apact-foundation%2Fpact-reference+info%21&type=code
• pact-plugins - https://github.com/search?q=repo%3Apact-foundation%2Fpact-plugins%20info!&type=code
• pact-core-mock-server - https://github.com/search?q=repo%3Apact-foundation%2Fpact-core-mock-server%20info!&type=code

I think lib authors can suppress log output by piping to a buffer (or file) and reading from there if necessary (fetch_log_buffer_as_json)

[YOU54F]

Could capture additional info statements found here, in this PR if you wanted to, although they cross crates

https://github.com/search?q=repo%3Apact-foundation%2Fpact-reference+info%21&type=code

[mefellows]

Could capture additional info statements found here, in this PR if you wanted to, although they cross crates

https://github.com/search?q=repo%3Apact-foundation%2Fpact-reference+info%21&type=code

Good shout, they look like decent targets to switch to debug! as well.

Pact JS was one of the earlier adopters and we were toying with various output options. Resolving pact-foundation/pact-js-core#428 will go some way to making this less relevant in the JS use case.

[rholshausen]

The other option is if you don't want to see INFO level logs, then don't set the logging to INFO. Set it to WARN.

[YOU54F]

this is pretty much ready to go pact-foundation/pact-js-core#428

however it is a pain to test as when the ffi lib is started and you set a log sink, you can't change it, so it logs to stdout/buffer or file. it's the cause of noise in the pact-go and js logs about the ffi already being initialised and a log level is already set, so cannot set a new level

Not sure if we can setup multiple?

Also it would actually be nice if we could control the log level per test, but that currently isn't possibly. I would find maybe being able to log per test more useful that a massive log dump in a file.

makes the haystack smaller if something does go wrong, as no-one wants to go sifting through logs unless there is a really good key that you can reliably search on.