In Focal it is an FTFBS as well, but a different one
=================================== FAILURES ===================================
_______________ TestConnect.test_connect_node_device_create_xml ________________
Fixture "node_device_create" called directly. Fixtures are not meant to be called directly,
but are created automatically when test functions request them as parameters.
See https://docs.pytest.org/en/latest/fixture.html for more information about fixtures, and https://docs.pytest.org/en/latest/deprecations.html#calling-fixtures-directly about how to update your code.
===================== 1 failed, 33 passed in 4.91 seconds ======================
FAIL test_connect.py (exit status: 1)
In Focal it is an FTFBS as well, but a different one
======= ======= ======= ======= ======= FAILURES ======= ======= ======= ======= ======= test_connect_ node_device_ create_ xml ________________ create" called directly. Fixtures are not meant to be called directly, /docs.pytest. org/en/ latest/ fixture. html for more information about fixtures, and /docs.pytest. org/en/ latest/ deprecations. html#calling- fixtures- directly about how to update your code. ======= ======= 1 failed, 33 passed in 4.91 seconds ======= ======= ======= =
_______________ TestConnect.
Fixture "node_device_
but are created automatically when test functions request them as parameters.
See https:/
https:/
=======
FAIL test_connect.py (exit status: 1)
That seems to be /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 952200
https:/
We have the fix for that one in groovy and can cherry-pick it from salsa.