GitLab

@jerome, this patches should improve transparency of what is going on. I decided to do this, because I've hit several tests for which nxdtest log output is completely empty even though corresponding test lines are still in Running state. We want to see just from the log whether nxdtest is stuck or whether it exited cleanly and run n test (with n=0 indicating that it had nothing to run).

Please see details and context in the patch1.

For the reference: here is how updated output looks like in the normal case:

date:   Thu, 09 Dec 2021 04:20:37 CET
xnode:  slapuser7@rapidspace-testnode-001
uname:  Linux rapidspace-testnode-001 4.9.0-16-amd64 #1 SMP Debian 4.9.272-1 (2021-06-21) x86_64
cpu:    Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
# running for test_result_module/20211209-170FD3998
 
>>> pytest
$ python -m pytest
============================= test session starts ==============================
platform linux2 -- Python 2.7.18, pytest-4.6.11, py-1.9.0, pluggy-0.13.1 
rootdir: /srv/slapgrid/slappart7/t/dfp/soft/47cc86af27d234f0464630f2a0d22a6f/parts/zodbtools-dev
collected 46 items
 
zodbtools/test/test_analyze.py .                                         [  2%]
zodbtools/test/test_commit.py ..                                         [  6%]
zodbtools/test/test_dump.py ...                                          [ 13%]
zodbtools/test/test_restore.py ..                                        [ 17%]
zodbtools/test/test_tidrange.py .............................            [ 80%]
zodbtools/test/test_zodb.py .........                                    [100%]
 
========================== 46 passed in 9.15 seconds ===========================
ok      pytest  12.433s # 46t 0e 0f 0s
# ran 1 test case:  1·ok

Thanks, I think this is good.

Thanks, @jerome, let's get this in then.

mentioned in commit kirr/nxdtest@4fe9ee16

mentioned in commit kirr/nxdtest@f8ec5787

added 2 commits

• f8ec5787 - Always log system info and run summary, even if master tells us to do nothing
• 4fe9ee16 - Log that master is connected and for which test_result this run is

Compare with previous version

merged

mentioned in merge request !14 (merged)

mentioned in merge request !13 (merged)