Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[phpunit] disable prophecy#18304

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
fabpot merged 1 commit intosymfony:2.3fromnicolas-grekas:no-prophecy
Mar 27, 2016
Merged

Conversation

@nicolas-grekas
Copy link
Member

QA
Branch?2.3
Bug fix?no
New feature?no
BC breaks?no
Deprecations?no
Tests pass?yes
Fixed tickets-
LicenseMIT
Doc PR-

Both Prophecy and Symfony require some phpdocumentor dependencies, but incompatible versions.
Since we don't use Prophecy, let's disable it.
phpunit-mock-objects is forced to v3.1.1 until we fix our test suite (seesebastianbergmann/phpunit-mock-objects#299).

@stof
Copy link
Member

phpunit-mock-objects is forced to v3.1.1 until we fix our test suite

Isn't it fixed already ? A bunch of PRs related to it have been merged already

@stof
Copy link
Member

you forgot to update the cache id

phpunit Outdated
chdir("phpunit-$PHPUNIT_VERSION");
passthru("$COMPOSER remove --no-update symfony/yaml");
passthru("$COMPOSER remove --no-update phpspec/prophecy");
passthru("$COMPOSER require --no-update phpunit/phpunit-mock-objects\"3.1.1\"");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

3.1.1 is not compatible with PHP 5.3 to 5.5

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

This change should not be done for PHPUnit 4.8, as it depends onphpunit/phpunit-mock-objects ~2.3

@stof
Copy link
Member

@nicolas-grekas can you also try to debug failures inhttps://travis-ci.org/symfony/symfony/jobs/118326801#L1867 ? This looks weird as the PropertyAccess 2.3.0 component is installed, and it contains this class. This makes me think there might be a corruption of the installation in our Travis setup

@xabbuh
Copy link
Member

@stof I fixed a lot of mocks Sebastian Bergmann reported for themaster branch. But we still have some issues that are only present on the other branches. I am going to prepare pull requests.

@nicolas-grekas
Copy link
MemberAuthor

@stof comments addressed
@xabbuh don't forget to change the cache id and revert forcing mock-objects to 3.1.1 in your PRs

@nicolas-grekasnicolas-grekas changed the title[phpunit] disable prophecy and force mock-objects to v3.1.1[phpunit] disable prophecyMar 25, 2016
@nicolas-grekas
Copy link
MemberAuthor

Rebased on top of#18306

@nicolas-grekas
Copy link
MemberAuthor

No need to change the cache id btw here

@xabbuh
Copy link
Member

@nicolas-grekas What is the point in adding this but not updating the cache id? This way it doesn't have any affect, does it (seems I do miss something)?

@nicolas-grekas
Copy link
MemberAuthor

The real cache-id is the md5 of the phpunit file itself. The cache id in the comment is just a way to change this md5 without changing actual code.

@dunglas
Copy link
Member

A PR to fix Prophecy is ready:phpspec/prophecy#264

@nicolas-grekas
Copy link
MemberAuthor

@dunglas we don't use prophecy in Symfony's test suite. Should we allow using it? Until now, we've asked people submitting prophecy tests to rewrite them to regular phpunit mock tests. If we stick to this policy, then we should merge this PR. If we should allow prophecy, then not of course.

@fabpot
Copy link
Member

IIUC, prophecy is not a direct dep, but installed but phpunit, right? In any case, we are not using prophecy in Symfony, so let's drop it.

@fabpot
Copy link
Member

And if we start using it, we would then be able to add it explicitly.

@fabpot
Copy link
Member

Thank you@nicolas-grekas.

@fabpotfabpot merged commitae9bae7 intosymfony:2.3Mar 27, 2016
fabpot added a commit that referenced this pull requestMar 27, 2016
This PR was merged into the 2.3 branch.Discussion----------[phpunit] disable prophecy| Q             | A| ------------- | ---| Branch?       | 2.3| Bug fix?      | no| New feature?  | no| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets | -| License       | MIT| Doc PR        | -Both Prophecy and Symfony require some phpdocumentor dependencies, but incompatible versions.Since we don't use Prophecy, let's disable it.phpunit-mock-objects is forced to v3.1.1 until we fix our test suite (seesebastianbergmann/phpunit-mock-objects#299).Commits-------ae9bae7 [phpunit] disable prophecy
@dunglas
Copy link
Member

@nicolas-grekas it was just a side note.

@nicolas-grekasnicolas-grekas deleted the no-prophecy branchMarch 30, 2016 06:44
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@nicolas-grekas@stof@xabbuh@dunglas@fabpot@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp