Skip to content
This repository has been archived by the owner on Jun 30, 2020. It is now read-only.

Validate return code behavior #36

Open
mbestavros opened this issue Jul 11, 2019 · 0 comments
Open

Validate return code behavior #36

mbestavros opened this issue Jul 11, 2019 · 0 comments

Comments

@mbestavros
Copy link
Contributor

Originally reported by @npmccallum.

Most of the unknown error codes are commented with FIXME. However, we need lots of tests here. Basically, we need to test similar behavior in plain sockets (without TLSSock), then dlopen() TLSSock, then test the behavior again to see that we get the same behavior.
@mbestavros mbestavros added this to Triage in Planning Jul 14, 2020
@npmccallum npmccallum removed this from Triage in Planning Jul 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mbestavros