From c61b4af33d226fdde05cc7bf02845323c9087096 Mon Sep 17 00:00:00 2001 From: Eric Anderson Date: Mon, 16 May 2022 11:09:41 -0700 Subject: [PATCH] benchmarks: Raise timeout for aarch64 runUnaryBlockingClosedLoop is failing after 10.3s, which means 5.3s was probably spent loading the LoadWorker. That means things are likely indeed slow enough that 5s isn't enough time to wait for the server to start. A successful execution of runUnaryBlockingClosedLoop takes 12.1 seconds, which again points to general slow execution. --- .../src/test/java/io/grpc/benchmarks/driver/LoadWorkerTest.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/benchmarks/src/test/java/io/grpc/benchmarks/driver/LoadWorkerTest.java b/benchmarks/src/test/java/io/grpc/benchmarks/driver/LoadWorkerTest.java index 0d40b2f6b5..827c514df8 100644 --- a/benchmarks/src/test/java/io/grpc/benchmarks/driver/LoadWorkerTest.java +++ b/benchmarks/src/test/java/io/grpc/benchmarks/driver/LoadWorkerTest.java @@ -42,7 +42,7 @@ import org.junit.runners.JUnit4; public class LoadWorkerTest { - private static final int TIMEOUT = 5; + private static final int TIMEOUT = 10; private static final Control.ClientArgs MARK = Control.ClientArgs.newBuilder() .setMark(Control.Mark.newBuilder().setReset(true).build()) .build();