Re: [VOTE] CI tests RFC
| From: | Stas Malyshev | Date: | Fri, 25 Apr 2014 18:41:13 +0000 |
| Subject: | Re: [VOTE] CI tests RFC | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-73801@lists.php.net to get a copy of this message | ||
Hi!
> Would be nice if we could also create some policy regarding the usage of
> XFAILs (when should be a failing test marked as XFAIL, should we add the
> tests from the open bugreports as XFAIL by default, whose responsibility
> is to make sure that it will be fixed eventually, etc.).
I agree. I didn't get into this but it definitely makes sense to have
some rules there.
> I would also like to extend the current travis config a bit (we could
> have more exts, more axes for stuff like ts/nts builds, enable debug
> builds, so memory leaks are also triggering the test failures, etc.),
You're more than welcome :) I've planned to get to some of it next -
i.e. going through the list of exts and see which ones we can support on
Travis - but any help would be great.
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227