logging not captured #402

zsluedem · 2019-01-13T03:54:56Z

test_5.py file content

import logging
logger = logging.getLogger(__file__)

def test_1():
    logger.info('123123')

def test_2():
    logger.info('123123')

def test_3():
    logger.info('123123')

def test_4():
    logger.info('123123')

pytest.ini

[pytest]
log_cli=true
log_cli_level=DEBUG
log_format = %(asctime)s %(levelname)s (%(threadName)-10s) %(filename)s:%(lineno)d %(message)s
log_date_format = %Y-%m-%d %H:%M:%S

run pytest test/test_5 -n auto

logs:

================================================================= test session starts =================================================================
platform darwin -- Python 3.6.5, pytest-4.1.1, py-1.7.0, pluggy-0.8.1 -- /Users/w/.virtualenvs/pytest_xdist_fixture_scope_test/bin/python
cachedir: .pytest_cache
rootdir: /Users/w/pytest_xdist_fixture_scope_test, inifile: pytest.ini
plugins: xdist-1.26.0, forked-1.0.1
[gw0] darwin Python 3.6.5 cwd: /Users/w/pytest_xdist_fixture_scope_test
[gw1] darwin Python 3.6.5 cwd: /Users/w/pytest_xdist_fixture_scope_test
[gw2] darwin Python 3.6.5 cwd: /Users/wpytest_xdist_fixture_scope_test
[gw3] darwin Python 3.6.5 cwd: /Users/wpytest_xdist_fixture_scope_test
[gw0] Python 3.6.5 (default, Apr 25 2018, 14:23:58)  -- [GCC 4.2.1 Compatible Apple LLVM 9.1.0 (clang-902.0.39.1)]
[gw1] Python 3.6.5 (default, Apr 25 2018, 14:23:58)  -- [GCC 4.2.1 Compatible Apple LLVM 9.1.0 (clang-902.0.39.1)]
[gw2] Python 3.6.5 (default, Apr 25 2018, 14:23:58)  -- [GCC 4.2.1 Compatible Apple LLVM 9.1.0 (clang-902.0.39.1)]
[gw3] Python 3.6.5 (default, Apr 25 2018, 14:23:58)  -- [GCC 4.2.1 Compatible Apple LLVM 9.1.0 (clang-902.0.39.1)]
gw0 [4] / gw1 [4] / gw2 [4] / gw3 [4]
scheduling tests via LoadScheduling

test/test_5.py::test_1
test/test_5.py::test_2
[gw0] [ 25%] PASSED test/test_5.py::test_1
test/test_5.py::test_3
[gw1] [ 50%] PASSED test/test_5.py::test_2
[gw2] [ 75%] PASSED test/test_5.py::test_3
test/test_5.py::test_4
[gw3] [100%] PASSED test/test_5.py::test_4

============================================================== 4 passed in 1.47 seconds ===============================================================

There are no logs print out.
I saw #256 , but it doesn't help

The text was updated successfully, but these errors were encountered:

nicoddemus · 2019-01-17T21:17:19Z

Hi @zsluedem,

Thanks for the report.

If you force one of the tests to fail and use logging.warning, you will see the output:

def test_3():
    logger.warning('123123')
    assert 0

λ pytest .tmp\test-capture.py -n2 -q
bringing up nodes...
F                                                                                            [100%]
============================================ FAILURES =============================================
_____________________________________________ test_3 ______________________________________________
[gw0] win32 -- Python 3.6.3 x:\pytest-xdist\.env36\scripts\python.exe

    def test_3():
        logger.warning('123123')
>       assert 0
E       assert 0

.tmp\test-capture.py:12: AssertionError
---------------------------------------- Captured log call ----------------------------------------
2019-01-17 19:14:16 WARNING (MainThread) test-capture.py:11 123123
1 failed in 0.76 seconds

I'm using logging.warning because that's the default logging setting, and I suspect that log_cli_level setting in your pytest.ini is not having an effect is due to a problem on how config is initialized in workers. This is something which @RonnyPfannschmidt is working on.

simonfontana · 2019-05-13T11:13:13Z

Hi @nicoddemus. Could you link the issue that @RonnyPfannschmidt is working on?

