component/*/test*cfg: reorganise now that python3 is default

test.cfg becomes the python3 version
a new test-py2.cfg is introduced
test-py3.cfg is removed

cf slapos commit cc7f36a0 (component/defaults: use python3 by default, 2022-08-27)

component/nxdtest/test-py3.cfg → component/nxdtest/test-py2.cfg

@@ -5,4 +5,4 @@ extends =
   test.cfg
 
 [python]
-part = python3
+part = python2.7

component/pygolang/test-py3.cfg → component/pygolang/test-py2.cfg

-# SlapOS software release to test pygolang/py3 on Nexedi testing infrastructure.
+# SlapOS software release to test pygolang/py2 on Nexedi testing infrastructure.
 
 [buildout]
 extends = test.cfg
 
 [python]
-part = python3
+part = python2.7

[Jérome Perrin]

@kirr FYI, we changed the default ${python:part} to be python3, so I also adjusted here. The profiles are also renamed so that the default test.cfg is python3.

I am taking care of updating the test suites for master branch and checking the test run correctly.

[Kirill Smelkov]

@jerome, thanks for the heads up and for caring about this topic.

[Jérome Perrin]

In cc7f36a0 I took care of software/*/software*.cfg but I did not realize there were also test profiles in components, so I'm fixing in follow-up commits.

• This fixed Pygolang.UnitTest-Master.Python2/Pygolang.UnitTest-Master.Python3 and nxdtest.UnitTest-Master.Python3/nxdtest.UnitTest-Master.Python2
• 5cb11e9e fixed ZODB.UnitTest-WC2 there's a test failing in ZEO/functional, but it is not new.
• Wendelin.core.UnitTest-ZODB5, Wendelin.core.UnitTest-ZODB4(xfail) and Wendelin.core.UnitTest-ZODB4-wc2 were not impacted. ie. they are still running python 2.
• Zodbtools.UnitTest-Master, Zodbtools.UnitTest-ZODB4-wc2 and Zodbtools.UnitTest-ZODB5 are still on my TODO list, they fail because they now run with python3, but zodbtools does not support python3 yet. I need to think a bit about how organising the profiles - also, I plan to add them to the test overview page ( https://www.erp5.com/quality/integration )

BTW @kirr what's the py3 status of wendlin.core ? If it supports python3 already, we can create test suites.

[Kirill Smelkov]

@jerome, thanks for the update and fixups.

Wendelin.core itself should support py3 ok, but it is currently blocked on Zodbtools not supporting py3 yet. I've tried to fix this some time ago, and after several unsuccessful trials, that added much noise to the code and were still hard to get to "working right" state, finally draftly done py3 porting in kirr/zodbtools@42799cf6. But to work it needs bstr from Pygolang. This is one of the reasons kirr/pygolang@c9648c44 was started.

[Jérome Perrin]

Oh thanks @kirr it's good to read this. zodbtools is another thing where python3 support will be very welcome

[Kirill Smelkov]

Thanks, @jerome.

[Kirill Smelkov]

Port of Zodbtools to py3: zodbtools!23 (merged).

[Jérome Perrin]

I added profiles for testing 339490eb and corresponding test suites:

                           "Zodbtools.UnitTest-Master-ZODB4-Python2",
                           "Zodbtools.UnitTest-Master-ZODB4-wc2-Python2",
                           "Zodbtools.UnitTest-Master-ZODB5-Python2",
                           "Zodbtools.UnitTest-Master-ZODB4-Python3",
                           "Zodbtools.UnitTest-Master-ZODB4-wc2-Python3",
                           "Zodbtools.UnitTest-Master-ZODB5-Python3",

@kirr I merged the commit and changed the test suites before we had a chance to discuss, I was maybe too fast, but we can of course still change, if you have suggestions don't hesitate.

On change I did is that there is no "default" in the zodb version in the profiles and test suite names, I was thinking that this way if we change the default (from ZODB4 to 5) we don't have a risk to test the same thing twice.

[Kirill Smelkov]

@jerome, thanks. It is ok. I trust you to do such changes without discussion.