public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Miroslav Šulc" <fordfrog@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-java/jctools-core/files/
Date: Tue, 17 Sep 2024 07:56:57 +0000 (UTC)	[thread overview]
Message-ID: <1726559803.e2cc1c2ac980244e6128da5d06d9f3bb0d543fa6.fordfrog@gentoo> (raw)

commit:     e2cc1c2ac980244e6128da5d06d9f3bb0d543fa6
Author:     Volkmar W. Pogatzki <gentoo <AT> pogatzki <DOT> net>
AuthorDate: Mon Sep 16 07:05:31 2024 +0000
Commit:     Miroslav Šulc <fordfrog <AT> gentoo <DOT> org>
CommitDate: Tue Sep 17 07:56:43 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e2cc1c2a

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 <AT> pogatzki.net>
Closes: https://github.com/gentoo/gentoo/pull/38622
Signed-off-by: Miroslav Šulc <fordfrog <AT> gentoo.org>

 .../jctools-core/files/jctools-core-4.0.3-increase-TEST_TIMEOUT.patch  | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/dev-java/jctools-core/files/jctools-core-4.0.3-increase-TEST_TIMEOUT.patch b/dev-java/jctools-core/files/jctools-core-4.0.3-increase-TEST_TIMEOUT.patch
index 57941ff69001..f573170ee482 100644
--- a/dev-java/jctools-core/files/jctools-core-4.0.3-increase-TEST_TIMEOUT.patch
+++ b/dev-java/jctools-core/files/jctools-core-4.0.3-increase-TEST_TIMEOUT.patch
@@ -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));


             reply	other threads:[~2024-09-17  7:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-17  7:56 Miroslav Šulc [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-14  8:38 [gentoo-commits] repo/gentoo:master commit in: dev-java/jctools-core/files/ Miroslav Šulc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1726559803.e2cc1c2ac980244e6128da5d06d9f3bb0d543fa6.fordfrog@gentoo \
    --to=fordfrog@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox