Hello, As the subject states, this is about python3-django recipes in Kirkstone - if you are not interested in them, then this email won't be too useful for you.
Motivated by Haixiao's findings about problems in python3-django/2.2.28 recipe[1], I wanted to add some (p)tests to these recipes at least in my test layer, to avoid such regressions in the future. Django comes with a comprehensive testsuite fortunately (over 10k tests, increasing with each release). I have worked on that in the past days, and have found some further issues. Some of them are coming from our patches, some are problems that come from changed behavior of dependencies - I hope that my patches from the past days mitigate most of them. The current state of Django in Kirkstone (after applying the patches from Haixiao and me): * v2.2.28: 1 non-selenium test fails, otherwise the suite passes. The test is about sending emails with recipients declared as lazy_strings. I was able to find a patch that fixed that test, but it broke two other tests... for now this one will stay broken (unless someone else looks into it). There are some Selenium tests that are broken, not sure about the root cause yet. (But it requires a very old version of Selenium, and don't know if it is fully compatible with the latest Firefox version, that I was using for testing) There is however one important caveat: Django 2.2.28 does not officially support the Python version that comes with Kirkstone. The latest it supports is 3.9 - but Kirkstone comes with 3.10. Though I think after the recent patches it works as good as it can (based on the tests at least), if someone still relies on this old version and must stay on Kirkstone, this might be a new reason to migrate to a newer version of Django. * v3.2.25: After applying the recent patches, the whole non-Selenium testuite passes. Regarding the Selenium tests: there are 2 flaky tests that sometimes pass, and sometimes fail, otherwise it's also passing. I have wasted too much of my life on fixing flaky Selenium tests in the past, so I will just ignore this. (If someone wants to fix them, I'm very happy to take patches of course). I consider this version of Django to be in a good shape (though EOL by upstream). * v4.2.26: The testsuite passes without additional patches. It also has the same flaky Selenium tests as v3.2.25. If anyone's curious about the the ptest recipes, you can find the relevant bbappends in my test layer[2]. The test output is not yet ptest-compatible, and note that it has some extra dependencies: meta-firefox, meta-firefox-test, meta-clang and meta-lts-mixins/rust-kirkstone. I'm planning a Django-only Kirkstone PR next week (I don't want to have very broken recipes for very long), but want to leave the patches to float on the ML for a few days, to see if there is any feedback. Any questions or comments -> just reply to this message. Thank you, Gyorgy [1]: https://lists.openembedded.org/g/openembedded-devel/message/123443 [2]: https://github.com/OldManYellsAtCloud/meta-oe-test/commit/0b5967e555f1f36c9c1384b431aeb0e50895ac1d
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#123507): https://lists.openembedded.org/g/openembedded-devel/message/123507 Mute This Topic: https://lists.openembedded.org/mt/117278464/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
