Conversation
Gbp-Pq: Name 0001-Fix-a-few-tests.patch
|
I added a second commit that tweaked the imports in the testsuite, to allow running it on an installed system as well as during the build, for the autopkgtests CI system in Debian. |
|
Hi Rolland, which prints out where the library is loaded: while the same script ruun without the option tests a local installation. I don't know precisely how debian tests are launched but this should be fixed in the debian scripts. Cheers, Jerome |
|
The autopkgtests (as well as the build-time testsuite) are run with a simple "pythonX -m unittest discover -v" (with X iterating across supported Python versions). This leaves the logic in unittest's hands, greatly simplifiyng the running of the testsuite, and avoids having to ship run_tests.py, bootstrap.py and the pyproject.toml file in the temporary dir from where the tests are run, avoids having two different ways to run tests, and also avoids having to ship the tests themselves in the installed package. So I'm curious, what does run_tests.py do in addition to that? Is it something that's relevant to the packaging, or mainly to the upstream authors? I can of course revert that part of the patch if it's not relevant to you, but I'm unsure about how best to run the tests in the packaging/distro environments. |
|
|
74f2e88 to
5d7f472
Compare
|
Okay, I removed the second commit from the PR and will only keep it as Debian-specific patch. |
|
Thanks Roland |
Hi,
Roland Mas here, as the maintainer of the Debian packages for Freesas. I started updating the packages to v2024.09.0 today, and I found a few errors in the testsuite. I fixed them as best I could, so I submit them to you in the hope that the patch can be included in your repository so as to reduce the need for a Debian-specific patch in the future.
Feel free to comment or request changes :-)