From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: 41394@debbugs.gnu.org
Subject: bug#41394: java-testng: again nondeterministic test-failures?
Date: Tue, 19 May 2020 11:27:45 +0200 [thread overview]
Message-ID: <20200519112745.6971271b@alma-ubu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]
Does anyone else have the same problems?
On my system java-testng sometimes fails nondeterministically within
the check phase:
===============================================
TestNG
Total tests run: 1633, Failures: 2, Skips: 0
===============================================
Failures in <suite> :TestNG, <test> :Regression2
test.thread.ParallelTestTest.verifyParallel()
StackTrace:
java.lang.AssertionError:
Expected size:<4> but was:<3> in:
<{59L=59L, 60L=60L, 62L=62L}>
at test.thread.ParallelTestTest.verifyExpected(Unknown Source)
at test.thread.ParallelTestTest.verifyParallel(Unknown Source)
... Removed 24 stack frames
test.thread.ParallelTestTest.verifyParallel()
StackTrace:
java.lang.AssertionError:
Expected size:<4> but was:<3> in:
<{55L=55L, 56L=56L, 58L=58L}>
at test.thread.ParallelTestTest.verifyExpected(Unknown Source)
at test.thread.ParallelTestTest.verifyParallel(Unknown Source)
... Removed 24 stack frames
Do others experience this too, or is it just my machine?
On berlin, everything looks fine, that makes we wonder:
https://ci.guix.gnu.org/search?query=%5Ejava-testng
We had some problems in the past with other parallel tests:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30526
I also tried to update java-testng but that was not possible quickly,
because of new/updated dependency-graph.
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2020-05-19 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 9:27 Björn Höfling [this message]
2020-05-19 12:08 ` bug#41394: java-testng: again nondeterministic test-failures? Julien Lepiller
2023-08-24 11:25 ` Konrad Hinsen
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=20200519112745.6971271b@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=41394@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.