From: "Gábor Boskovits" <boskovits@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 30526@debbugs.gnu.org
Subject: bug#30526: java-testng: non-deterministic test failures
Date: Wed, 21 Feb 2018 10:07:33 +0100 [thread overview]
Message-ID: <CAE4v=pgjxygJ=8RWnyte6E4iAxUUkHhghJvZRKgzmP2E1rX8rg@mail.gmail.com> (raw)
In-Reply-To: <87606tjd8n.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]
2018-02-19 14:55 GMT+01:00 Ricardo Wurmus <rekado@elephly.net>:
> Sometimes I get this error when building java-testng 6.14.2:
>
> --8<---------------cut here---------------start------------->8---
> ===============================================
> TestNG
> Total tests run: 1630, Failures: 1, Skips: 0
> ===============================================
>
> Failures in <suite> :TestNG, <test> :Regression2
> test.testng387.TestNG387.testInvocationCounterIsCorrect
> ForMethodWithDataProvider()
> StackTrace:
> java.lang.AssertionError: Arrays do not have the same size:3 != 4
> at test.testng387.TestNG387.testInvocationCounterIsCorrect
> ForMethodWithDataProvider(Unknown Source)
> ... Removed 27 stack frames
>
> phase `check' failed after 297.3 seconds
> --8<---------------cut here---------------end--------------->8---
>
>
>
This actually seems to be known upstream, I consider reopening this bug:
https://github.com/cbeust/testng/issues/582.
It seems they just disabled the failing tests. I guess we should do the
same.
> --
> Ricardo
>
> GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
> https://elephly.net
>
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 2050 bytes --]
next prev parent reply other threads:[~2018-02-21 9:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 13:55 bug#30526: java-testng: non-deterministic test failures Ricardo Wurmus
2018-02-21 9:07 ` Gábor Boskovits [this message]
2018-02-21 9:20 ` Gábor Boskovits
2018-02-25 11:16 ` Julien Lepiller
2018-02-26 7:23 ` Gábor Boskovits
2018-02-27 7:19 ` Gábor Boskovits
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE4v=pgjxygJ=8RWnyte6E4iAxUUkHhghJvZRKgzmP2E1rX8rg@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=30526@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).