Change the workflow of tests to only require MyISAM on everything
| Project: | Project Issue File Review |
| Version: | 6.x-2.x-dev |
| Component: | Miscellaneous |
| Category: | task |
| Priority: | normal |
| Assigned: | boombatower |
| Status: | closed |
Jump to:
It's becoming apparent through issues like #512762: InnoDB optimization that it's not practical to test every core and contrib patch in queue on every database platform and/or every candidate operating system. It would take too many resources.
DamZ's current PIFR v1 server can fly through 7.x core patches pretty quickly on MySQL MyISAM, so we ad-hoc decided in IRC to only test every patch on Linux-based MyISAM clients. Additional platforms, whatever that might be (Linux/Windows/FreeBSD, etc and MySQL InnoDB 5.0/5.1, PostgreSQL 8.3/8.4, SQLite) should only test commits and open a critical issue with details about any failures on the alternate platforms and db configurations. It'll somehow have to keep track of what failures match which existing issues as well, so as to not flood bomb the issue queue with repeat failures.
Part of the problem with this idea is the current workflow would involve having to re-enable clients after each failure of a clean checkout, which would be unmaintainable.
| Attachment | Size |
|---|---|
| pifr_workflow_chat_log.txt | 3.03 KB |
#1
Let's not rush into this. While Damien is right that testing on every platform is resource intensive, once this starts testing D6 contrib modules, everyone is going to want to have testing servers, and they are going to want to be sure patches are working on their target platform. Let's let this one brew for a bit and keep focused on getting PIFR 2.x clients and servers working as currently designed first.
#2
Per #1
#3
This is configurable and can be changed during run-time.
#4
Automatically closed -- issue fixed for 2 weeks with no activity.