log_level in testing config

[dwilding]

I'm reading https://canonical.com/juju/docs/ops/latest/howto/write-integration-tests-for-a-charm/#log-to-a-file, which has an example of pyproject.toml:

# Retain INFO logs in the "Captured log call" section when run interactively.
# Otherwise, that section will have DEBUG logs (coming from log_file_level).
log_level = "INFO"

Based on my experience of Jubilant, I don't think log_level = "INFO" has any effect on the Jubilant output during an integration test. But maybe there's a behaviour difference with the latest version of Jubilant?

[github-actions]

The doc-validation agent did not produce a result. Check the workflow logs.

[github-actions]

The doc-validation agent did not produce a result. Check the workflow logs.

[github-actions]

The doc-validation agent opened a draft PR: #45

Review the PR, then mark it ready for review to run CI. Inspect the CI runs to determine whether the doc was validated or refuted.

[github-actions]

The doc-validation agent opened a draft PR: #45

Review the PR, then mark it ready for review to run CI. Inspect the CI runs to determine whether the doc was validated or refuted.