-
Notifications
You must be signed in to change notification settings - Fork 9.1k
[ABFS] [Backport 3.4] Back Merging PRs from trunk to Branch 3.4 #6611
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
Conversation
… for connection timeout. (apache#5881) Contributed By: Anuj Modi
…fication of the request content during transport (apache#6069) Contributed By: Anuj Modi
🎊 +1 overall
This message was automatically generated. |
:::: AGGREGATED TEST RESULT :::: HNS-OAuth[INFO] Results: HNS-SharedKey[INFO] Results: NonHNS-SharedKey[INFO] Results: AppendBlob-HNS-OAuth[INFO] Results: Time taken: 22 mins 43 secs. |
🎊 +1 overall
This message was automatically generated. |
I think what I will do here is check this branch out then cherrypick each PR in order, so that they are still two separate PRs. Do you see any problem with this? |
I think it will depend on the fact first commit works as it its and is not dependent on second one. We need to merge these separately such that if we have to revert in future we can revert only one. |
Cp'ed the first one, compiled and ran azure tests. It went fine. Will do the same for 2nd one and combine the checkstyle in 2nd one. |
Right.. |
Merged into branch-3.4. |
Description of PR
Following two PRs were merged to trunk.
#5881
#6069
These two PRs may have conflicts thus creating this single backport PR to avoid any merge issues.
Commits Backported from trunk:
1336c36
99b9e7f
How was this patch tested?
Both the commits were cherry-picked and ABFS Test Suite was run.