dev-java/jctools-core: duplicate test timeout value #939725

This bug seems specific to slower hardware while it cannot be reproduced on
other computers. We duplicate again, this time 'TEST_TIMEOUT = 120000'

Closes: https://bugs.gentoo.org/939725
Signed-off-by: Volkmar W. Pogatzki <gentoo@pogatzki.net>
Closes: https://github.com/gentoo/gentoo/pull/38622
Signed-off-by: Miroslav Šulc <fordfrog@gentoo.org>
This commit is contained in:
Volkmar W. Pogatzki
2024-09-16 09:05:31 +02:00
committed by Miroslav Šulc
parent 6bfd470b7f
commit e2cc1c2ac9

View File

@@ -1,5 +1,6 @@
https://bugs.gentoo.org/863977
https://bugs.gentoo.org/924135
https://bugs.gentoo.org/939725 for 120000
--- a/src/test/java/org/jctools/util/TestUtil.java
+++ b/src/test/java/org/jctools/util/TestUtil.java
@@ -8,7 +9,7 @@ https://bugs.gentoo.org/924135
public static final int CONCURRENT_TEST_DURATION = Integer.getInteger("org.jctools.concTestDurationMs", 500);
public static final int CONCURRENT_TEST_THREADS = Integer.getInteger("org.jctools.concTestThreads", Math.min(4, Runtime.getRuntime().availableProcessors()));
- public static final int TEST_TIMEOUT = 30000;
+ public static final int TEST_TIMEOUT = 60000;
+ public static final int TEST_TIMEOUT = 120000;
private static final AtomicInteger threadIndex = new AtomicInteger();
public static void sleepQuietly(long timeMs) {
LockSupport.parkNanos(TimeUnit.MILLISECONDS.toNanos(timeMs));