On Fri, Apr 25, 2014 at 9:50 AM, Stas Malyshev <smalyshev@sugarcrm.com>wrote:
> Hi!
>
> I'd like to propose the CI tests RFC for the vote. Please vote at:
> https://wiki.php.net/rfc/travis_ci
>
> The vote is planned to close on May 5. If you have any questions, please
> contact me.
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
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 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.), which could on
the short term cause some "new" test failures (but also give those problems
more visibility, hence better chances to be fixed).
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu