Update OsTest#test_socket_setSockoptTimeval_effective (again)
This change goes back to the behaviour before I91f729f8637bf8cea819,
but allows "rounding errors" for all kernels rather than just kernel
before 3.0.18.
Change I91f729f8637bf8cea819 read the receive timeout back after
setting it and used that as the basis for determining premature
timeout. However, on go/art-builtbot some devices report a larger
timeout than requested (it appears to have been rounded up) and this
lead to failures.
Bug: 216667550
Test: atest CtsLibcoreTestCases:libcore.android.system.OsTest#test_socket_setSockoptTimeval_effective
Change-Id: I94f72b81b4625323823410a62eb5e29ddbeb77fc
1 file changed