nicoddemus · 2019-05-16T19:25:31Z

Sure, it is actually a "project" involving a lot of issues: https://github.com/pytest-dev/pytest/projects/2

sourcecode14 · 2019-05-29T12:31:06Z

@nicoddemus and @RonnyPfannschmidt : Can you please let me know , when this issue will be resolved , as we are facing issues due to this . Awaiting your reply .

nicoddemus · 2019-05-29T14:23:46Z

Hi @sagardaine,

Unfortunately @RonnyPfannschmidt is a hiatus right now, so this work is halted at the moment. @RonnyPfannschmidt can provide more information about when he plans to get back to this.

nicoddemus · 2019-05-29T14:34:51Z

Indeed it is a initialization problem, reproducible example:

import logging

logger = logging.getLogger('foo')
def test_3():
    logger.info('123123')
    assert 0

[pytest]
log_cli=true
log_cli_level=DEBUG

 λ pytest test_foo.py
======================== test session starts ========================
...
collected 1 item

test_foo.py::test_3
--------------------------- live log call ---------------------------
INFO     foo:test_foo.py:5 123123
FAILED                                                         [100%]

============================= FAILURES ==============================
______________________________ test_3 _______________________________

    def test_3():
        logger.info('123123')
>       assert 0
E       assert 0

test_foo.py:6: AssertionError
------------------------- Captured log call -------------------------
INFO     foo:test_foo.py:5 123123
===================== 1 failed in 0.03 seconds ======================

λ pytest test_foo.py -n2
======================== test session starts ========================
gw0 [1] / gw1 [1]
scheduling tests via LoadScheduling

test_foo.py::test_3
[gw0] [100%] FAILED test_foo.py::test_3

============================= FAILURES ==============================
______________________________ test_3 _______________________________
[gw0] win32 -- Python 3.7.3 c:\users\bruno.esss.co\temp\.env-test-packs\scripts\python.exe

    def test_3():
        logger.info('123123')
>       assert 0
E       assert 0

test_foo.py:6: AssertionError
===================== 1 failed in 0.44 seconds ======================

nicoddemus · 2019-05-29T14:38:25Z

Hmm on the other hand, I just noticed that not using log_cli, but just normal logging capture, works as expected:

[pytest]
log_level=DEBUG

λ pytest test_foo.py -n2
======================== test session starts ========================
...
gw0 [1] / gw1 [1]
F                                                              [100%]
============================= FAILURES ==============================
______________________________ test_3 _______________________________
[gw0] win32 -- Python 3.7.3 c:\users\bruno.esss.co\temp\.env-test-packs\scripts\python.exe

    def test_3():
        logger.info('123123')
>       assert 0
E       assert 0

test_foo.py:6: AssertionError
------------------------- Captured log call -------------------------
INFO     foo:test_foo.py:5 123123
===================== 1 failed in 0.42 seconds ======================

