You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would expect to be able to set the log level for the logger. Currently, because our unit tests are so quick, they are generating quite a lot of Haneke warnings because of the state of the cache. These warnings do not affect the tests and are not a real problem. The warnings, however, are printing at the same time the test results are printing, which means that our test results parser cannot parse the test results and so we get a random number of tests that the parser thinks executed every build.
In any case, I think log level should always be configurable.
The text was updated successfully, but these errors were encountered:
I would expect to be able to set the log level for the logger. Currently, because our unit tests are so quick, they are generating quite a lot of Haneke warnings because of the state of the cache. These warnings do not affect the tests and are not a real problem. The warnings, however, are printing at the same time the test results are printing, which means that our test results parser cannot parse the test results and so we get a random number of tests that the parser thinks executed every build.
In any case, I think log level should always be configurable.
The text was updated successfully, but these errors were encountered: