-
Notifications
You must be signed in to change notification settings - Fork 498
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
Fix Travis CI #302
Fix Travis CI #302
Conversation
Codecov Report
@@ Coverage Diff @@
## master #302 +/- ##
============================================
- Coverage 92.11% 91.94% -0.18%
- Complexity 0 760 +760
============================================
Files 21 21
Lines 1762 1762
============================================
- Hits 1623 1620 -3
- Misses 139 142 +3
Continue to review full report at Codecov.
|
This "could" be merged now, at least the PHPUnit failures are now visible, fixing those should get passing Travis CI jobs for PHP 5.3 - PHP 7.2 I haven't even looked at any HHVM issues, I expect them to fail and should more than likely be removed, though I'm not sure who else apart from WordPress is using this library PHP 5.2 is broken, because Composer requires >PHP 5.3, I can follow up fixes for PHP 5.2 in a subsequent PR. |
If I can get someone to approve this I'll merge it 🎉 |
- composer install --dev --no-interaction | ||
- TESTPHPBIN=$(phpenv which php) | ||
- phpenv local --unset |
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.
Does composer install
work on PHP 5.2 though? That was the issue previously which required the phpenv
hack.
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 does not, I'll add back Composer for PHP 5.2 in a follow-up PR, it was quicker and easier to have some CI functionality for the majority of PHP versions rather than nothing, now all but PHP 5.2 and HHVM work, previously all CI jobs were erroring
I'm hesitant to merge a PR that doesn't actually fix the tests. Based on the failures I see on https://travis-ci.org/rmccue/Requests/jobs/315173786, it seems like the local HTTP server isn't actually running, which I suspect is due to removing the |
That’s fair enough, I hadn’t dug in any further than confirming PHPUnit tests were now running (previously they were not) I’m also pretty unfamiliar with this library, I’ll take a look at what the HTTP server bits look like and take a stab at fixing that, and PHP 5.2 As to fixing the bugs reported I’ll be leaving that others cc @dd32 |
Looks like the proxy failure is due to mitmproxy not supporting Python 2:
|
I took a further swing at it, here's the green result: https://travis-ci.org/dd32/Requests/builds/315356440 from https://github.com/dd32/Requests/tree/pr/302 specifically https://github.com/dd32/Requests/commit/3bbcd2bd55b0f29a42ebb6c886201f24e10b6a1e, https://github.com/dd32/Requests/commit/80291d262501acbe87b36284c74409e88e9e39e4, https://github.com/dd32/Requests/commit/4b91d503f025adde368d1cd6b48476660f22c56a, and https://github.com/dd32/Requests/commit/6493d638d901a9ecc06bc9715e5f2fd2cd6e4944 (I can't push to the PR here)
|
@dd32 you rock. I totally gave up on phpenv when trying to fix. I completely agree on HHVM. So, what's next ? We close here and you open a new PR to merge it? |
@dd32 Thanks for that! Let's PR that up and get it merged.
Happy to drop compatibility with it now that they're no longer aiming for PHP compatibility. |
This is a WIP to fix Travis CI -
Do Not Merge Yet🤖Cherry picking various pieces from #298 and #280