Skip to content
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 "curl: (52) Empty reply from server" error #2860

Merged
merged 3 commits into from
Dec 4, 2020
Merged

Conversation

ceyhun
Copy link
Contributor

@ceyhun ceyhun commented Dec 3, 2020

curl: (52) Empty reply from server errors are happening randomly during Upload .app to sauce labs step on macOS e2e test jobs:

One of the solutions suggested by Sauce Labs is to upgrade curl to a newer version:
https://support.saucelabs.com/hc/en-us/articles/360052420274--Empty-reply-from-server-when-uploading-application-to-Sauce-Storage-using-curl

And that's what is done in this PR.

To test:

Check if Test iOS on Device CI jobs are successful.

PR submission checklist:

  • I have considered adding unit tests where possible.
  • I have considered if this change warrants user-facing release notes more info and have added them to RELEASE-NOTES.txt if necessary.

@ceyhun ceyhun requested a review from hypest December 3, 2020 11:04
Copy link
Contributor

@hypest hypest left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only left one non-blocking comment, LGTM otherwise!

@ceyhun ceyhun force-pushed the fix/ci-52-empty-reply branch from a5b9ccd to 561456b Compare December 4, 2020 17:19
@peril-wordpress-mobile
Copy link

Wanna run full suite of Android and iOS UI tests? Click here and 'Approve' CI job!

@ceyhun ceyhun merged commit 83fccc8 into develop Dec 4, 2020
@ceyhun ceyhun deleted the fix/ci-52-empty-reply branch December 4, 2020 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants