grpc-java

History

Eric Anderson 2cd884ea80 core: Reduce DeadlineTest flake To my knowledge, there has been just a single DeadlineTest flake since the code was fixed to avoid issues with I/O due to class loading: io.grpc.DeadlineTest > defaultTickerIsSystemTicker[0] FAILED java.lang.AssertionError: <-21431071 ns from now> and <0 ns from now> should have been within <20000000ns> of each other But we don't really need fine-grained verification during the test though; if the code is not using nanoTime, then it is almost certainly not going to have even a day of accuracy (except on a fresh VM). So checking for a second of accuracy vs 20ms shouldn't really be an issue.	2016-07-20 09:53:00 -07:00
..
src	core: Reduce DeadlineTest flake	2016-07-20 09:53:00 -07:00
build.gradle	Create new AbstractTransportTest for Transports	2016-02-25 16:23:17 -08:00

Eric Anderson 2cd884ea80 core: Reduce DeadlineTest flake

To my knowledge, there has been just a single DeadlineTest flake since
the code was fixed to avoid issues with I/O due to class loading:

io.grpc.DeadlineTest > defaultTickerIsSystemTicker[0] FAILED
    java.lang.AssertionError: <-21431071 ns from now> and <0 ns from now> should have been within <20000000ns> of each other

But we don't really need fine-grained verification during the test
though; if the code is not using nanoTime, then it is almost certainly
not going to have even a day of accuracy (except on a fresh VM). So
checking for a second of accuracy vs 20ms shouldn't really be an issue.

2016-07-20 09:53:00 -07:00

src

core: Reduce DeadlineTest flake

2016-07-20 09:53:00 -07:00

build.gradle

Create new AbstractTransportTest for Transports

2016-02-25 16:23:17 -08:00