-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Smoke tests #8636
Smoke tests #8636
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8636 +/- ##
==========================================
- Coverage 87.33% 81.17% -6.16%
==========================================
Files 148 148
Lines 18515 18515
Branches 3163 3163
==========================================
- Hits 16170 15030 -1140
- Misses 2060 3197 +1137
- Partials 285 288 +3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
* Added initial/sanity smoke tests * Allow using all integration tests tasks in the smoke tests environment, in addition to smoke tests specific tasks (to reuse existing tests tasks) * Added xdist support to smoke tests only * Added CI workflow for building the smoke tests dockerfiles * Added new tox env to clean resources & remains from the smoke tests: tox -e clean
* Fixed bug in test: test_prefetch_count_restored() * Changed all smoke tests workers log level from INFO to DEBUG * Changed usage of wait_for_log() -> assert_log_exists()
* Added auto-session redis:latest container to smoke tests
Hey friend - you've jumped the gun a bit. Also, the v5.4 topic is premature - I want to handle this release when the time comes due to the significant changes I am developing for it. I suggest closing it for now, thank you. |
I just tried to initiate the process. not to take your work. Also you can also be the RM for 5.4 if you want. we can discuss further, and if it seems premature we can close for now! no problem at all |
I hope my tone didn't sound offensive 🙏 Thank you for everything bro ! 👑 |
I thought it offended you so I tried to clarify and ask for apology! I'm with you fully in your next plans! |
All good 🙂 |
No description provided.