On 11/7/25 1:55 PM, Jan Jasek wrote:
I saw you mentioned parallel running multiple times.
Yes, because it's very annoying that it takes forever, when it could take 32 times less time to build the Horizon package on my 16 cores laptop (my boss bought it to me so I spend less time waiting for builds...).
Pytest-xdist, I was experimenting very very little with it some time ago. It worked fine for “ui-pytests” (where tests are completely independent and running in django live server). I did not have time to experiment much with “integration-pytests” but I am afraid that as the tests there include pagination tests for instance, image, volume, snapshot and all the tests require “resources” in general (like volume resource for all volume snapshot tests, etc.).
I do not run integration tests when building packages. IMO, integration tests should be living in tempest, not in a per-project thing, otherwise it's difficult for me to run them. What I would like to run in parallel is unit tests, which in the past in Horizon, wouldn't run in parallel. As for pytest vs stestr, again, the best thing would be if you could use stestr as test runners, because it has a nice interface (for selecting tests with a regex), even if you're using pytest extensions. That's asking a lot less than just removing all traces of pytest. Though I wont complain too much about this, it's more a strong suggestion than a hard requirement.
being able to run the tests in parallel was not super high priority on my plate - it was to make tests somehow stable and maintainable
Thanks for that already! :)
And I am quite sure that parallel running did not exist in previous integration tests (as they were barely stable).
As I wrote, even unit tests couldn't run in parallel... Switching subject now... One other thing which I think would be awesome, would be getting rid of local_settings.py and get an openstack_dashboard.conf instead, using oslo.config. This has been discussed for like 10 years, but was never achieved. The local_settings.py of Horizon is just horrible to deal with when using config management. In puppet and in Kolla, there's no other choice but using Jinja2 templates, which is barely readable when you add conditionals. Is this still something the team is working on? Or has this been just given-up ? Cheers, Thomas Goirand (zigo) P.S: Do you CC me please, I'm registered to the list, and that's breaking my mail filtering.