Store integreat-cms.log as an artifact after test run in CI

[seluianova]

Short description

Sometimes we encounter test failures in CI that are not reproduced locally.
We can see some pieces of the log in the test output, but sometimes it's not enough to localize the problem.
To make the analysis a bit easier, I suggest attaching full integreat-cms.log as a job artifact.
It will only be available when there are test failures:

Proposed changes

• add step "Copy CMS log" to the test job in CI

Side effects

No?

I think it would also be useful to set the logging level to DEBUG, but I couldn't find how to do that :(
I thought this was supposed to be managed by

#: Use debug logging on CircleCI
LOG_LEVEL = "DEBUG"

in circleci_settings.py, but no.
The actual log level in CI is currently INFO.
log example
Maybe someone has some ideas on how to change this?

Resolved issues

Fixes: #2256

---

Pull Request Review Guidelines

[codeclimate]

Code Climate has analyzed commit d540ee3 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (50% is the threshold).

This pull request will bring the total coverage in the repository to 81.5% (-0.2% change).

View more on Code Climate.

[david-venhoff]

Thanks, LGTM. I was a bit surprised that the circleci checks for this pr did not generate the artifact (Or I did not find it). Is that to be expected?

[timobrembeck]

Thanks! 👍

think it would also be useful to set the logging level to DEBUG, but I couldn't find how to do that :(
I thought this was supposed to be managed by

#: Use debug logging on CircleCI
LOG_LEVEL = "DEBUG"

in circleci_settings.py, but no.
The actual log level in CI is currently INFO.
log example
Maybe someone has some ideas on how to change this?

@seluianova Ah, I got it: The LOG_LEVEL setting is just an intermediary variable and not used by Django. The real logging setting is here:

integreat-cms/integreat_cms/core/settings.py

Line 580 in 781f29a

LOGGING: Final[dict[str, Any]] = {

So what happens is this:

• from .settings import * sets the LOGGING setting based on the default value of LOG_LEVEL (which is INFO in this case)
• LOG_LEVEL = "DEBUG" does not change the LOGGING setting anymore and thus has no effect

I was a bit surprised that the circleci checks for this pr did not generate the artifact (Or I did not find it). Is that to be expected?

@david-venhoff I think that's expected since the tests did not fail and the artifact is only stored when the tests fail.
I mean we could also think about storing the log in any case, since a few lines of text are only a few kb, so storing it will not cost a lot of credits.

[seluianova]

@timobrembeck thank you!
Added logging configuration for integreat_cms and integreat_cms.core.management.commands.
I assume this should be sufficient for analyzing test failures.