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.

Sign up for GitHub

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

Jump to bottom

latest iOS cbl 2.1.0 builds are crashing #2150

Closed
sridevi-15 opened this issue May 2, 2018 · 2 comments
Closed

latest iOS cbl 2.1.0 builds are crashing #2150

sridevi-15 opened this issue May 2, 2018 · 2 comments
Assignees
@sridevi-15
Labels
functional-test-blocker
Milestone
2.1.0

Comments

@sridevi-15
Copy link

sridevi-15 commented May 2, 2018 •
edited

Version

CBL - 2.1.0-150
sg version -> 2.1.0-55

Issue caused

  1. Running ios functional tests on jenkins having crash on the app and bunch of tests failing

I ran tests with 2.1.0-126 and that looks good

If I run tests individually, it works fine.

Logs:

CBLTestServer-iOS_2018-04-30-154305-1_Dans-Test-MacBook-Pro.crash.zip
@sridevi-15 sridevi-15 added this to the 2.1.0 milestone May 2, 2018
@sridevi-15 sridevi-15 changed the title latest cbl 2.1.0 builds are crashing latest iOS cbl 2.1.0 builds are crashing May 2, 2018
@djpongh djpongh added the ready label May 4, 2018
pasin added a commit that referenced this issue May 4, 2018
@pasin
Fixed #2148 by converting zero data w/ EOF into ENOTCONN error
12d1387 
* Refixed #2140 by converting zero data with EOF stream response into ENOTCONN error so that the retry logic could be kicked in.
* Made a speculative fix for #2150 by reverting fa0f920 commit.
@pasin
Copy link
Contributor

pasin commented May 4, 2018

Please try with build 156. Thanks.

@pasin pasin assigned sridevi-15 and unassigned pasin May 4, 2018
@sridevi-15
Copy link
Author

testing on build 159 and it looks good. Do not see any crash

@snej snej removed the ready label May 10, 2018
pasin added a commit that referenced this issue May 19, 2018
@pasin
Fixed #2148 by converting zero data w/ EOF into ENOTCONN error
f46d193 
* Refixed #2140 by converting zero data with EOF stream response into ENOTCONN error so that the retry logic could be kicked in.
* Made a speculative fix for #2150 by reverting fa0f920 commit.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sridevi-15 sridevi-15

Labels
functional-test-blocker
Projects
None yet
Milestone
2.1.0
Development

No branches or pull requests
5 participants
@snej @pasin @ritamcouchbase @sridevi-15 @djpongh