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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rely on own phpunit, not one from CI service #1995
Conversation
Thanks so much for picking this up! |
@@ -25,7 +25,8 @@ | |||
"sebastian/diff": "~1.1" | |||
}, | |||
"require-dev": { | |||
"satooshi/php-coveralls": "0.7.*@dev" | |||
"phpunit/phpunit": "@stable", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wildcards are a bad idea.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@stable
is exactly the same as *
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This of course breaks prefer lowest too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps ~4.0|~5.0
will work fine here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 for ^4|^5
!
@SpacePossum please temporary merge this PR into your once that has problems with AppVeyor and let see if it will help |
- 'if [ "$SYMFONY_VERSION" != "" ]; then sed -i "s/\"symfony\/\([^\"]*\)\": \"[^\"]*\"/\"symfony\/\1\": \"$SYMFONY_VERSION\"/g" composer.json; fi' | ||
|
||
install: | ||
- travis_retry composer global require hirak/prestissimo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This actually ends up slower surely? It takes just as long to install this globally as it does to install the rest.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mean about the time to insstall this library?
Dependencies for this one is very light, it should not be a problem.
@keradus I would ever say that the travis_retry
should not be here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see no reason to drop it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
travis_retry
is good for long with no output jobs.
This command would not take more than 10 minutes to execute.
Plus, travis_retry
drop the original output of the command, harder to read.
This is as you want, but I suggest you to remove this. 👍
thanks, done over @ #1949 (please note I made changes because that PR targets master, but as a POC it should be useful for now) |
@@ -25,7 +25,8 @@ | |||
"sebastian/diff": "~1.1" | |||
}, | |||
"require-dev": { | |||
"satooshi/php-coveralls": "0.7.*@dev" | |||
"phpunit/phpunit": "^4.5|^5", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👎
If we are able to not make it dependents, don't do it.
This will install a lot of dependencies, making composer longer to resolve.
Plus, all developer does not work with vendor/bin/phpunit.
What about directly download the .phar
on travis?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't like fetching some deps by Composer and some not. You don't like it? Cool. You are not enforced to download dev deps.
Composer is nicer way to describe required version. like not supporting 4.1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't like fetching some deps by Composer and some not.
As you want but IMHO, it's more a tool than a "dependency".
You don't like it? Cool. You are not enforced to download dev deps.
Not really true for all projects. Some can require dev packages other than phpunit and we can select which one we want to install.
By installing with composer, you get dependencies described by phpunit, not locked by composer.lock
like for .phar
. This mean you increase the issue risk to get PHPUnit not working because of a sub-dependency update.
So this is not only a matter of taste for me. 😉
Composer is nicer way to describe required version. like not supporting 4.1
Well, if you not support it, tests will fail. :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- tool could be a dependency
- to develop a project you should have a phpunit. you may have global one - cool, but we don't promise that our project is compatible with it.
- theoretically, but such an edge case...
- it;s better to say "this one will work, you may use it" than "some phpunit could work, we dont know, try, and if it fails - well... we dont know which version works"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it;s better to say "this one will work, you may use it" than "some phpunit could work, we dont know, try, and if it fails - well... we dont know which version works"
Or simply rely on the last stable version of PHPUnit. 😉
theoretically, but such an edge case...
Are you talking about the risk to get PHPUnit not working because of a sub-dependency update?
Not such an edge case as you think. 😉
Anyway, at least I have an answer. :-)
So, this fixes AppVeyor bug of #1949 @SpacePossum |
Indeed, AppVeyor is happy, so 🚢 this :) |
AppVeyor break it's PHPUnit, I remember that it happens once with Travis as well. |
So no concern about my last comment? #1995 (comment) :-/ FYI, if you made this PR to fix this error: https://ci.appveyor.com/project/keradus/php-cs-fixer/build/dev-2529 Please not this is not related at all. This was an issue from PHPUnit: sebastianbergmann/phpunit#2219 |
@soullivaneuh answered. If you have some power and willing please focus on something important, like #1119 |
cc @SpacePossum