-
Notifications
You must be signed in to change notification settings - Fork 121
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
Removed bad line #195
Removed bad line #195
Conversation
Thanks again! |
I think the failing build must be somehow related to cache? Is there a way to delete all travis' caches from the UI? |
removed all cache and restarted the build |
Did that restart work? |
It doesn't seem to have re-run> |
this is not cache, the issue is that we are a dependency of phpunit. Which is causing issues as always. This is why we were very happy with the scoped phar of phpunit v8. |
It doesn't make sense, though. Composer resolves fine on my machine, and on the PR build. |
there is one main difference, travis is building a commit and not a branch. So what it does is executing the clone command and after that is does: This brings git into a detached mode, so composer does not recognize the package or any alias you are configuring. So it will fail on your machine as well when you execute that command before the composer install. :-) |
Well... we could fix that :P ... |
Give me a sec |
sure, by creating a tag like |
No, I was thinking... just get travis to actually check out the branch we are on, then hard reset to the place we need to be at. |
Actually, I think we can just set |
I am rather hopeful this will work: #196. |
No description provided.