So it does not seem to be a problem with initialization, but with capturing output on workers, which is a long standing issue and hard to fix (#296).

neXussT · 2019-10-24T18:50:18Z

I'm running into this as well. I need my fixtures to print out INFO level logs, but they are never seen, nor are ERROR level during a successful run (tried, just to see). v1.30.0

karaage-kkkris · 2020-02-03T18:01:01Z

Hey, I have the same request related to this ticket. I need the tests and fixtures to print out INFO level logs since some logs are important for people to check. Do not know if there is a solution right now. Thanks.

andreabisello · 2020-08-03T13:16:26Z

one year 7 months later, someone has found a workaround?

pytest-xdist is too much important for me ( many thanks pytest-xdist plugin developers <3 ) but i need to store DEBUG logs in a file and output ERROR log in console.

for now , it is only possible to store anything in the file but obtain console output only if test is failing, right?

many thanks.

andreabisello · 2020-08-19T15:17:53Z

Hmm on the other hand, I just noticed that not using log_cli, but just normal logging capture, works as expected:

[pytest]
log_level=DEBUG

λ pytest test_foo.py -n2
======================== test session starts ========================
...
gw0 [1] / gw1 [1]
F                                                              [100%]
============================= FAILURES ==============================
______________________________ test_3 _______________________________
[gw0] win32 -- Python 3.7.3 c:\users\bruno.esss.co\temp\.env-test-packs\scripts\python.exe

    def test_3():
        logger.info('123123')
>       assert 0
E       assert 0

test_foo.py:6: AssertionError
------------------------- Captured log call -------------------------
INFO     foo:test_foo.py:5 123123
===================== 1 failed in 0.42 seconds ======================

So it does not seem to be a problem with initialization, but with capturing output on workers, which is a long standing issue and hard to fix (#296).

mmh i think not,

log area overwritten and corrupted, for example this is a log without xdist

19-08-2020 17:15:57 test_prima_funzionalita.py test_rosso_uno WARNING warning!
19-08-2020 17:15:57 test_prima_funzionalita.py test_rosso_uno ERROR error!
19-08-2020 17:15:57 test_prima_funzionalita.py test_rosso_uno CRITICAL critical!
19-08-2020 17:15:57 test_prima_funzionalita.py test_rosso_due WARNING warning!
19-08-2020 17:15:57 test_prima_funzionalita.py test_rosso_due ERROR error!
19-08-2020 17:15:57 test_prima_funzionalita.py test_rosso_due CRITICAL critical!
19-08-2020 17:15:57 test_prima_funzionalita.py test_rosso_tre WARNING warning!
19-08-2020 17:15:57 test_prima_funzionalita.py test_rosso_tre ERROR error!
19-08-2020 17:15:57 test_prima_funzionalita.py test_rosso_tre CRITICAL critical!
19-08-2020 17:15:57 test_seconda_funzionalita.py test_bianco WARNING warning!
19-08-2020 17:15:57 test_seconda_funzionalita.py test_bianco ERROR error!
19-08-2020 17:15:57 test_seconda_funzionalita.py test_bianco CRITICAL critical!
19-08-2020 17:15:57 test_seconda_funzionalita.py test_verde WARNING warning!
19-08-2020 17:15:57 test_seconda_funzionalita.py test_verde ERROR error!
19-08-2020 17:15:57 test_seconda_funzionalita.py test_verde CRITICAL critical!
19-08-2020 17:15:57 test_seconda_funzionalita.py test_arancione WARNING warning!
19-08-2020 17:15:57 test_seconda_funzionalita.py test_arancione ERROR error!
19-08-2020 17:15:57 test_seconda_funzionalita.py test_arancione CRITICAL critical!

this is with -n auto

19-08-2020 17:16:19 test_prima_funzionalita.py test_rosso_due WARNING warning!
19-08-2020 17:16:19 test_prima_funzionalita.py test_rosso_due ERROR error!
19-08-2020 17:16:19 test_prima_funzionalita.py test_rosso_due CRITICAL critical!
cal!

you see "cal" is a piece of a row or log, and you get only 4

nicoddemus · 2020-08-19T18:53:20Z

for now , it is only possible to store anything in the file but obtain console output only if test is failing, right?

Yes that is right: we can't transmit arbitrary output from workers easily under the current xdist implementation (which uses execnet under the covers), which is the same problem as in #296.

andreabisello · 2020-08-26T15:18:21Z

for now , it is only possible to store anything in the file but obtain console output only if test is failing, right?

Yes that is right: we can't transmit arbitrary output from workers easily under the current xdist implementation (which uses execnet under the covers), which is the same problem as in #296.

thanks @nicoddemus but not sure, in my use case, file logging will be corrupted (see the previous comment), so with xdist is never possible to log anything, console or file. If you think logging to file should work, maybe there is something wrong in my configuration. Another question is "why does pytest-logger is working with xdist?"

az-pz · 2021-07-15T21:24:11Z

If anyone stumbles upon this, there is a workaround. Use

import sys
sys.stdout = sys.stderr

Use this only for debugging purposes.
Credit: https://stackoverflow.com/a/37210976/2312300

JonesKenzie · 2021-07-26T13:49:42Z

@arizzubair sorry I tried this solution but I couldn't figure out how to make it work. I guess this is not a replacement for Live Logs?

Any way, there are no available solution yet to show live logs?

az-pz · 2021-07-26T14:37:39Z

@JonesKenzie , did you use -s, -vvvv and --log-cli-level=debug arguments while running tests?

Lz1427611970 · 2022-10-27T03:47:46Z

Mark it and I'll try again if it solves the problem，thanks.

This provides incremental output when test is running _without xdist_, just like the old runner did. With xdist the live output is not available, I believe because of pytest-dev/pytest-xdist#402 pytest-dev/pytest-xdist#883 might help with that, but I'm not going to hold my breath until it is available on distros we use.

This provides incremental output when test is running _without xdist_, just like the old runner did. With xdist the live output is not available, I believe because of pytest-dev/pytest-xdist#402 pytest-dev/pytest-xdist#883 might help with that, but I'm not going to hold my breath until it is available on distros we use. (cherry picked from commit d0619c7)

nicoddemus changed the title ~~logging not capture~~ logging not captured Jul 10, 2019

nicoddemus mentioned this issue Jul 10, 2019

pytest xdist is unable to capture logs pytest-dev/pytest#5586

Closed

neXussT mentioned this issue Oct 26, 2019

Ability to execute certain tests sequentially while using -n (xdist) #385

Open

andreabisello mentioned this issue Aug 3, 2020

xdist + logging + @parametrize log on file only the latest test execution #567

Open

andreabisello mentioned this issue Aug 19, 2020

Option --logger-logsdir doesn't work well with pytest-xdist aurzenligl/pytest-logger#14

Closed

arssher mentioned this issue Sep 21, 2021

reenable parallel test runs in CI neondatabase/neon#637

Merged

IAlibay mentioned this issue Feb 23, 2022

HydrogenBondAnalysis log warn test fails with more than 4 workers MDAnalysis/mdanalysis#3543

Open

ian-r-rose mentioned this issue Aug 19, 2022

Improve traceability between currently-running tests and Coiled resources they create coiled/benchmarks#267

Open

5 tasks

kurt-cb mentioned this issue Mar 3, 2023

added code to honor --log-cli-level (issue #402) #883

Open

2 tasks

kurt-cb mentioned this issue Apr 25, 2023

Allow one test per node #894

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

logging not captured #402

logging not captured #402

zsluedem commented Jan 13, 2019

nicoddemus commented Jan 17, 2019

simonfontana commented May 13, 2019 •

edited

Loading

nicoddemus commented May 16, 2019

sourcecode14 commented May 29, 2019

nicoddemus commented May 29, 2019

nicoddemus commented May 29, 2019

nicoddemus commented May 29, 2019

neXussT commented Oct 24, 2019

karaage-kkkris commented Feb 3, 2020 •

edited

Loading

andreabisello commented Aug 3, 2020 •

edited

Loading

andreabisello commented Aug 19, 2020

nicoddemus commented Aug 19, 2020

andreabisello commented Aug 26, 2020

az-pz commented Jul 15, 2021

JonesKenzie commented Jul 26, 2021

az-pz commented Jul 26, 2021

Lz1427611970 commented Oct 27, 2022

logging not captured #402

logging not captured #402

Comments

zsluedem commented Jan 13, 2019

nicoddemus commented Jan 17, 2019

simonfontana commented May 13, 2019 • edited Loading

nicoddemus commented May 16, 2019

sourcecode14 commented May 29, 2019

nicoddemus commented May 29, 2019

nicoddemus commented May 29, 2019

nicoddemus commented May 29, 2019

neXussT commented Oct 24, 2019

karaage-kkkris commented Feb 3, 2020 • edited Loading

andreabisello commented Aug 3, 2020 • edited Loading

andreabisello commented Aug 19, 2020

nicoddemus commented Aug 19, 2020

andreabisello commented Aug 26, 2020

az-pz commented Jul 15, 2021

JonesKenzie commented Jul 26, 2021

az-pz commented Jul 26, 2021

Lz1427611970 commented Oct 27, 2022

simonfontana commented May 13, 2019 •

edited

Loading

karaage-kkkris commented Feb 3, 2020 •

edited

Loading

andreabisello commented Aug 3, 2020 •

edited

Loading