[WIP] Update guzzle and add integration test capabilities settings#29054
[WIP] Update guzzle and add integration test capabilities settings#29054phil-davis wants to merge 5 commits into
Conversation
c82bd78 to
98a362b
Compare
|
duplication of #28063 |
|
Yes, last week I noticed that there was work to move to Guzzle v6 that changed quite a lot of integration test files. So I quickly did a merge of my proposed integration test refactoring changes on top of it - to see if there would be a lot of annoying conflicts. Actually it was quite easy to resolve the conflicts and Jenkins comes up with the same set of test fails as are currently happening in #28063 So my proposed refactorings in #28970 will not cause too much pain (and do not break anything for #28063 ) |
|
@phil-davis feel free to push directly to #28063 if your changes help solving / simplifying the Guzzle update |
|
most of the guzzle related changes are on the tests anyway. The core changes are rather small. |
|
@PVince81 I will look in the morning. After the merge of my integration test stuff today, that WIP PR of yours will have conflicts to be resolved, but they are not difficult. Then there were a list of failed integration test scenarios. From memory, the fails in Jenkins here were the same as in your other PR: so there i a bit of guzzling to be done to tweak it into success. |
|
See #29211 for "the final solution" |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
About to try integrating the Guzzle update with some integration test refactoring.
First pass - the Guzzle change and see if they pass CI OK.