are you sure apc.enable_cli is On ?

@pborreli no I'm not sure, have you any idea of how check if is it "On"?

i think it is as you make more assertions than before, but you can test it with php -i | grep enable_cli inside your before_script section of .travis.yml on another branch.

Ok I will do it.

Sorry I don't get which is the benefit of enablig APC by default in the
test (apart speed)?

On Wed, Mar 13, 2013 at 12:23 AM, Abdellatif AitBoudad <
[email protected]> wrote:

no I'm not sure, have you any idea of how check if is it "On"?

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/7355#issuecomment-14812533
.

liuggio_______________

/|_ We reject kings, presidents and voting.
/o ) / We believe in rough consensus
) v _/\ and running code (I.E.T.F. credo)

@liuggio i guess it won't give any speed gain but/because it will execute all the skipped assertion when apc is not enabled

@pborreli

apc.enable_cli => Off => Off
but can be enabled by adding if necessary:

 echo "apc.enable_cli = 1" >> ~/.phpenv/versions/$(phpenv version-name)/etc/php.ini

You need to enable APC for the CLI so that tests that requires APC won't be skipped. If not, that's useless.

@fabpot apc.enable_cli controls the opcode cache AFAIK, not the user cache (which is the one needed for the tests)

yes that's why adding apc.so was enough to unskip those assertions.
so 👍 for this PR and 👎 for enable_cli