-
Notifications
You must be signed in to change notification settings - Fork 844
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
fixing the compareHeaders sorting algorithm #23545
Conversation
Thank you for your contribution @gunjansingh-msft! We will review the pull request and get back to you soon. |
@gunjansingh-msft - The tests of all 3 modules - azblob, azfile, and azdatalake seems to be failing because of -
|
/azp run go - azblob |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run go - azblob |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run go - azblob |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run go - azfile |
/azp run go - azblob |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run go - azblob |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run go - azfile |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run go - azblob |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run go - azblob |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run go - azfile |
Azure Pipelines successfully started running 1 pipeline(s). |
@microsoft-github-policy-service agree |
@microsoft-github-policy-service agree company="Microsoft" |
Fixed a Panic in the test :- TestUploadBlobWithMD5WithCPK() which was caused due to a functional issue in the compareHeaders custom sorting algorithm.