How to configure debug.log logging level

[marioaag]

I'm trying to configure the messages that are logged to the debug.log file of each one of the tests with out total success, I started using the configuration option job.output.loglevel and that helped with the messages from the progress logger but still getting the debug messages from the rest of the python modules used. I try configuring by my self the root logger logging and that help with the modules called by my test but still seeing some debug messages, that looks like are coming from modules used by Avocado.

Execution code:

from avocado.core.job import Job
from avocado.core.suite import TestSuite
from avocado.core.nrunner.runnable import Runnable

JOB_CONFIG = {'core.show': {'app', 'avocado.test.progress'}, 'job.output.loglevel': 'INFO'}

suite = TestSuite(name="suite", tests=[Runnable("avocado-instrumented", "basic.py:PassTest.test", config=JOB_CONFIG)], config=JOB_CONFIG)
with Job(JOB_CONFIG, test_suites=[suite]) as job:
    result = job.run()

Test code:

import logging
from avocado import Test

class PassTest(Test):
    """
    Example test that passes.
    """
    def test(self):
        """
        A test simply doesn't have to fail in order to pass
        """
        progress_log = logging.getLogger("avocado.test.progress")
        progress_log.info("Test Info")
        progress_log.warning("Test Warning")
        progress_log.debug("Test Debug")
        self.log.info("Test log info")

Logs:

mario@MacBookPro Desktop % python3 -m advance
JOB ID     : c0e9f63a961bdcdce57999db38fc5fe4e5282f8b
JOB LOG    : /Users/mario/avocado/job-results/job-2025-11-21T15.08-c0e9f63/job.log
 (suite-1/1) basic.py:PassTest.test: STARTED
avocado.test.progress: suite-1-basic.py:PassTest.test: 2025-11-21 15:09:00,555 avocado.test.progress basic            L0013 INFO | Test Info
avocado.test.progress: suite-1-basic.py:PassTest.test: 2025-11-21 15:09:00,556 avocado.test.progress basic            L0014 WARNI| Test Warning
 (suite-1/1) basic.py:PassTest.test: PASS (0.01 s)
RESULTS    : PASS 1 | ERROR 0 | FAIL 0 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 0
JOB TIME   : 1.38 s

debug.log:

[stdlog] 2025-11-21 15:09:00,550 avocado.test test             L0312 INFO | INIT 1-basic.py:PassTest.test
[stdlog] 2025-11-21 15:09:00,552 avocado.utils.deprecation deprecation      L0038 INFO | The data_structures utility is deprecated. It has been moved to the AAutils project and will be removed after the next LTS release. For more information, please see the following link: https://github.com/avocado-framework/aautils
[stdlog] 2025-11-21 15:09:00,552 avocado.utils.deprecation deprecation      L0038 INFO | The path utility is deprecated. It has been moved to the AAutils project and will be removed after the next LTS release. For more information, please see the following link: https://github.com/avocado-framework/aautils
[stdlog] 2025-11-21 15:09:00,554 asyncio selector_events  L0054 DEBUG| Using selector: KqueueSelector     <<-- Unexpected
[stdlog] 2025-11-21 15:09:00,555 avocado.test test             L0526 INFO | START 1-basic.py:PassTest.test
[stdlog] 2025-11-21 15:09:00,555 avocado.test.progress basic            L0013 INFO | Test Info
[stdlog] 2025-11-21 15:09:00,556 avocado.test.progress basic            L0014 WARNI| Test Warning
[stdlog] 2025-11-21 15:09:00,556 avocado.test basic            L0016 INFO | Test log info
[stdlog] 2025-11-21 15:09:00,557 asyncio selector_events  L0054 DEBUG| Using selector: KqueueSelector     <<--- Unexpected
[stdlog] 2025-11-21 15:09:00,557 avocado.test test             L0736 INFO | PASS 1-basic.py:PassTest.test
[stdlog] 2025-11-21 15:09:00,558 avocado.test test             L0718 INFO | 

Is any way to configure the root logger via Avocado or all the loggers from Avocado to avoid the debug logs?

[marioaag]

@richtja do you have any suggestion?

[marioaag]

@clebergnu do you have any suggestion?

[richtja]

Hi @marioaag, if you wan't to track 'avocado.test.progress' stream in separated file. You could use job.run.store_logging_stream option. This will create new file in the test result dir where you will have logs only from this stream. For more info see https://avocado-framework.readthedocs.io/en/latest/guides/writer/chapters/logging.html#using-store-logging-stream and https://avocado-framework.readthedocs.io/en/latest/config/index.html#job-run-store-logging-stream

[marioaag]

Hi @richtja, I'm ok with the avocado.test.progress messages I already found how to control them in the way that we want, the messages that I want to control now and I don't find how are the ones coming from other modules.
I already setup everything that I know to info level but I still getting debug level messages from modules outside of avocado or the test implementation, for example the asyncio module:

[stdlog] 2025-11-21 15:09:00,550 avocado.test test             L0312 INFO | INIT 1-basic.py:PassTest.test
[stdlog] 2025-11-21 15:09:00,552 avocado.utils.deprecation deprecation      L0038 INFO | The data_structures utility is deprecated. It has been moved to the AAutils project and will be removed after the next LTS release. For more information, please see the following link: https://github.com/avocado-framework/aautils
[stdlog] 2025-11-21 15:09:00,552 avocado.utils.deprecation deprecation      L0038 INFO | The path utility is deprecated. It has been moved to the AAutils project and will be removed after the next LTS release. For more information, please see the following link: https://github.com/avocado-framework/aautils
[stdlog] 2025-11-21 15:09:00,554 asyncio selector_events  L0054 DEBUG| Using selector: KqueueSelector     <<-- Unexpected
[stdlog] 2025-11-21 15:09:00,555 avocado.test test             L0526 INFO | START 1-basic.py:PassTest.test
[stdlog] 2025-11-21 15:09:00,555 avocado.test.progress basic            L0013 INFO | Test Info
[stdlog] 2025-11-21 15:09:00,556 avocado.test.progress basic            L0014 WARNI| Test Warning
[stdlog] 2025-11-21 15:09:00,556 avocado.test basic            L0016 INFO | Test log info
[stdlog] 2025-11-21 15:09:00,557 asyncio selector_events  L0054 DEBUG| Using selector: KqueueSelector     <<--- Unexpected
[stdlog] 2025-11-21 15:09:00,557 avocado.test test             L0736 INFO | PASS 1-basic.py:PassTest.test
[stdlog] 2025-11-21 15:09:00,558 avocado.test test             L0718 INFO | 

[richtja]

Hi @marioaag, I did some testing, and it looks like we have a bug here. Therefore, I opened #6248 with a fix. Can you please verify that it fixes your issue? Thank you.

[marioaag]

yes it works as expected!

BTW, the messages related with data_structures and path utilities deprecation is something internal to Avocado that we don't need to do anything, correct?

[richtja]

Thanks for testing.

The warning messages are related to migration of Avocado utilities to a separated project called AAutils. The utilities mentioned in the warning messages has been already migrated and will be removed from Avocado after next LTS release. Therefore, if you are using them in your testing, you will need to migrate your tests also. We will prepare migration guidelines before the LTS release for everybody to follow. For more info, you can read our blueprint or look directly to AAutils repo.

[marioaag]

Thanks @richtja, I'm not calling avocado.utils in my actual code implementation. Just call me attention that even when it is internally call by avocado I get the message in the test logs.